How to build and publish a website in Gamma

The Gamma AI website builder can start a webpage from a creation conversation; the classic generator is also available through Use classic generator. Start with an approved site brief, then treat page review and publication as separate steps. Gamma’s creation guide↗ (opens in a new tab) establishes webpage creation, but does not establish the current controls for navigation, preview, domains, or publishing. Keep your site instructions and review findings in fenbs so you can continue the work on another device or with another AI.

Where do you start a webpage?

1. Write the site’s purpose in one sentence. Name the visitor and the action that person should take after reading.
2. Start a creation conversation in Gamma and ask for a webpage. If you want the documented classic flow, choose Use classic generator on the dashboard; Create New AI offers Generate, Paste, and Import there.
3. Give Gamma the approved source copy, desired page outline, and missing information. Keep unconfirmed claims visibly unresolved rather than asking for invented business details.
4. Review the draft’s content before planning publication. A generated page is a starting point for editing, not proof that the site is approved or publicly available.

For example, a local repair business might want visitors to understand its service area and request an estimate. Its brief should name the actual service area, the approved contact route, and the owner who checks the copy. A beautiful page with an invented coverage area still fails the job.

If you are choosing a website tool before creating anything, use the broader AI web creators guide. Here the task is to make the Gamma draft reviewable and know what remains before it can go live.

What should the site brief contain?

Give the page enough real material to answer a visitor’s questions. Separate facts that must remain exact from wording that can change. Put business names, service boundaries, contact information, and approved claims in the first group; headings and introductions can usually be revised more freely.

• Audience: who arrives, what they already know, and what they need to decide.
• Goal: one main action, such as reading a service description or using an approved contact link.
• Content outline: the purpose of each proposed page or section, with its source copy.
• Navigation plan: the labels visitors should understand and the intended destination for each link.
• Review boundary: who can approve copy, images, contact details, and the final public version.

A navigation plan is a content plan until you have confirmed the actual site controls. Do not describe a list of requested pages as a working multipage site. Likewise, a written domain preference does not mean that domain is connected. Keep each of those as a separate check with a clear result.

Keep the approved brief beside the outstanding work in fenbs. The next session can see the visitor’s goal and the unanswered checks together, instead of mistaking a polished draft for a finished website.

How do you review pages and navigation?

Review one visitor journey at a time. Start at the first page someone would see and follow the route to the intended action. Read every label literally: would a first-time visitor know what opens next? Record the page or section, the problem, and the proposed correction.

These are checks to perform on the resulting page, not claims about a particular Gamma preview control. If you cannot inspect an intended page or follow a link, leave that item unfinished. Do not replace missing evidence with a screenshot of the editor or a teammate’s assumption.

What must be confirmed before publishing?

The cited creation documentation does not provide a verified current click path for publishing, unpublishing, domain setup, or page navigation. Confirm those controls in Gamma’s own current product guidance before taking a draft public. This guide cannot safely supply a menu name or promise which account includes a domain feature.

1. Identify the exact version the owner approved. Note any changes made after that review.
2. Confirm the intended public address and who is allowed to publish there. Keep this separate from permission to edit the draft.
3. Verify how the current publishing control changes visibility and how you would reverse an unwanted publication.
4. After an authorized publication, open the public address and repeat the visitor journey. Record the actual result rather than the intended result.

An exported presentation is a different deliverable. Gamma’s export documentation↗ (opens in a new tab) covers PDF, PNG, and PowerPoint; it does not make an export evidence of a hosted website. Use the separate Gamma saving guide when the deliverable is a downloaded deck.

What should you save after the review?

Save the accepted brief, the draft link, the approved version, and a short list of unfinished checks. Include the reason for important choices. “Keep one contact action because visitors were missing it among three options” gives the next editor a useful boundary; “make it cleaner” does not.

Keep a precise publication status: draft only, approved but unpublished, or published and checked at the recorded address. Add who approved it and what they approved. A later AI should be able to tell whether it may suggest copy or whether a person still needs to authorize going live.

For the wording that starts the draft, see writing a useful Gamma prompt. More guides to these everyday checks live in the AI at work hub.

How to keep your site review with fenbs

Keep the work so you can carry on from exactly where you left off, on any device and in another AI. You only need the accepted brief and the next useful check, not every abandoned line of copy.

1. Create a free account.
2. Add a task for the website. Write who it is for, what it should help visitors do, and where the draft is.
3. Save the owner’s approved choices and the page checks that passed. Say plainly which publishing or domain checks remain.
4. Before stopping, write the next step. Ask your next connected assistant to read that record before suggesting another change.

fenbs keeps your site instructions, decisions, and progress; it does not publish or host your Gamma website. If all you need is a single page and you will finish in one sitting, a separate work record may add little. It helps when review crosses sessions, devices, or people.