Your First Page

Creating and publishing your first page takes four steps: write it, preview it, build, and check the live site. This page walks the whole path so it’s clear what happens at each stage.

Step 1: Write the page

1. In the admin area, open Pages → New Page.
2. Fill in a title: the page’s headline and what readers will see as the H1.
3. Write the body in the rich-text editor: type normally, use the toolbar for headings (H2–H4), lists, and links, insert images from the media library, and embed reusable blocks if you’ve created any.
4. Set the rest in the side sections when you’re ready: SEO description and social-share fields, sitemap settings, scheduling, and an optional page password.
5. New pages are saved as drafts: the page exists, but readers don’t see it. Long writing sessions are safe: your work auto-saves as a server-side draft, so a closed browser doesn’t lose anything.
6. Optional: use a block shortcode via the editor’s Insert Block picker to reuse a CTA, quote, or gallery.

Your page can be saved and re-edited as many times as you like; nothing goes live until both it is published and the site is rebuilt.

Step 2: Preview

Two ways to look before you publish:

• Preview (edit screens): the Preview button renders the page with your real theme, including the latest edits and even draft blocks, without saving anything. It requires being signed in as an admin.
• Shareable preview link: the edit screen can produce a private preview URL you can paste to a colleague or client; anyone with the link sees the page without logging in. The link is revocable: regenerate it to kill the old one.

Step 3: Publish and build

Publishing is a switch on the page (Save & Publish, or from the pages list, including in bulk). But a published page stays invisible until a build writes the static site:

• Click Build on the dashboard (or save/publish from the editor, which queues a build automatically).
• Choose “Full rebuild” if the site seems out of sync or a theme change needs everything regenerated; normal builds are incremental and fast.
• If a build is already running, the app says so rather than starting a second; you’ll see a clear “in progress” message.
• The dashboard shows live progress: which pages are done and what’s currently being written. A build history with outcomes and durations sits alongside.
• First-time saver note: a promotion guard runs before each build comparing your site’s metrics; if the change looks risky, promote anyway (or read the guard’s report first).

Build logs record every outcome; on failure the previous site keeps serving until a build succeeds.

Step 4: See it live

• The pages list offers a View link built from the actual URL for the current language and URL mode. Click it after the build completes to see the page on your site.
• The page now lives as a plain file on disk under the output directory, served by your web server. Publishing also fires your configured “publish” webhook if you’ve set one (useful for search indexing and social previews).
• Try the rename: edit the page slug and rebuild: old URLs keep working via an automatic redirect.

Continuing from here

Your first page is a draft-to-live loop, and everything else builds on it:

• Editing later works the same way: the editor, preview, rebuild cycle (see The Editor).
• Translated versions are per-language records of the same idea (see Translating Content).
• Pages vs posts: posts add categories, dates, and the blog index; pages are standalone with hierarchical parents.
• CDN or caching: static files mean caches can keep serving visitors the moment a build completes; site updates typically reach readers within minutes.

The short version

Write it, preview it using the real theme, hit Publish, build; your first page is live at its permalink URL, and every edit afterwards is another safe rebuild away.