Get started
Your first site.
Ready for real clients.
Ask your agent to set up your workspace, customize the site, and help put it online. Follow each step below, or switch to manual commands if you prefer.
01 · Create a site
Start with a site you can make your own.
Ask your agent to set up Primo on your machine and help you choose a marketplace starter or a blank site. Decide where to host it when you’re ready.
Help me create my first Primo site. Read https://docs.primo.build/getting-started/quickstart and check the installed CLI help. Ask what kind of site I need and help me choose a marketplace starter or a blank site. Check Node.js, install the Primo CLI if needed, then initialize a new workspace with primo init before creating a site. Offer to connect the Primo MCP tools to my agent. If I choose a starter, guide me through the actual marketplace import flow. Start the local server in file authoring mode and show me the working preview and editor URLs.
Starts with Node.js and the CLI installed. Use the setup prompt or CLI instructions to install them first.
Read the walkthrough steps
- With Node.js and the CLI installed, create a workspace. This demo skips MCP setup.
- Inside the workspace, create a site. --skip-dev leaves starting the server to you.
- Validate the site files before starting Primo.
- Run primo dev --author files. Open its editor URL: Browse mode keeps local files authoritative.
- Stop with Ctrl+C, then run primo dev --author cms to edit in the browser.
02 · Make it yours
Shape the design. Edit the content.
Ask your agent to change the layout, components, and content. When you want to edit visually, ask it to open Primo in browser editing mode.
- Replace the starter content with your own.
- Check the site on a phone as well as a desktop.
- Create the page types and fields your client will need.
Help me customize this Primo site. Read the workspace AGENTS.md and use the Primo MCP docs if available. Ask about the design and content, update the source in file authoring mode, and check desktop and mobile layouts. Create the page types and editable fields my client needs, and validate the changes. When I’m ready to try the visual editor, stop only this workspace’s dev server and restart it with primo dev --author cms. Open the editor URL printed in the terminal. Explain how to switch back to file authoring before making more source edits.
Read the walkthrough steps
- A complete site, ready for your content.
- Click the headline and make it your own.
- Replace a photo directly on the page.
- Create a blog post from a reusable page type.
- The same design, with this post’s own content.
- Arrange the homepage with reusable blocks.
03 · Put it online
Give the site a home—and an editor.
Ask your agent to deploy an editable Primo server and verify the published site. Choose a hosted plan or use your own hosting account.
Deploy your workspace to your Railway account, including the browser editor and persistent storage.
Help me deploy this Primo workspace as an editable CMS on Railway. Read https://docs.primo.build/cli/deploy and check the current CLI help. Confirm the hosting account, expected costs, and which sites in this workspace should be deployed. Install the provider CLI if needed and guide me through signing in privately. Run primo deploy -p railway --dry-run, then, after I approve the plan, deploy from the folder containing server.yaml. Verify persistent storage at /app/pb_data and wait for the server to be healthy. Check that the workspace upload succeeded; if needed, guide me through Primo login and retry primo push. Verify the site’s assigned hostname and DNS/HTTPS, publish the intended site after I approve, and check its public URL and editor at /admin. Keep passwords and tokens out of the conversation.
Primo is free to self-host. Your hosting provider bills separately.
Only need a static website?
Ask your agent to export the site with primo build and deploy the output to your static host. You can also run the command from the site folder yourself. To give clients a browser editor, deploy the CMS instead.
This manual Railway example shows the infrastructure that primo deploy sets up for a workspace. CLI screens use captured command output; waiting and credential entry are omitted.
Read the walkthrough steps
- Create a Railway project. CLI commands in this walkthrough use the linked demo project and service.
- Add an empty service for Primo.
- Before deploying, attach persistent storage at /app/pb_data. Verify the mount path.
- Configure Primo account variables privately. This excerpt hides passwords; normal variable output contains secrets.
- Connect the service to the published Primo image. This demo pins the 3.3.1 image digest.
- Wait for the service deployment to report SUCCESS. The waiting period is omitted here.
- Generate a Railway hostname on port 8080. Railway supplies DNS routing and HTTPS for this address.
- Open /admin/dashboard over HTTPS. Sign in with the regular Primo account, not the PocketBase superuser.
- The fresh CMS is ready for sites. Credential entry is omitted from this recording.
Ready for the handoff
Hand it over. Keep building.
Ask your agent to help prepare the handoff: page types, editable fields, and a short client guide. Your client edits at /admin; visitors see the published site at the root.
Help me prepare this Primo site for my client. Review the page types and editing fields, and show me how to invite them with the appropriate access. Write a short guide for editing content, creating pages, and publishing, using this site’s actual editor and public URLs. Let me approve any invitation or access changes before they are sent.