FREEFirst project with us? Your landing page design is on the house.See the offer

Chapter 2 of 6

Planning the library

Most of a good library is decided before any code. Audit what you have, merge what repeats, name each section by its job and write down the recipes.

6 min readUpdated 2026-11-07
All chaptersChapter 2 of 6
  1. 01Why sections, not pages
  2. 02Planning the library
  3. 03Sanity schemas for sections
  4. 04Studio for marketers
  5. 05AI page building with guardrails
  6. 06Testing and governance

The short answer

Plan a library from your real pages. Audit the pages you have and the ones coming next, group what you find by the job each block does, merge near duplicates, then name each section for its job. Write page recipes to prove the set works. Only then design what is missing.

Our usual starting point for a marketing site is 20 or more sections, each with two to four variants, as our section library page says. Your audit decides the real number. A site with one offer may need fewer. Fewer, better sections are always easier to use.

Step 1: audit what you have

Take your most important pages and the page types on your roadmap. You do not need every blog post, because those stay on a template. Screenshot each page, cut it into blocks, and log each block in one sheet.

ColumnExampleWhy you need it
Page/pricingShows where the block is used
Block jobAnswer objectionsUsed for grouping in step 2
Current lookTwo-column accordionSpots near duplicates
Content neededQuestion, answer, up to 8 pairsBecomes the field list
Facts insidePrices, client namesTells you what should be a reference
BehaviourOpens on clickSets the build effort
Earns?High leads, keep as isProtects what already works

Ask the marketing lead what is coming in the next few months too. A library built only from the past will miss the next campaign. If you are also moving platform, this sheet sits alongside your URL inventory.

Step 2: group by job, then merge

Sort the sheet by job, not by how a block looks. Five blocks that all exist to prove you are trusted belong in one conversation. A common set of jobs:

  • Introduce: say what the page offers.
  • Explain: features, how it works, steps.
  • Prove: logos, quotes, numbers, case studies.
  • Compare: plans, tables, before and after.
  • Convert: call to action, form, pricing.
  • Reassure: FAQ, security, guarantees you can truly stand behind.
  • Navigate: related links, tabs, table of contents.

Within each job, merge hard. Two feature grids that differ only in columns are one section. A logo strip and a case study card are two sections, because they need different content.

Decision rule Same fields, different look: one section with a variant. Different fields: two sections. If a variant would hide more than a couple of fields, it is probably a separate section too.

How to name sections

Names last. Every saved section stores its type name, your code uses it, and your AI instructions will quote it. Renaming later means a content migration, so spend ten minutes on this now.

AvoidUseWhy
section3featureGridSays what it is
homeHeroheroA section is not tied to a page
purpleBannerctaBandColours change, jobs do not
heroNewhero with a variant"New" goes stale quickly
summer24PromoofferBandCampaigns end, the section stays
  • Use camelCase, the same in the schema and the component file, so featureGrid maps to FeatureGrid.astro.
  • Give each section a plain title for editors, such as "Feature grid".
  • Name fields the same way across sections. If one section says heading, none should say title or headline.
  • Name variants by what changes: imageLeft, centred, dark.

How many sections, and how many variants

There is no magic number. There is a clear sign of too few, and a clear sign of too many.

SignWhat it meansWhat to do
Editors keep asking for a new section for ordinary pagesToo fewLook for a missing job, then add one section
Editors use a section in ways it was not meant forToo few, or poor fieldsWatch them work, then fix the fields
Editors scroll past most of the list and pick the same fewToo manyRetire what nobody uses
Two people choose different sections for the same jobToo many, or poor usage notesMerge, or write the rule down

Variants need the same discipline. Every variant must be designed, built, tested and explained, and each one is a new choice the editor, or the AI, has to make. Keep two to four per section, and make each one look clearly different. Avoid open-ended options such as "custom colour" or "padding size". Those are how design drifts back in.

Write page recipes

A recipe is an allowed order of sections for one page type. Recipes do three jobs. They test your list, they guide editors, and later they give AI a safe starting point. Here is a sample:

Page typeRecipe
Feature pagehero, logoStrip, featureGrid, steps, quoteBlock, faq, ctaBand
Ad landing pagehero, logoStrip, problem, quoteBlock, form
Comparison pagehero, comparisonTable, quoteBlock, faq, ctaBand
Event pagehero, agenda, speakers, form, faq

Now do the paper test. Pick three real pages from your roadmap and build each one from your list, on paper. Each time you get stuck, ask whether you found a truly new job or just a page that should change shape. Add a section only for the first.

Separate content from sections

While you plan, mark anything in your sheet that must be true everywhere: prices, client names, testimonials, team bios, stats. These should not be typed into sections. They should be their own documents, which a section points to. Structuring Sanity content for AI explains why, and it is the most useful habit to adopt even if you never use AI.

The same goes for shared blocks that must stay identical on many pages, such as a standard closing call to action. Decide per block: is this the same everywhere, so edit once, or is it filled in per page?

What to build first

Do not build all of it at once. Order the work so that something usable arrives early.

  1. Core set. The sections that appear in nearly every recipe: hero, proof, features, call to action, FAQ.
  2. First real page. Build one live page from the core set. This finds most mistakes while they are cheap.
  3. Next set. Add what the next recipes need, in roadmap order.
  4. Long tail. Leave rarely used sections until someone has a dated need for them.

Done when You have a list of sections with one job each, a field list for each, named variants, and recipes that cover three real upcoming pages without a new design.

Takeaways

What to remember from chapter 2.

  • Audit real pages and your roadmap, then log every block in one sheet.
  • Group by job. Same fields means a variant, different fields means a new section.
  • Name sections for their job, because names are expensive to change later.
  • Keep two to four clearly different variants, and avoid open-ended style options.
  • Paper test recipes on three real pages before you build anything.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.