AI Page Builder for Project Pages: Design From a Prompt

Building a team home page the old way means opening a blank canvas, dragging in a section, dropping in a text block, resizing a column, and repeating that six or seven times before there's anything worth showing anyone. Onplana's page builder still has that canvas, but it now has a second way in: describe what the page is for, and a full draft appears with sections, content, and live project data already arranged.

The direct answer: Onplana's AI page builder is a Professional-and-above feature that turns a one-line prompt into a complete web part page, sections, content blocks, and live-data widgets, ready for review before anyone but you sees it. It works from the new-page dialog, where you describe a page before it exists, and from inside the editor of a page that already exists, where you can ask it to add a section or reorganize the layout.

What the AI Page Builder Actually Generates

A prompt like "build a project overview for our Q4 website redesign" produces a page assembled from the same component library a person drags in by hand: headings, text, callouts, dividers, and spacers for content; images, buttons, quick links, and embeds for media and navigation; and live-data widgets, stats cards, task status charts, milestone timelines, and activity feeds, that pull real numbers from the project instead of a screenshot someone has to update manually. The Onplana docs describe the output as "the same page building blocks a person would use," which is the operative detail: the AI isn't producing a special AI-only page type, it's operating the same canvas at prompt speed.

How Building a Page From a Prompt Works

The path from prompt to a page other people can see has four steps, and only one of them belongs to the AI:

1. Describe the page. In the new-page dialog, choose "Design with AI" and write what the page is for and who it's for; from inside an existing page's editor, ask for a specific change instead, like adding a milestones section.
2. Review the draft. The AI proposes a full layout with sections and content already filled in; nothing is visible to anyone else yet, because a page's draft and its published version are two separate states.
3. Edit what needs it. Rearrange blocks, rewrite copy, swap a stats card for a different widget, or ask the AI to restyle a specific section, all on the same canvas a hand-built page uses.
4. Publish. Publishing creates a version snapshot and gives the page a stable URL; the page moves from "what you're editing" to "what readers see."

The diagram above shows why publishing has to stay a distinct, human step: three of the four boxes happen entirely inside a draft that nobody outside the editor can see.

Where a Generated Page Lives: Organization or Project

Scope	Typical page	Who sees it
Organization	Team home, links hub, policy or template index	Everyone with organization access, or a restricted group
Project	Project overview, FAQ, status hub	Members of that project

Prompting works the same way at both levels; the only difference is where the page is created and, therefore, its default audience.

Can You Trust What the AI Publishes?

Yes, in the specific and narrow sense that matters: the AI never publishes anything itself. A generated page always lands as a draft, the same draft state a hand-built page starts in, and Onplana's own product documentation describes the workflow as proposing changes for a person to review before they're applied, not applying them directly. The riskier failure mode isn't a rogue publish, it's a plausible-looking draft that nobody actually reads before clicking publish themselves, which is a human process gap the tool can't close on its own. Treat an AI-generated page the way you'd treat a page a new hire built: read it before you ship it.

AI Page Builder vs Building Pages by Hand

The AI path and the manual path aren't two different products, they're two ways into the same custom pages canvas. Prompting is faster for the first draft of a page type you've built before: a links hub, an FAQ, a status page. Building by hand still makes sense when a page is unusual enough that describing it in a sentence would take longer than dragging in the three sections you actually need. Most teams end up doing both: prompt the skeleton, then hand-edit the parts that are specific to this one page.

The pattern isn't unique to pages. Generating a full project plan from a prompt works the same way, structured output a person edits before it's real, and the same trust question applies in both places: review the draft, don't skip the step where a human decides it's actually ready.

If your team already builds links hubs or FAQs by hand, try prompting the next one instead of building it block by block. The AI page builder ships on Professional and above; see what else shipped this year on What's New, check plan details on Pricing, or browse the rest of the Onplana blog for how other teams are using pages.