Easiest
Ask the AI assistant
Visual
Content Editor UI
For developers
Code Editor directly
Pages vs CMS Collections
Before adding more pages, it’s worth knowing what kind of content belongs on a page versus in a CMS collection — they’re handled differently.| Use a website page for… | Use a CMS collection for… |
|---|---|
| Home, About, Pricing, Contact | Blog posts |
| Bespoke marketing landers | Products in a catalog |
| One-off layouts | Team members |
| Anything where the layout is the content | Testimonials |
| Case studies | |
| FAQs | |
| Anything that repeats with a shared shape |
hiveku.cms.json — see CMS Collections.
For repeating content like blog posts, products, or team members, use a CMS collection rather than creating a page per item. The CMS gives you a Webflow-style editor, version history, and search out of the box, and means a content team can manage entries without touching code. See CMS Overview and Collections.
Option 1: Ask the AI (Easiest)
Option 2: Content Editor (Visual)
Fill in the page details
- Title — shown in the browser tab and used as the default heading
- Slug — the URL path.
welcomeproduces/welcome - Meta description — used by Google and social previews
- Status — Draft or Published
Option 3: Code Editor (Developers)
Navigate to the pages folder
Depending on your framework:
app/— Next.js App Router (each folder with apage.tsxis a route)pages/— Next.js Pages Routersrc/pages/— Astro, Vite, Gatsby
Create the new page file
Right-click the folder and choose New File. Name it based on the URL you want —
app/about/page.tsx maps to /about.Understanding Slugs
The slug is the URL path for a page.| Slug | URL |
|---|---|
welcome | /welcome |
about/team | /about/team |
products/hats | /products/hats |
(empty or /) | / (homepage) |
our-story is better than OurStory.
Setting the Homepage
Only one page can be the homepage at a time. Setting a new one automatically demotes the previous homepage to a regular route.
Meta Title & Description
For SEO, every page should have:- Meta title — 50-60 characters, keyword-rich
- Meta description — 150-160 characters, compelling summary
Draft vs Published
- Draft — saved but not visible on the live site
- Published — visible to visitors after you deploy
Renaming a Page
- Content Editor
- Code Editor
Open the page in Content > Pages, change the Slug field, and save. Hiveku updates internal nav links automatically.
Deleting a Page
Verifying Changes
After creating, renaming, or deleting a page:- Check the live preview in the Editor — it reloads instantly
- Click Deploy to push the change to your live site
- Visit
https://{project}.hiveku.com/{slug}to confirm it’s live
Troubleshooting
Page isn't showing on the live site
Page isn't showing on the live site
You probably haven’t deployed yet. Click Deploy in the top bar. Pages appear in the preview immediately but need a deploy to go live.
The URL is different than I expected
The URL is different than I expected
Double-check the Slug field in the Content Editor, or the file/folder name in the Code Editor. Slugs with uppercase or spaces can cause unexpected URLs — stick to lowercase and hyphens.
Homepage didn't update
Homepage didn't update
Make sure you toggled Set as homepage for the new page. Only one page can be homepage at a time — check that no other page still has the toggle on.
Navigation links still point to the old page
Navigation links still point to the old page
What’s Next?
CMS Collections
Manage repeating content like blog posts and products
Post a Blog
Publish articles on your site
Edit Visually
Click and edit directly in the preview
Initialize CMS
Scaffold a CMS for repeating content