Every guide opens with the answer, then shows the shortest correct path to it. No preamble, no tour of features you did not ask about.
How do you add a visual page editor to a Next.js app?
Install the pagiera package, point it at PostgreSQL and Redis, mount its catch-all API route under /api/pagiera, load the editor bootstrap on the server, and render the studio behind your own authentication. The editor runs inside your application rather than on a separate hosted account, so the pages it produces are rendered by your own Next.js server.
How do you bind live API data to a page in Pagiera?
Add a Request block to fetch one object or a Repeat block to iterate an array, then reference route parameters and query fields inside the URL, headers or body using {{params.x}} and {{query.x}} placeholders. For published pages both resolve on the server before HTML is returned, so API-backed content is present in the initial response rather than filled in afterwards.
Does saving a page in Pagiera make it public?
No. Saving updates the draft only. You preview the draft on a preview route, and the page becomes public only when you publish it. The home slug maps to /. Publishing updates the page content — it does not deploy your host application or configure a domain.
Can an AI coding agent build a website you can still edit visually?
Yes, if the agent creates native Pagiera document elements instead of a separate hardcoded page. The package ships an AGENTS.md integration guide for exactly this. A document produced that way can be saved, opened in the visual editor, previewed and published like any other page — which is what keeps the result editable after the agent finishes.
How do you avoid rebuilding navigation and footers on every page?
Design the shared structure once as a linked layout and place a children placeholder where page-specific content belongs. Pair that with reusable components and variants for the smaller repeated pieces. Every page that uses the layout inherits changes to it, so a navigation edit happens in one place rather than on every page.
Can you use Pagiera as a CMS for a Next.js site?
Yes, for pages. Pagiera stores every page as a document in your own PostgreSQL database, separates drafts from published revisions, and gives non-developers a visual editor to change them — the job a CMS does. It is not a headless CMS in the content-modelling sense: instead of defining collections and querying them over an API, pages bind to the APIs you already have. Nothing leaves your infrastructure and no CMS service sits in the request path.
The documentation renders the package README and the coding-agent integration guide, synced from the official repository.
Guides are the short versionInstall the complete visual builder, choose a starting point and shape it into something unmistakably yours.
