Pages ship in days
Production is measured in days rather than sprints, because nothing is being invented from scratch.
SHIP PAGES WITHOUT A DEVELOPER
Shopify section libraries for content-heavy brands
Catalogue-heavy brands get a library of reusable Shopify sections so new collections, campaigns and landing pages ship without a developer in the loop. Marketing composes pages from parts that are already designed, tested and fast.
IN SHORT
- A section library is a documented set of reusable Shopify sections your team composes pages from.
- It is native theme code — no page builder subscription, no third-party script, no performance penalty.
- The trade-off is that genuinely new section types still need a developer; the library is sized to make that rare.
- Most brands need 12 to 20 sections to cover the page types they actually publish.
- It pays for itself when campaign pages stop going through a development queue.
- Typical library
- 12–20 sections
- Build time
- 4–7 weeks
- Built on
- Online Store 2.0
- Page build after
- Hours, not sprints
- Needs a developer
- No
The problem it solves
A brand ships a campaign. Marketing needs a landing page. The page needs a layout that is nearly — but not quite — the one from last time. So it goes into the development queue, waits a week, comes back slightly wrong, and by the time it is right the campaign has half run.
Do that twelve times a year and the cost is not the development hours. It is the campaigns that never shipped because the queue was too long to bother.
A section library removes the queue for the ninety percent of pages that are variations on something you have published before, and keeps the developer for the ten percent that genuinely are new.
What a section library actually is
Not a page builder, not a template
It is a set of Online Store 2.0 sections in your theme, each with schema settings, that your team assembles in the Shopify editor. The sections are yours, they are native theme code, and they load like the rest of your theme because they are the rest of your theme.
What you give up compared to a page builder app is total freedom — nobody can invent an arbitrary new layout at 5pm. What you gain is that nobody can invent an arbitrary new layout at 5pm, so the site stays fast and on-brand.
Library against page builder app
| Section library | Page builder app | |
|---|---|---|
| Cost | Built once | Monthly subscription, forever |
| Page speed | Native theme code | Third-party script on every page |
| If you cancel | Nothing changes, it is your theme | Pages can break or need rebuilding |
| New layout types | Needs a developer | Anyone can assemble one |
| Brand consistency | Enforced by the tokens | Depends on who is building |
| Best for | Brands publishing repeatable page shapes | Teams needing total layout freedom |
How we build one
Five stages, starting from what you have actually published rather than what you think you might need.
- 01
Audit what you publish
We look at the last six to twelve months of pages you actually shipped — campaigns, collections, launches, editorial — and find the page types underneath them. Most brands publish four or five shapes repeatedly.
- 02
Define the set
Those shapes become a section list, each with the settings it needs to exposed. Typically 12 to 20 sections covers everything a brand publishes in a year.
- 03
Build with tokens
Sections are built against shared spacing, type and colour tokens mapped to theme settings, so the library stays visually coherent no matter who composes the page.
- 04
Document for merchandisers
Guidance written for the people who will use it — what each section is for, what each setting does, and which combinations work. Not developer documentation.
- 05
Extend as campaigns need
New sections get added to the library rather than built one-off for a single page, so the set compounds instead of sprawling.
What a typical library covers
- Hero variants — image, video, split and text-led
- Product and collection grids with editable filtering and sort
- Editorial blocks — long-form copy, pull quotes, image and text pairings
- Comparison and specification tables for considered purchases
- Social proof — reviews, press, user-generated content
- FAQ and accordion blocks
- Campaign and launch blocks with countdown, badge and offer settings
- Cross-sell and bundle blocks that do not cost page speed
How a library stays useful
Every section library decays the same way: it grows. Three years on, a set of sixteen has become sixty, four of them do nearly the same thing, and nobody can remember which one is current. The rules below are what stops that, and they are the part most teams skip.
- A new section needs a second use case before it is built. One page wanting something is a one-off; two pages wanting it is a section.
- Sections are named for the job they do, not the layout they use. "Product comparison" survives a redesign; "three-column grid" does not.
- Settings are constrained deliberately. Every extra toggle is a way for a page to end up off-brand, and the library exists to stop that.
- When two sections converge, they are merged and one is retired — with the pages using it migrated, not left behind.
- The set is reviewed twice a year against what actually gets used. Sections nobody has placed in twelve months come out.
- Somebody owns it. A library with no owner becomes a folder.
- Healthy size
- 12–20 sections
- Near-duplicates
- Zero
- Named for
- The job, not the layout
- New section needs
- A second use case
- Reviewed
- Twice a year
What it changes
The site stays fast
Sections are built once against a performance budget, so a new page cannot quietly add a third-party script.
The brand stays consistent
Shared spacing, type and colour tokens mean a page built by anyone looks like the rest of the site.
The set compounds
New sections join the library rather than living on one page, so year two is faster than year one.
What drives the cost
A library is priced by how much has to be decided, not by how many sections are listed. These move the number most.
How many sections are genuinely distinct●●●●●
Twelve real jobs cost far less than twenty layouts that overlap. Most of the work in scoping a library is arguing the list down.
Depth of settings●●●●
A section with four deliberate settings is quick. The same section with twenty settings is a small product, and someone has to document and support it.
Existing theme quality●●●●
Building into a clean Online Store 2.0 theme is straightforward. Building into a theme four agencies have extended means untangling first.
Content and merchandising rules●●●
Sections that have to respect stock state, market pricing or B2B catalogues carry logic, not just layout.
Migrating existing pages●●
Rebuilding live landing pages onto the new sections is usually the right call, and is scoped separately so it can be phased.
The set is deliberately finite. A library of forty sections costs more than twice a library of twenty and is worth less, because nobody can hold forty in their head.
One page, composed
What this looks like on the day someone uses it.
A campaign landing page is usually a hero, a proof block, a product grid, an editorial explainer and an FAQ. Every one of those already exists in the library, so the page is assembled in the theme editor by the person who planned the campaign, in an afternoon.
The difference is not speed on the first page. It is that the fiftieth page costs the same as the first, and looks like it belongs to the same brand — which is not true of a site where every landing page was built by whoever was free that week.
Brands running on one
Wonderskin
Mighty Jaxx
Julia B
Wonderskin runs continuous landing page production off a section library. Julia B uses one for a catalogue where merchandising is the product story, and Mighty Jaxx for a release calendar that would otherwise be a permanent development queue.
Section library questions
What teams ask before committing to one — usually after a year of landing pages arriving late.
How is a section library different from a page builder app?
It is native theme code, so there is no third-party script, no subscription and no performance penalty. The trade-off is that new section types need a developer, which is what the library is sized to avoid.
Who maintains the library after launch?
We do, on a retainer, or your team does — the sections are ordinary Shopify theme code with documentation.
How many sections does a brand need?
Usually 12 to 20. That covers the four or five page shapes most brands publish repeatedly, with enough settings on each to handle the variation. Beyond about 25 the library becomes hard to choose from, which defeats the point.
Is a section library better than a page builder app?
For most brands, yes. It is native theme code, so there is no subscription, no third-party script slowing every page and nothing that stops working when you cancel. The trade-off is that new section types need a developer, where a page builder lets anyone assemble anything — including things that are slow or off-brand.
What happens if we change agency?
The library is ordinary Shopify theme code in your repository with documentation. Any competent Shopify developer can extend it.
Related
New Store Design & Development
A custom Shopify storefront built from your brand and your buyer data — not a retrofitted template.
Theme Customization
Extend Dawn or your existing theme with maintainable sections your merchandisers can actually use.
Design to Shopify
Send us the design files. We build them into a Shopify theme section by section, with the CMS wiring done.
NEXT STEP
Free store audit
A senior Shopify engineer reviews your storefront, theme performance and checkout, then sends a prioritised list of fixes.