# Creating resource pages A resource page is a single web page within PortalHQ — richer than a file resource, with formatted text, images, embedded videos and links. Use it when the content doesn't fit into a single file or external URL. ## When to use a page vs. a file | Page | File | |---|---| | Content that's read in-place (FAQs, guides) | Documents meant to be downloaded or printed | | Content with rich formatting (images inline, embedded video) | Documents that exist as standalone PDFs | | Content that gets updated frequently | Fixed-version documents | | Content unique to PortalHQ (not also a downloadable doc) | Documents that also live as files elsewhere | A school's *Term Dates* page is best as a resource page — easy to update each year, easy to read on mobile. The *Year 7 Handbook* PDF is best as a file resource — printable, shareable, fixed-version. ## Creating a page Go to **Resources → Pages → New page**. ## Fields - **Title** — page heading. - **Slug** — URL-friendly version of the title. Auto-generated from the title; can be customised. - **Category** — which category the page belongs to. See [Organising resources with categories](/portalhq/articles/organising-resources-with-categories/). - **Content** — the page body. Rich text editor with formatting, headings, lists, images, embeds. - **Audience** — who can see the page. *Public*, *Parents*, *Students*, *Staff*, *Specific groups*. - **Active** — untick to retire. ## The content editor The editor supports: - **Formatting** — bold, italic, headings (H1-H4), bullet and numbered lists. - **Links** — to internal pages, external URLs or downloadable files. - **Images** — upload or insert from the file manager. - **Videos** — embed YouTube, Vimeo or similar. - **Tables** — for structured data. - **Code blocks** — for technical content. - **Quotes** — for testimonials, references. ## Linking from a page Pages often link to other resources: - **Internal links** — to other resource pages or file resources. Use the editor's link tool. - **External links** — to URLs outside PortalHQ. - **Anchor links** — to sections within the same page (useful for long FAQs). ## Embedding files For a page that points to a file: - **Inline link** — the file's name as a clickable link in the text. - **Button** — a styled button leading to the file. - **Preview** — for PDFs, an embedded preview that lets users read inline without downloading. Pick based on the user experience you want. ## Updating a page Open the page and edit any field. Changes apply immediately. The URL stays the same as long as the slug isn't changed. For substantial restructuring, consider doing it in a draft state: 1. Untick *Active*. 2. Make changes. 3. Test in preview. 4. Re-tick *Active*. This avoids users seeing a half-finished page. ## Versioning PortalHQ doesn't have built-in versioning for pages. To preserve previous content: - **Copy the page** before substantial edits, marking the copy as archived. - **Or export the page content** to a separate document. Most schools don't need versioning for resource pages — the current state is the source of truth. ## Audience and SEO Pages set to *Public* are publicly accessible at a URL like `/resources/pages//`. They can be indexed by search engines. If you want a page to be findable via Google, use *Public* audience and a descriptive slug. If you want it private, use any other audience. ## Tips - **Keep pages focused.** One topic per page. A 5,000-word mega-page is harder to navigate than five focused pages. - **Use headings.** Helps readers scan and supports anchor-link navigation. - **Embed images sensibly.** Don't paste 4 MB photos — resize first. - **Test on mobile.** Most parents read on phones. Check the page renders well on a small screen. - **Cross-link.** A page about *Camp Information* should link to the camp's resource files; the file should link back to the page.