Creating and editing pages

Start with getting started for sign-in and a first publication. A page has a stable internal ID, a title, a URL path and editable content. Changing its title or path does not create a different ID. The page list includes saved pages regardless of whether they appear in navigation.

Choose a format

Use Convert to HTML to turn a Markdown draft into a visual page that accepts blocks. Convert to Markdown extracts text, links, images and common formatting from an HTML draft. It warns that fine details, styles, layout blocks and dynamic bindings may be lost. Conversion uses your current edits and keeps the page ID, URL, menu, layout and featured image. Review the result, then Save draft; conversion alone does not change the saved page or public website. Keep a backup before converting a complex page. Raw objects and renderer pages cannot use this conversion. Automation can also explicitly replace formats at a URI; see content uploads.

Installed page-type packages add a separate Page type choice and properties. For Blog creation, dated URLs and conversion, see Blog posts.

Titles, paths and collisions

The title labels the page and generated menu link. The path is the part of the public address after the hostname: /about/team becomes https://example.com/about/team/. Use / for the homepage. Each path segment must start with a letter or digit and contain only ASCII letters, digits, dots, underscores or hyphens, up to 128 characters per segment and 2000 characters for the full path. Spaces, full URLs and accented/percent-encoded paths are rejected. Filename extensions are allowed: /docs/overview.md becomes https://example.com/docs/overview.md/. It is still a rendered HTML page; the URL extension does not select the content format or download the source.

The /api/assets and /theme-assets namespaces are reserved, as are the generated root files /sitemap.xml, /robots.txt and /release.json and their descendants. The segment index.html is reserved at every level for generated page output.

Only one page can own a normalized path. When a collision is reported, choose a different path or use the explicit overwrite confirmation after reviewing the existing page. Overwriting can discard another page's content. When changing a URL, arrange redirects with your administrator for bookmarks and external links to the old address.

Markdown editing

Visual provides headings, bold, italic, strikethrough, inline code, quotes, bulleted/numbered/task lists, links, images, tables, code blocks, dividers and undo/redo. Task boxes can be changed while editing; published checkboxes are disabled because the public site has no editable state.

Source shows ordinary Markdown, for example:

# Our team

We write **useful guides**. Read [About](/about/).

- [ ] Review this draft
- [x] Add a title

Switching modes alone preserves source. Visual edits can normalize Markdown syntax. Unsupported syntax, such as raw HTML, front matter, footnotes and custom directives, stays in Source mode; it is not executable content. YAML front matter is not page metadata. Menu directives are a separate, supported leading-block syntax.

Upload .md accepts UTF-8 Markdown up to 1 MiB and replaces the current draft's text after confirmation when needed. It does not upload files referenced by image links. Download .md exports current text, including unsaved changes, and current menu directives. It is a single-page source export, not a site backup.

Visual layout editing

Select content on the canvas, then type to edit text. Use Blocks to insert sections, columns, cards, text, images, lists and tables. Layers shows the nested structure; select a parent there when a small child is hard to select. Styles changes appearance and Properties changes the selected block's attributes. Hover icon controls to see their label: undo, redo, duplicate, select parent, delete, source editing, outlines and fullscreen.

In Styles → Extra, adjust vertical alignment, cursor, horizontal/vertical overflow, visibility, text overflow, word breaking, overflow wrapping and text selection, alongside opacity, transitions and transforms. Vertical alignment applies to inline elements and table cells; use flex alignment for flex containers.

HTML and CSS are available through the source control for advanced editing. Scripts, embedded applications and unsafe markup are sanitized; pasted code is not a supported way to add executable features. The chosen site theme wraps page content. Its shared header/footer appear around the page but are edited in Themes, not by changing each page's content.

Enable or disable publication

Pages are Enabled for publication by default. Clear that checkbox above the editor (or in Body → Properties) and save the draft to disable a page. Disabled pages stay in the page list with a Disabled label and can still be edited and previewed. On the next publication their page URLs disappear from the active site, navigation, indexes, repeaters and sitemap. Enable and publish again to restore them.

This affects the selected page only; descendants remain enabled independently. Enabled menu children of a disabled parent appear at the top level. Ordinary links you wrote are not rewritten, so review links to pages you disable. Existing public releases keep their previous content until replaced or removed by retention; reactivating an older release also restores its old publication state. Uploaded media is managed separately and remains available in publications.

Featured images

Upload an image with Media. On an HTML page choose Page properties (or select Body in Layers, then Properties) and set Featured image and its Image description (alt). On Markdown and other source pages use the featured image controls above the editor. Choose No featured image to clear it.

The image belongs to the page independently of its content. A theme can render it as a cover; Site → Featured image inserts it into a visual page or a Repeat files card template. The block produces no markup when the page has no featured image. Repeat files uses each listed page's image. Save the image selection and publish to update the public site. Clear or replace a saved selection before deleting that media item. A downloaded .md file does not carry this metadata.

Save, preview and delete

Save draft commits to CMS storage. Preview renders current page changes without making them public. Previews use the publication renderer; responsive widths simulate layout sizes, not every property of a real mobile device. Other pages used by a preview come from their saved drafts.

Deleting a page removes its editable draft. The public copy remains in the active release until another publication. Deleting a menu parent promotes its children to the top level; deleting one page does not imply deleting its URI descendants. Check links and menu placement after deletion. Retained public releases can be reactivated, but rollback does not restore deleted drafts.

Page formats and content transfer are explained in the content reference. For public behaviour use publishing; for uploaded images use media.