Glossary | Doghouse SaaS Knowledge Base [Skip to content](#main) [ ![Doghouse SaaS Knowledge Base](/storage/branding/01M3N8PQ7PSDNQBBKKJM6XGW03.svg) ](https://nginx.deploy-lagoon-production.districtcms-docs.dh1.amazee.io) [Product documentation](/articles) [Roadmap](/roadmap) Toggle navigation [Product documentation](/articles) [Roadmap](/roadmap) 1. [Home](/) › 2. [Product documentation](/articles) › 3. [Getting started](/articles?category=16) › 4. Glossary Glossary ======== Updated 5 days ago · 5 min read Search Search Overview -------- Doghouse SaaS is built on Drupal, and Drupal brings its own vocabulary. Some of it is ordinary English used in a particular way: "content type", "taxonomy", "revision". It is easy to nod along without being certain. This page defines the terms you will actually meet, grouped by where you run into them. Nothing here is something you need to memorise; it is here so you can look one up mid-task. --- Content and structure --------------------- Term What it means **Content item** One piece of content. You may also see it called a *node*, which is the underlying technical name. They mean the same thing. **Example:** a single news article, event or page. **Content type** A template defining what a kind of content is made of. Choosing a content type decides which fields you are given. **Example:** an Event has a date, a location and an event type; an Article has a subtitle, a banner image and news categories. **Field** One labelled box on a content form. Fields are what a content type is built from. **Example:** Title, Body, Summary, a date, an image. **Component** A reusable block of page content you stack to build a layout. Also called a *paragraph*. **Example:** a text section, a card grid, an accordion or a call to action. **Media** A file the site manages as a reusable item. Because media items are reused rather than copied, replacing one updates every page using it. **Example:** this site handles five kinds: image, document, video, remote video and SVG. **Media library** The shared store of every media item, which you pick from when adding an image or document to a page. --- Organising and finding things ----------------------------- Term What it means **Taxonomy** The site's system of categories. **Example:** it's how a news article gets filed under a topic, or an event marked as a workshop. **Vocabulary** One set of categories within the taxonomy. This site has two. **Example:** News categories and Event types. **Term** One entry inside a vocabulary. **Example:** "Infrastructure" is a term in the News categories vocabulary. **Menu** A navigation list. Each is a separate menu you can edit. **Example:** Main navigation, the Footer links and the Footer bottom links. **URL alias** The readable web address of a page, rather than an internal number. Change it and the site keeps a redirect from the old address, so links keep working. **Example:** */planning/development-applications*. **Redirect** A forwarding rule sending an old address to a new one, so links and bookmarks keep working after a page moves. --- Writing and publishing ---------------------- > **💡 Note:** Every content type on this site uses the Draft / Published / Unpublished workflow, so every content form has a **Save as** or **Change to** box in place of a Published tick. Term What it means **WYSIWYG editor** The formatting toolbar above a rich-text field. "What you see is what you get": you style text visually rather than writing HTML. **Rich text** Text that carries formatting, as opposed to plain text, which carries none. **Example:** bold, headings, links, lists. **Text format** The rule set deciding which HTML is allowed in a field. It is why markup you paste in can silently disappear on save. **Draft** Saved but not visible to visitors. Drafts let you work on a page over several sittings without publishing it half-finished. **Published** Live and visible to everyone. **Unpublished** Taken down but not deleted. The page and its history remain; visitors simply cannot reach it. **Moderation state** Which of those a piece of content is currently in, and the mechanism for moving between them. Where it applies you will find a **Change to** menu in the sidebar of the content form, offering Draft, Published and Unpublished. **Revision** A saved snapshot of a page at a point in time. Every save creates one, which is what makes it possible to see what changed and go back. **Scheduling** Setting a future date and time for content to publish or unpublish itself. It is installed but not yet switched on for any content type. --- People and access ----------------- Term What it means **Account** One person's sign-in. Actions are recorded against it, which is how the site knows who changed what. **Role** A named bundle of permissions given to accounts, so access is decided once per role rather than once per person. **Example:** Content editor, Administrator. **Permission** One specific thing an account may do. **Example:** creating a page or deleting an image. **Anonymous user** Anyone reading the site without signing in. Most of your visitors. **Authenticated user** Anyone who is signed in, whatever else they hold. --- Behind the scenes ----------------- These appear in the interface or in conversation with your developers. You will rarely need to act on them. Term What it means **Module** An add-on providing a feature. Installed once, then available site-wide. **Example:** webforms, the accessibility checker, scheduling. **Theme** The design layer deciding how the site looks. **Example:** colours, fonts, spacing. **Block** A small piece of content placed in a region of the page, rather than being a page in its own right. **Example:** the homepage hero, the site alert, or the Acknowledgement of Country in the footer. **View** A configurable list of content. Most listings on a site are views. **Example:** the Content administration screen or a "latest news" feed. **Cache** Stored copies of pages that make the site fast. Occasionally a change will not appear until the cache clears, which is why "try again in a minute" is sometimes the right advice. **Webform** A form visitors fill in, together with the submissions it collects. **Example:** contact, feedback, a service request. Related articles ------------------ - [ Signing in → ](/articles/signing-in) - [ Finding your way around the editing interface → ](/articles/finding-your-way-around-the-editing-interface) - [ Roles and what they let you do → ](/articles/roles-and-what-they-let-you-do) - [ Content workflow and statuses → ](/articles/content-workflow-and-statuses) - [ Taxonomy: vocabularies and terms → ](/articles/taxonomy-vocabularies-and-terms) Was this article helpful? ------------------------- Your feedback helps us prioritise what to rewrite. Yes No [ Back to Getting started ](/articles?category=16) On this page **Need additional help?** Submit a support request through the [**support portal** ](https://doghouse.atlassian.net/servicedesk/customer/portals)or email © 2026 [Doghouse SaaS](https://doghouse.agency) [Glossary](/articles/glossary)