Skip to main content
Version: 2.0.0

Structure & Organization

As a content designer, your job is to organize information so users can find what they need instantly. Good structure is invisible—it just works. Bad structure frustrates users.

The Content Designer's Framework​

Structure is about understanding user journeys and organizing content to support how users actually search, read, and learn.

Information Architecture Principles​

1. Start with User Tasks​

Organize content around what users want to accomplish, not your product structure:

Product-focused:

  • Dashboard Settings
  • User Profile Management
  • Notification Controls
  • Data Export Features

Task-focused:

  • Getting Started
  • Managing Your Account
  • Staying Updated
  • Exporting Your Data

2. Hierarchy That Matches User Needs​

Create mental models that match user thinking:

Writing Guide
├── Getting Started
│   ├── What is this?
│   └── First steps
├── Common Tasks
│   ├── Creating content
│   ├── Publishing
│   └── Analytics
└── Advanced
    ├── Custom styles
    └── API

3. Descriptive Headings​

Headings are scannable—make them meaningful:

Vague:

Overview Details Settings

Descriptive:

What is Markdown? Formatting Your Text Control Notifications

Content Structure Formula​

The 4-Part Pattern​

1. Context (What is this?)

Brief explanation of what you're about to read

2. Action (What do I do?)

Step-by-step instructions or key points

3. Example (How does it work?)

Real example users can relate to

4. What's Next?

Links to related topics or next steps

Example Page Structure​

# Creating Your First Post

Want to share your first update? Here's how.

## Step 1: Click "New Post"
[Screenshot]

## Step 2: Write Your Title
Make it clear and specific.

## Step 3: Add Your Content
Click the text area and start typing.

## Step 4: Publish
Click the green "Publish" button.

## What can I do next?
- Share your post
- Add collaborators
- See analytics
Home > Documentation > Content > Creating Posts

Users always know where they are and how to go back.

Related Content Links​

At the bottom of each page:

← Back to Getting Started
Next: Publishing Your Post →

Related Articles:
- Formatting Guide
- Analytics Explained
- Troubleshooting

Search & Discoverability​

  • Use clear, predictable URL structures
  • Include keywords in headings
  • Create a sitemap or index
  • Link between related topics

Visual Content Hierarchy​

Typography for Scanning​

  • H1: Page title (1 per page)
  • H2: Main sections (users skip to these)
  • H3: Subsections (detail level)
  • Body text: Actual content
  • Bold: Key terms users should remember

Lists Over Paragraphs​

When you have 3+ items, use a list:

Before publishing, check:
- Spelling and grammar
- Links work correctly
- Images are optimized
- Title is clear

Content Patterns​

Decision Trees​

Help users choose the right path:

Do you have an account?
├─ Yes → Go to login
└─ No → Create account first

FAQ Structure​

Organize by user question, not topic:

Frequently Asked Questions

Q: How do I change my password?
Q: Why won't my post publish?
Q: Can I export my data?

Troubleshooting Guide​

Organized by symptom, not cause:

Problem: App keeps crashing
- Check you have latest version
- Clear app cache
- Restart your device

Problem: Can't log in
- Verify your email
- Reset your password
- Contact support

Testing Your Structure​

Card Sorting Exercise​

Ask users to organize topics the way they'd expect them. Compare results to your structure.

Tree Testing​

Test navigation before building. Do users find content easily?

User Feedback​

  • Can they find what they need?
  • Is the path logical?
  • Are headings clear?
  • What's confusing?

Style Guide

Estimated reading time: 5 min
Skill level: Beginner – Intermediate

What you'll learn​

  • How to maintain consistent voice, tone, and grammar
  • Formatting rules for code, lists, and tables
  • When to choose tutorials, how‑tos, and API references
  • Useful tools and style guide resources

Voice and Tone​

Active Voice Example:

 "The system processes the request"
 "The request is processed by the system"

Appropriate Tone:

  • Instructional: Confident and direct
  • Explanatory: Clear and educational
  • Error Messages: Helpful and actionable
  • Release Notes: Professional and informative
Last updated on

Was this page helpful?