Page formats and content transfer

Choose a format according to what you want to publish. A page has a title, a public URL and an editable draft. Saving changes the draft; publishing includes it in a complete public release. Follow editing pages for the browser controls.

Choose a page format

Markdown and visual pages keep their own formats until you explicitly choose Convert to HTML or Convert to Markdown. Conversion operates on current draft content and retains the page's identity and metadata. HTML-to-Markdown conversion warns about loss of styles, fine details, blocks and dynamic bindings. Review the result before saving; publication is a separate action.

Markdown features

Use headings, bold/italic/strikethrough, lists, task lists, links, images, tables, quotes, code blocks and dividers. Task boxes can be changed in the editor; published checkboxes display their saved state. Visual and Source modes edit the same text. Switching modes preserves source; visual changes can normalise its Markdown syntax. Keep unsupported syntax in Source mode when the editor asks you to do so.

Headings receive stable IDs in previews and published pages, so links can target sections with fragments such as #markdown-features. IDs use lowercase heading text, replace spaces with hyphens and omit punctuation while preserving Unicode letters, digits, underscores and hyphens. Repeated IDs receive -1, -2 and subsequent available suffixes. Links to other pages must use their public URL, including the trailing slash before a heading fragment.

Transfer a Markdown file

Upload .md accepts UTF-8 text up to 1 MiB and replaces the selected draft's text after any required confirmation. Upload referenced images separately to the media library. Download .md exports the current text, including unsaved edits and menu directives. Use storage backups to protect the complete editable site.

For automated Markdown and HTML updates, use content uploads.

Page URLs and generated indexes

Use / for the homepage and paths such as /about/team for other pages. Segments start with an ASCII letter or digit, contain ASCII letters, digits, dots, underscores or hyphens, and are at most 128 characters long (2000 for the full path). Filename extensions such as /docs/overview.md are allowed; pages still publish as HTML at /docs/overview.md/. The /api/assets and /theme-assets namespaces, the generated root filenames /sitemap.xml, /robots.txt and /release.json (including descendants), and every index.html segment are reserved. Review existing links when changing a URL and arrange redirects with your administrator.

A Markdown paragraph containing {{index}}, or a visual Site → Index block, lists direct URL children in title/URL order with a short summary. Menu parents and visibility are separate from URL hierarchy. Save the child pages before previewing, and publish again when the listing needs to change.

Publication state

Enabled for publication controls whether a saved page appears in the next release. Disabled pages remain editable and previewable, but page output, navigation, indexes, repeaters and sitemap omit them. The setting does not cascade to descendants. See publication controls.

Featured images

A page can select one image from the media library with an independent alt text description. Themes can display it through the Featured image binding; visual pages and Repeat files templates can insert the Featured image block. Missing images produce no block markup. Selection is saved as page metadata, not embedded into Markdown source. See page properties.

Themes and publication

The selected theme supplies shared layouts, navigation, headers, footers and styles. Keep page content in the page editor and shared design in Themes. Preview renders the current page privately; publication builds from the saved site. See themes, media and publishing for the next steps.