Start with one real page. GoRun brings content, design and team access together, but your team still decides what should be published.
1. Give the page a specific job
Write down who will read it, what question it answers and what action should follow. Gather the approved text, images, links and source material before opening the editor. A starter design provides structure; its demonstration content is not evidence about your organization.
2. Prepare the content and design separately
Create a draft and choose a suitable template or supported page-builder sections. Set the page title, slug and summary. Add images with useful descriptions, then check the menu and related links. A theme controls appearance; it does not create or approve the content for you.
3. Review as a reader
- Read the draft in both wide and narrow layouts.
- Check headings, dates, contact details, image permissions and source links.
- Open each primary action and confirm where it leads.
- Check the intended language and its related translation before publishing.
4. Keep editing and publishing responsibilities clear
Give each team member the access needed for their task. Review the actual role and site policy before giving them publishing or integration access. An AI-generated draft needs the same editorial review as any other draft; a private canvas result is not a published page.
5. Check the public result
After publishing, open the public URL outside the editor. Confirm the title, layout, links and navigation. Submit only an appropriate test through a form you control, and verify its actual destination before relying on it for visitors.
A reusable acceptance checklist
- The page answers its stated question.
- Images, links, language and metadata have been reviewed.
- The right people can edit; unintended people cannot.
- The published URL renders correctly and points to a useful next step.