Team, events, and partners
These lists intentionally start empty. Their introduction may remain visible, but an empty list does not create empty cards or a grid. Add only information your organization has reviewed and authorized for publication.
Team Directory
Supports 0–12 people, starting at zero. A nonblank Person name is needed to render a person. Role, summary, image, and profile action are optional; spaces alone do not count as a name.
Add a person, supply the name and relevant responsibilities, then optionally choose an image and profile destination. Profile actions require both visible text and a supported destination. The layout uses one column on small screens, two from 768px, and three from 1024px. Portraits use a 4:5 frame with cover cropping; preview the crop before publishing.
The module has no dedicated credentials, social-profile collection, or medical-endorsement fields. Review any qualifications you choose to include in prose rather than assuming the theme verifies them.
Event List
Supports 0–10 events, starting at zero. A nonblank Event title is required for display. Kind, date text, time text, location text, summary, and action are optional.
Dates and times are plain text. Write clear information for the intended audience, including timezone context when relevant. The theme does not calculate timezones, sort upcoming/past events, schedule sessions, or integrate a calendar. Arrange and maintain entries yourself. The list uses a single stacked layout.
An action can point to your actual event information or registration destination; a link does not create registration handling. Publish dates and locations only when confirmed.
Partner Directory
Supports 0–12 partners, starting at zero. A nonblank Partner name is required for display. Region, summary, logo, and action are optional. Logos use a 4:3 frame with contain sizing. The layout uses one, two, and three columns at the same breakpoints as Team Directory.
Region is descriptive text, not a territory filter or coverage system. The theme does not establish exclusivity, availability, or distributor authorization. Supply only verified relationship information and permitted logos.
Check empty and populated states
For each list, add one real record, save, reload, and preview it. Remove the record if it is no longer needed and confirm the empty list collapses. The section's introduction and spacing can still remain.
These three modules accept HTTP(S) URLs, site-root paths beginning with a single slash (such as /contact), query strings, and named fragments. Paths such as contact or ../contact are not supported. Blank destinations, a bare hash, and unsupported schemes are rejected; use a web contact page rather than assuming email/telephone links will display. See image guidance.