Create and publish your first website

What you will create #

You will create one website with a home page, working navigation, a deliberate mobile layout, page metadata, and a public Fronty URL. The goal is not merely to make the editor look finished. The public URL must show the same content, links, forms and data that you approved in preview.

Keep the first version small. A clear home page plus the few pages a visitor actually needs is easier to verify than a large generated site whose links and placeholder text have not been reviewed.

Create the website #

1. Sign in, choose the workspace that should own the website, and select New website.
2. Complete Starting point, Website details, Domain name, and Generate & launch.
3. At Starting point choose Prompt, Starter, Link, Screenshot, or Blank. Give the website a recognizable internal name.
4. Every new website begins on a .fronty.live address. A custom domain is connected after launch, even though the wizard asks about the name.
5. When generation finishes, open every created page before changing details. Confirm that the page list, navigation and primary action match the intended site.

Make one complete editing pass #

1. Replace placeholder names, prices, addresses, contact details and calls to action. Remove any section you cannot verify.
2. Open navigation links and buttons. Each should lead to a real page, section, file, email address or external destination.
3. Preview at a phone, tablet and desktop width. Check the header, menus, forms, tables, cards, modals and footer rather than only the hero.
4. Add a useful title and description to every indexable page. Add meaningful alt text to informative images and empty alt text to purely decorative ones.
5. If the site uses data, forms or item pages, add representative rows and submit the published form once before launch.

Preview, publish, and verify #

1. Save outstanding editor changes and open preview from the dashboard.
2. Run the readiness check and resolve blockers. Treat warnings and manual review items as work to inspect, not as automatic approval.
3. Publish with an account that has publish permission.
4. Open the public URL in a separate browsing session. Refresh it, follow the navigation, open an item page, and complete the primary action.
5. If a custom domain is connected, repeat the check on that hostname and confirm HTTPS is active.

Common first-launch problems #

The public page shows an older version

Confirm the editor finished saving before publish. Check that you opened the public URL rather than an old preview tab, then refresh once.

A page exists but cannot be reached

Add it to the intended navigation or link to it from another page. A page in the dashboard is not automatically useful to visitors.

The layout looks right only on desktop

Inspect the first width where it breaks. Fix stacking, overflow and fixed widths at the component that causes the problem instead of hiding the section.

Readiness is green but the experience is not

Automated checks cannot judge writing quality, business accuracy, complete keyboard behavior, every responsive width, or real-world performance. Complete the manual review items too.