> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wpos.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Build a page

> The page-by-page workflow agencies use to ship a site with WPOS: one page right, then the next.

WPOS works best the way a good designer works: get one page right, then carry that
look across the rest. This page describes the workflow agencies actually use to
ship client sites.

## Work one page at a time

Do not ask WPOS to build a whole site in a single instruction. Get the **homepage**
exactly right first. Once it is right, move to the next page, and the next. Each
page is faster because the look is already settled.

<Steps>
  <Step title="Start with the homepage">
    Build and refine the homepage section by section, clicking each element in the
    preview and asking for the change. See [The Command Center](/operate/command-center).
  </Step>

  <Step title="Lock the look">
    Get spacing, type, and brand right on the homepage. This becomes the reference
    for every other page. See [Styling and brand](/operate/styling).
  </Step>

  <Step title="Move page by page">
    "Let's move on to the next page." Apply the same look to the about page, the
    services page, and so on, one at a time.
  </Step>

  <Step title="Wire up the functional pieces">
    Add the forms, the lead capture, and any tools the site needs. See
    [Forms](/operate/forms) and [Connectors](/connect/connectors).
  </Step>
</Steps>

## Reuse the client's existing content

If you are rebuilding or restyling an existing site, keep the client's words. Tell
WPOS to pull the content and images from the current site and only redesign the
layout, rather than rewriting copy you did not want touched.

```text theme={null}
Rebuild this section using the design we just made, but keep the exact copy and
images from the existing page at https://theirsite.com/about.
```

<Tip>
  Be explicit that the copy stays word for word. WPOS will happily rewrite text if
  you do not tell it to preserve it.
</Tip>

## Review on staging, then go live

Build and review on your staging or preview URL first. When a page is right,
publish it. After launch, do a quick pass to confirm everything moved over.

<Steps>
  <Step title="Review on staging">
    Walk the page on the preview URL. Check the layout, links, images, and mobile.
  </Step>

  <Step title="Go live">
    Publish when you are happy. Ask WPOS to push the page live.
  </Step>

  <Step title="Post-launch check">
    Confirm the live URLs resolve, the forms submit, and any redirects work. See
    [Forms](/operate/forms) for testing submissions and thank-you redirects.
  </Step>
</Steps>

<Note>
  Lead generation and a working contact path are usually the highest priority on a
  client site. Test the form and its redirect before you call a launch done.
</Note>