Q: How can I organize content on my agency’s website?
A: Most people skim web pages instead of reading every word — especially on mobile devices. Well-organized content helps Connecticut residents and businesses find answers quickly, builds trust in the State government, and improves accessibility and search results.
Good organization reduces confusion, lowers support calls, and makes your agency’s website more user-friendly.
Recommended page structure (Bite-Snack-Meal)
Follow the Bite-Snack-Meal approach on all of Ct.gov’s pages:
Bite — The main headline (H1). Make it short, powerful, and specific. It should clearly describe what the page is about and include key search terms users might type.
How to add the H1 in Sitecore: The H1 is created in the Rich Text component that Sitecore automatically adds under the Resources folder for each page. Click Show editor and replace “Page Header Here” with your page title. Then add a Full Width Container at the top of your page in the Experience Editor and insert that Rich Text component so the H1 appears correctly on the live page.
Snack — A summary paragraph right at the top (often called the teaser or lead-in). Keep it to one or two sentences or about 140 characters. This summary expands on the headline and helps users decide if they’re in the right place.
How to add the Snack (summary) in Sitecore: Use the Lead Story component for your summary paragraph. Add it directly under your H1. Keep the text short (one or two sentences) so customers can quickly confirm they’re in the right place.
Meal — The main content. Break it into small, easy-to-digest chunks using sub-headlines, short paragraphs, and lists.
How to build the Meal in Sitecore Use a mix of components to break your main content into clear, scannable sections. Most pages use a combination of tile cards, link lists, feature content cards, and accordions to build the meal. If you’re unsure which component fits your content, see the KB How to choose the right component for guidance.
Use clear headings to guide readers
- Start every page with one unique H1 (the page title).
- Each section of content needs a clear title. Sitecore automatically applies the correct heading level based on the component you use, so you don’t need to manually choose H2, H3, etc. If a component includes a title field, enter the section title there. If a component does not display a section title (like Tile Cards), add the title in the Experience editor within the container’s sublayout title field.
- Write all headlines in sentence case (capitalize only the first word and proper nouns).
- Though character limitations vary in each component, try to keep subheadlines under 30 words or 70 characters so that they display well on mobile devices.
- Headings help customers scan and also improve search engine optimization.
Example: (Title) How do I renew my driver’s license?
(Then a short snack paragraph)
(Copy) What you need to renew online. Include step-by-step instructions.
(Call to action and link to more content, often a knowledge base article.) What if I can’t renew online?
Break content into scannable chunks
- Limit paragraphs to 3 to 5 short sentences.
- Keep sentences to 15 to 20 words when possible.
- Use bulleted or numbered lists for key points, steps, or options.
- Add images or visuals only when they support the message — always with descriptive alt text if applicable.
- Place the most important information “above the fold” (visible without scrolling on a mobile phone).
More best practices for page organization
- Put the most important or frequently needed information first.
- Use a clear call to action with a descriptive link that tells customers what they can do next.
- Navigation: Anchor/jump links can help when a page has many sections.
- Avoid walls of text: Break content logically by topic or task.
We use a component-based design system in Sitecore. Use built-in components (such as Lead Story, Accordions, or Tile Cards) to keep layouts consistent across all State websites. This reduces errors and ensures a professional look.
Before you publish – quick checklist
- One clear H1 per page
- Logical heading hierarchy
- Content broken into short chunks and lists
- Most important info at the top
- Sentence case for all headlines
- Mobile-friendly (test on your phone)
- Plain language at approximately a 6th-grade reading level
Need more help?
- CT Content Style Guide
- On-page content structure details
- Voice, tone, and audience guidance
- Accessibility best practices
-
Submit a ticket through the BITS Service Portal for help:
- Go to BITS Service Portal – Home
- Click Request something new
- Select Digital Services Request