Designing the front page
This page is for theme designers who design a site's front page. It is the page clients care most about and the one that changes most often, so how it is built decides what editors can change without you. Exponential offers three ways to build it; the choice is a design decision as much as a technical one, and it should be made before the mockup is final.
Contents
- Three ways to build it
- Choosing with the client
- Designing a front page built from blocks
- Designing a fixed front page
- Content that changes every day
- The front page and the frame
- Checks
Three ways to build it
| Way | How | Who changes the arrangement |
|---|---|---|
| A layout | the root page gets a layout from the layouts editor; editors place and order blocks | editors |
| A class of its own | a front page class with fields (hero, featured items, intro), drawn by its own full view template | the template; editors fill the fields |
| An override of the root node | the root node's full view gets a dedicated template, matched by remote id | the template; content comes from fetches |
The template-based ways are explained in Override a single node and its alternatives; the layouts way in Tutorial: build a landing page with layouts.
Choosing with the client
| Question | Points toward |
|---|---|
| Will editors want to change the order or add sections themselves? | a layout |
| Is the front page one strict composition the brand depends on? | a class or an override |
| Will several pages (campaign pages, section fronts) share the same structure? | a layout, or a class used for all of them |
| Is the front page mostly automatic (latest news, upcoming events)? | an override with fetches, or list blocks with queries in a layout |
Most content sites end up with a layout: editors get freedom within the blocks and view types you designed. Write down the choice and the reason; it decides what the client can do without a designer later.
Designing a front page built from blocks
Design the front page as an example arrangement of your blocks, not as a fixed composition, and say so when you present it. Then:
- check that each block in it also works in other positions and next to other blocks (Designing layout blocks);
- design two or three alternative arrangements (a campaign week, a quiet week), to show the system holds;
- decide which blocks belong to a shared layout (often a pre-footer area) and appear on many pages (Shared layouts and linked zones).
Designing a fixed front page
A fixed composition must still take changing content. Map each area to its source: a field of the front page object, a fetch of the latest items of a class, or a relation list editors fill (Mapping a design to content classes). Draw each area with zero, one and the maximum number of items.
Content that changes every day
- The hero image changes; design its slot for any picture editors pick, with a crop rule and text that stays readable on any image (text beside the image, or on a solid band, rather than on top of the photo) (Designing image crops and art direction).
- Lists of the latest items vary in length of titles and presence of images (Designing content listings and cards).
- Avoid areas that only look right with exactly three items.
- Front pages are cached; a developer decides how freshly automatic lists update (Caching for designers).
The front page and the frame
The front page sits inside the same pagelayout as every other page. If the front page needs a different header (for example a transparent header over the hero), that is a variation of the frame for one page, which costs a condition in the pagelayout and testing in both forms. Prefer a front page that works with the normal header (Designing headers and footers).
Checks
- To do: The way of building it is chosen and written down.
- To do: Each area mapped to a source; zero, one and many items drawn.
- To do: Two alternative arrangements, if it is a layout.
- To do: Hero readable with a dark and a light photo, in light and dark themes.
- To do: The first screen meets the performance budget (Designing for performance budgets).
Related pages
- Layouts for designers
- Layout rules
- The layouts editor
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.