Blocks
A page block goes in a collection’s blocks field and is placed by RenderBlocks. Each page here shows the block rendered from its shipped sample, the fields an editor sees (read from the config at build time), and the two lines the site adds.
| Block | Slug | Renders |
|---|---|---|
| Hero | hero | HeroSweep |
| Sweep hero | heroSweep | HeroSweep |
| Compact hero | heroCompact | HeroCompact |
| Simple hero | heroSimple | HeroSimple |
| Rich text | richText | RichText |
| Showcase panels | showcasePanels | ShowcasePanelsBlock |
| Feature highlights | featureHighlights | FeatureHighlightsBlock |
| Feature checklist | featureChecklist | FeatureChecklistBlock |
| Process steps | processSteps | ProcessStepsBlock |
| Stats band | statsBand | StatsBand |
| Video | video | VideoBlock |
| FAQ columns | faqColumns | FAQColumnsBlock |
| Testimonial masonry | testimonialMasonry | TestimonialMasonry |
| Testimonial carousel | testimonialCarousel | TestimonialCarousel |
| Resources | resources | ResourcesBlock |
| Name, address, phone | nap | NapBlock |
The header blocks are separate: they go in a navigation global and build the bar, not the page.
What editors do not see
Section titled “What editors do not see”Accessible names, control text and per-row number overrides are not config fields. The @bison-lab/ui defaults stand, and a site that wants different wording overrides the renderer.
An array with a minimum opens with that many empty rows, and the admin field will not remove a row below it.