Modules and sections by task
A module is an editable content component, such as a product directory or form panel. A section is a reusable composition that positions modules and supplies starting content, background treatment, spacing, and gutters. The theme contains 25 custom modules and 50 section compositions; not every composition is offered as a separate item in the editor's section picker.
Use the page editor to select a module and edit the controls it exposes. Reorder or adjust page compositions using the native editing controls available on that page. A section's starting values can differ from a freshly inserted standalone module.
Choose by buyer task
| Task | Components to look for |
|---|---|
| Introduce products | Product hero, Product detail hero, Product directory, Product portfolio. |
| Explain technical and clinical context | Technology differentiators, Clinical applications, Specification list. |
| Organize supporting information | Evidence highlight, Standards register, Proof strip, Information index. |
| Present resources | Resource directory, Resource highlight, Document links. |
| Structure a story or process | Section introduction, Editorial feature, Workflow steps. |
| Invite a next step | Conversion panel, Primary action link, Native form panel. |
| Present people and relationships | Team directory, Event list, Partner directory. |
| Manage shared navigation | Site header navigation and Site footer information. |
Content and Styles
Content controls change text, records, images, and destinations. Styles controls change supported internal presentation, such as reading width, desktop columns, image position, alignment, or spacing. Not every module offers every style option.
Section compositions establish white, subtle, or dark surfaces where used, with compact, standard, or spacious spacing. These treatments are not universal module dropdowns. Preview after changing native section styles so text contrast and page rhythm remain appropriate.
Blank fields and records
Optional text, images, and actions are generally omitted when blank, but the exact requirements differ by module. A heading can remain when its list is empty. Removing a list does not remove the surrounding section's spacing.
Some repeaters require at least one structural record. Clear its content if you need the supported empty state; do not add invented information to fill the record. Specifications require both term and value, documents need a title, and people/events/partners need a name or title. See troubleshooting.
Workflow numbering follows the order of visible steps. Leave Step label blank unless you want additional descriptive text; entering another number can duplicate the automatic number.
Use a meaningful action label and an actual destination. A visually hidden action can still retain its label in the editor for later configuration.