> For the complete documentation index, see [llms.txt](https://docs.morpht.com/convivial-for-govcms/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.morpht.com/convivial-for-govcms/content-editing/other-content-types.md). # Other content types Most content is a Page or an Article, and those work as described in [Editing a page](/convivial-for-govcms/content-editing/editing-a-page.md). The types below add fields or behave differently. ## Sections A Section is a landing page for an area of the site — *News*, *Events*, *About* — that introduces the area and links down into it. *Manage → Content → Add content → Section*. See a test section on the demo site: ![The Section form](https://3733701002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3fBWwpuJPUqPpT2ulMXp%2Fuploads%2Fgit-blob-cf46707966fa59e6f05c0508282f2d24fdd54f52%2Fsection-add.png?alt=media) A Section has the same fields as a Page. What makes it a landing page is how it is built: a strong **Header** (banner image or palette, introduction, featured links), little or no body text, and a set of components — typically a **Node List** of the area's key pages, an **Embedded View** for a listing, cards for calls to action. Set **Hide → Sidebar** when the design should run full width. Put the Section in the main menu and nest the area's pages beneath it, so the menu and the breadcrumb match. ## People A Person page is a staff profile or an author page. *Manage → Content → Add content → Person*. See a test person on the demo site: ![The Person form](https://3733701002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3fBWwpuJPUqPpT2ulMXp%2Fuploads%2Fgit-blob-e18720114473f33c7e974d4ad7042827151abb37%2Fperson-add.png?alt=media) * **Title** — the person's name. **Role** — their position, shown under the name. * **Thumbnail** — the portrait, used on the People listing and wherever the person is shown as a card. * **Key** — a unique identifier for the person, e.g. `person-john-doe`, used when other content or personalisation refers to them. Lowercase with hyphens, and never change it once the page is published. * **Content** and **Components** — the biography. Articles name their author from the Person pages, and each Person page lists that author's articles automatically. People appear on the People listing in the order the site's view defines; there is no manual ordering. ## Collections A Collection is a faceted search page — Search, Resources and FOI on the demo site. Its results and filters come from a view placed by a Site administrator with Layout Builder, so editors normally change only the **Title**, **Description** and **Introduction**. Do not add a Collection for an ordinary list of links; that is a Section with a Node List. See a test collection on the demo site: ## Alerts An Alert is a site-wide, time-limited notice — a closure, an outage, a deadline — shown as a banner across the top of every page until it expires or the visitor dismisses it. *Manage → Content → Add content → Alert*. ![The Alert form](https://3733701002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3fBWwpuJPUqPpT2ulMXp%2Fuploads%2Fgit-blob-9cddfd7e4df73d2ce2c8d49f7f67f97eef7119de%2Falert-add.png?alt=media) * **Title** and **Content** — keep them to a sentence or two; the banner is narrow. * **Type** — *Success*, *Error*, *Warning* or *Info*. Sets the colour and icon, so pick by seriousness: *Error* for something broken, *Warning* for something visitors must know before acting, *Info* for the rest. * **Start date** and **End date** — the alert shows only between them, so you can set one up ahead of time and it retires itself. * **Dismissible** — lets visitors close the banner; their choice is remembered in their browser. Leave it off only for alerts nobody should be able to hide. Alerts go through the same workflow as any page, so an Approver has to publish one — plan for that when the notice is urgent. ## Events An Event is a page with a date, shown in the events listing and calendar-style cards. *Manage → Content → Add content → Event*. See a test event on the demo site: ![The Event form](https://3733701002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3fBWwpuJPUqPpT2ulMXp%2Fuploads%2Fgit-blob-19646bde64d2a134837ae9b49d4de11d6ec99f4f%2Fevent-add.png?alt=media) * **Start** and **End** — date and time. Past events drop off the listing automatically. * **Duration** and **Location** — free text shown on the event card, e.g. *2 hours* and *Canberra, ACT, or online*. * **Type** — the event type, from the *Event type* vocabulary, used to filter the listing. * **Series** — link to the parent event when this is one of a set, so the series page can list its dates. * **Topics**, **Audiences** and **Related** — classification shared with Articles and Resources; related pages appear at the bottom of the event. Everything else — header, content, components, metadata — works as on a Page; see [Editing a page](/convivial-for-govcms/content-editing/editing-a-page.md).