Editing a Page
Stacking blocks to build a page, the settings every block shares and the names that don't explain themselves
A page is a stack of blocks. Each block is one band of the page: a hero, a grid of cards, a form. You add a block, fill in its fields and drag it up or down to change the order. If you built pages on the legacy site, this is the same idea as stacking flexible content layouts, with different vocabulary.
The picker groups blocks rather than showing one long list: Layout, Content, Cards & Grids and Forms & Embeds.
Grouped Blocks
You usually don't need it. Every block carries its own Background & spacing panel: background, padding, rounded corners, a decorative flourish, container width and an anchor ID. Stacking blocks and giving each its own background covers most pages.
Grouped Blocks is for when two or more blocks should share one background band and one heading.
When a block sits inside Grouped Blocks, its own Background & spacing panel disappears. The wrapper supplies the band, so the background, spacing and anchor for everything inside live there. If you're looking for a background setting on an inner block, look one level up.
Hero
One block, seven variants: Standard, Split, Centered, Text Only, Compact, Feature and Backdrop. Title is the only required field. The rest of the form changes with the variant:
- Compact shows no buttons, so the button fields are gone.
- Standard and Feature seat media beside the copy; the media width, fit, overlap and position controls appear only on those two.
- Feature and Centered are the two with a checklist, so the features list appears only there.
- The image-flip control belongs to Backdrop alone.
If a field isn't in the form, the variant doesn't render it. Nothing you fill in gets quietly discarded.
Blocks that fill themselves
Some blocks have no per-item fields. You give them a heading and a column count, and the content comes from a list elsewhere in the CMS, which is what you edit to change what appears on the page:
| Block | Where the content comes from |
|---|---|
| Dining Center Grid | The Dining Centers list |
| Affiliation Seals | The Affiliations list |
| Volunteer Role Grid | The Volunteer Roles list. Leave the roles field empty to show all of them; list specific roles to control the order |
| News & Events Listing | News posts and events |
| Job Openings | Paycom's job board, fetched on a schedule. Not from the CMS at all |
| Service Area Map | Fixed. The counties aren't editable |
| Eligibility Check | Fixed. The questions aren't editable |
Card Grid
Card Grid has three sources, and each shows a different set of fields:
- Custom. You write the cards yourself and pick a card type.
- Latest. Pulls the most recent news or events automatically.
- Hand-picked. You choose specific posts or events, and the order you list them is the order they appear.
On Latest and Hand-picked, cards always render as link cards. The card-type setting does nothing there; it only takes effect on Custom.
Emphasis in headings
In a title you can mark words for emphasis:
==words==puts a highlighter swipe behind the words{{words}}colors the words with the accent color|forces a line break where you put it;\|gives you a literal pipe character
The color is decided by the background the heading sits on. You choose what to emphasize, never which color. These marks work in hero titles, CTA headings and the heading and subheading of every block's Background & spacing panel.
Emphasis marks never reach a screen reader. They're stripped from alt text, page titles and search results.
Headings
You never pick a heading level. They're built from where a block sits: the first hero on the page takes the h1, band titles are h2, and anything inside a band goes one level deeper. Rich Text offers h2 to h4 and nothing else.
Required fields
- Service Option Grid is the only block that requires an icon on every item.
- Testimonial has an optional single quote at the top, but each row in the Quotes list needs both a quote and an author. A row missing either is dropped.
For how the rest of the CMS maps onto what you knew from the legacy site, see Coming from WordPress.