Skip to content

Managing Pages

Pages are the building blocks of your guidebook. Each page contains a title, a URL slug, rich-text content, an optional header image, and a FontAwesome icon. Pages are organized in a nested tree structure up to 10 levels deep, letting you create a logical hierarchy that is easy for guests to navigate.

Adding a new page

  1. Open your guidebook from the Guidebooks section.
  2. Click "Add Page" to create a new page.
  3. Fill in the page fields (described below).
  4. Click Save to add the page to your guidebook.

Page fields

Every page has the following fields:

FieldDescription
TitleThe page name shown in the navigation menu and at the top of the page (e.g., "House Rules", "Kitchen").
SlugA URL-friendly identifier generated from the title. You can customize it. Slugs must be unique within the same parent level.
Short descriptionA brief summary shown on page tiles and in the navigation. Keep it to one or two sentences.
Body (HTML)The main content of the page, written in the rich-text editor.
Header imageAn optional banner image displayed at the top of the page. Uploaded images are automatically compressed and optimized.
IconA FontAwesome icon displayed next to the page title in the navigation menu (e.g., a bed icon for "Bedroom", a utensils icon for "Kitchen").

Using the rich-text editor

The content editor is powered by Quill.js and supports a full formatting toolbar:

  • Bold, italic, and underline -- Emphasize important information like door codes or WiFi passwords.
  • Headings (H1 through H3) -- Break longer pages into sections with subheadings.
  • Bullet and numbered lists -- Perfect for step-by-step instructions or checklists.
  • Links -- Add hyperlinks to external resources, maps, or booking platforms.
  • Images -- Upload photos directly into the content body. Images are compressed automatically for fast loading.
  • Blockquotes -- Highlight important notes or callouts within the content.

All content is sanitized on the server before being saved. Script tags, iframes, embedded objects, form elements, and event handler attributes are automatically stripped to keep your guidebook safe and clean.

TIP

Add a header image to your pages for a polished look. A good header image -- such as a photo of the kitchen for the "Kitchen" page or a beach photo for a "Nearby Beaches" page -- makes the guidebook more inviting and easier to browse. Uploaded images are automatically compressed to an optimized size.

Organizing the page tree

Pages are arranged in a nested tree structure. You can create parent pages with child pages underneath them, building a clear content hierarchy up to 10 levels deep.

For example:

  • Welcome
  • House Rules
  • The Property
    • Kitchen
    • Bathroom
    • Living Room
    • Garden
  • Getting Here
    • By Car
    • By Public Transport
  • Checkout Instructions

Reordering pages

To change the order of your pages:

  1. Open the layout editor to view the full page tree.
  2. Drag and drop pages to reorder them within the same level.
  3. The new order is saved automatically.

You can also use batch reorder to rearrange multiple pages at once.

Nesting pages (moving to a parent)

To nest a page under another page:

  1. Open the page you want to move.
  2. Use the "Move to parent" option to select a new parent page.
  3. The page becomes a child of the selected parent.

The system includes cycle detection to prevent you from accidentally creating infinite nesting loops (e.g., Page A inside Page B inside Page A).

WARNING

Nesting pages changes their URL path. A page called "Kitchen" nested under "The Property" in a guidebook with slug "beach-house" will have the URL /{guidebook-slug}/the-property/kitchen/. If guests have bookmarked the old URL, it will no longer work after you move the page.

URL path structure

Each page's public URL follows the full path of its ancestors:

/{guidebook-slug}/                              -- Guidebook home
/{guidebook-slug}/{page-slug}/                  -- Top-level page
/{guidebook-slug}/{parent-slug}/{page-slug}/    -- Nested page

Slugs must be unique within the same parent level. Two pages at the top level cannot share the same slug, but a top-level page and a nested page can have the same slug because they are at different levels in the tree.

When you change a page's slug, the full URL path is automatically rebuilt for that page and all its descendants.

Page visibility options

Each page has several toggles that control how it appears in the guidebook:

ToggleEffect
Published / DraftDraft pages are not visible to guests even if the guidebook is live. Use this to prepare content before making it visible.
HighlightHighlighted pages are emphasized in the navigation, making them stand out as featured content.
Show in infoWhen enabled, the page appears in the Info section of the guidebook (if the Info navigation item is turned on).
Hide from menuThe page still exists and is accessible via its URL, but it does not appear in the navigation menu. Useful for pages you only want to link to from other pages.

These toggles give you fine-grained control over what guests see. For example, you might keep a "Staff Only" page as hidden from the menu but link to it from another page that only certain people receive.

System pages

Guidebooks can include three system pages that are auto-generated based on your guidebook settings:

System pageContent source
InfoPulls from your guidebook's general information, or from a specific page you assign as the info page.
NearbyPowered by your Local Guide content -- shows categories, locations, maps, and a featured items carousel.
EmergencyDisplays the emergency contacts you configured in the guidebook settings (emergency number, police, hospital, pharmacy, dentist).

System pages are controlled by the navigation toggles in the guidebook settings (Show Info, Show Nearby). You do not need to create them manually -- they are generated from existing data.

Duplicating pages

To quickly create a new page based on an existing one:

  1. Open the page you want to duplicate.
  2. Click the Duplicate option.
  3. A copy is created with the title prefixed by "Copy of" (e.g., "Copy of House Rules").
  4. The duplicate gets a unique slug that does not conflict with the original.
  5. Edit the duplicated page to customize it.

Duplicating is useful when you have a page template you want to reuse -- for example, creating similar room description pages for multiple bedrooms.

Translating pages

Guidebooks support translations in 22 languages: English, Dutch, German, French, Spanish, Italian, Portuguese, Polish, Czech, Danish, Swedish, Norwegian, Finnish, Russian, Chinese, Japanese, Korean, Turkish, Greek, Hungarian, Romanian, and Ukrainian.

How the translation editor works

  1. Open the page you want to translate.
  2. Switch to the Translations tab.
  3. You will see a tab for each language. Select the language you want to add.
  4. Fill in the translated title, short description, and body content for that language.
  5. Save the page.

Each translation is stored independently. You can translate as many or as few languages as you need -- you do not have to translate every page into every language.

Auto-detect used languages

The system automatically detects which languages are in use across all pages in a guidebook. This is used to:

  • Show language options to guests in the published guidebook.
  • Help you track which pages still need translations.

If a page does not have a translation for a guest's language, it falls back to the default language (English).

TIP

Start by translating your most important pages -- Welcome, House Rules, and Check-out Instructions. These are the pages guests are most likely to read and where language barriers matter most.

Editing and deleting pages

  • To edit a page, click on it in the page tree and make your changes in the editor. Click Save when done. Changes to published pages are reflected immediately in the live guidebook.
  • To delete a page, open it and use the delete option. If the page has child pages, you will need to move or remove them first.
  • To upload or replace a header image, use the image upload area on the page editor. To remove a header image, click the delete button on the current image.

hejGuide Property Management System