Content model
Define the page types, fields and relationships before design. A service page, a case study and a guide need different structures and different review steps.
Next.js development for websites your team can run.
A code-based website built from your content model and reusable components, with editing, integrations, hosting and handover agreed before the build.
New website builds / Content model / Handover
The scope
Model the content.
Then build the parts.
A new build starts with how content is structured and edited, not with a framework choice.
Plan the pages before the designNext.js is a React framework for building websites in code. It suits a project that needs reusable components, custom integrations or close control over how pages render. It also means changes are made by people who work in code, unless an editing workflow is set up for your team.
A business planning a new website, with an owner who can approve the offer, content and operational requirements. If the current site mostly needs clearer pages or a working form, start with improvements instead.
Reusable components
Build sections from a shared set of components and design tokens. New pages reuse tested parts instead of copying layouts that drift apart.
Responsive design
Design for phone and desktop together. Check content, navigation, forms and controls on phone-sized viewports, not only on a desktop mockup.
Editing workflow
Agree who edits what, and where. Content can live in a CMS, in code changed by a developer, or both. The choice affects cost and how fast pages change.
Integrations
List each tool the site must connect to, such as analytics, a CRM or a booking system. Supported integrations are confirmed per project and tested end to end.
Hosting and handover
Agree where the site runs, who pays for hosting and who deploys changes. The handover records who owns each part of the running site.
Deliverables and inputs
What you receive.
What we need from you.
Both lists are agreed before the build starts, so responsibilities are clear on each side.
How delivery worksWhat you receive
- An agreed sitemap, page types and content model
- Responsive templates built from a shared component library
- A documented editing workflow, tried with your team before launch
- Agreed integrations, tested end to end with named owners
- A launch checklist covering search, forms and user journeys
- A handover covering hosting, updates, maintenance and recovery
What we need from you
- An owner who can approve the offer, page content and priorities
- Approved copy, images and evidence, or time to review drafts
- Access to the domain, analytics and tools the site connects to
- A decision on who edits content after launch
- Any brand, legal or accessibility requirements that apply
The process
Six stages.
Each one reviewed.
You review the work at each stage, on a staging site before anything goes live.
How engagements workDiscovery
Confirm the offer, audiences, pages and constraints. Decide whether a new build is justified or the current site can be improved.
Content model and sitemap
Define page types, fields and URLs. Agree which existing pages, if any, need a redirect to a new destination.
Design system
Design the key templates and the components they share, on phone and desktop, before every page is built.
Build and integrate
Build components and templates, connect the agreed integrations and set up the editing workflow on staging.
Test and review
Check priority journeys, forms, links, mobile controls and performance. You review content and behaviour on staging.
Launch and handover
Launch against the agreed checklist, then hand over the documentation and confirm who owns each part of the site.
Trade-offs
What a code-based site
costs to own.
A Next.js build gives control. It also adds responsibilities that a hosted website builder handles for you.
Compare improving the current siteWhat you gain
- Templates and components designed around your content, not around a theme
- Control over how pages render, load and connect to other tools
- Changes that are reviewed and versioned before they go live
- One component library shared by every new page
What you take on
- Hosting, deployment and monitoring, run by your team or an agreed provider
- Developer time for new layouts and components
- Dependency and security updates for the life of the site
- Any CMS or hosting fees, which vary by provider and plan
Ownership
Decide who owns it
before the build.
Five responsibilities outlast the launch. Each one is agreed early and written into the handover.
How engagements are scopedHosting
Agree before the build: Where the site runs, who pays for it and who deploys changes
Record in the handover: Accounts, environments and the deploy steps
Content updates
Agree before the build: Who edits which pages and fields, and how changes are reviewed
Record in the handover: Editing steps for each page type
Integrations
Agree before the build: Which tools connect to the site and who owns each connection
Record in the handover: Each connection, its owner and how to test it
Maintenance
Agree before the build: Who updates dependencies and fixes defects after launch
Record in the handover: The update routine and where issues are reported
Recovery
Agree before the build: How the site is backed up and restored if a release fails
Record in the handover: Restore steps and who is able to run them
Our own site
Hosting choices
change the work.
This website is a static Next.js export with no application server. Any redirects it needs belong at the hosting layer, not in Next.js. A client project can choose a different setup, and that changes who runs what after launch.
Scope and availability
The stack, CMS, integrations, hosting and maintenance are agreed per project. Website Optimiser audits are Live in the Ciny platform, run by the Ciny team on demand. Automatic changes to a live site and staged page release are planned. A custom development project is a separate engagement. A new website does not guarantee more traffic, rankings or enquiries.
Check platform capabilitiesWill Next.js improve our search rankings?
No framework guarantees a ranking. Search systems determine rankings and inclusion. A build can keep pages crawlable, usable on a phone and organised around clear URLs. Those are checks we can scope, not a ranking promise.
Can our team edit the site without a developer?
That depends on the editing workflow agreed in discovery. A CMS can let your team edit agreed pages and fields. New layouts and components still need development work.
Do we need Next.js, or would a simpler platform do?
It depends on the content, the integrations and who maintains the site. If a hosted website builder covers your needs, it may cost less to own. Discovery should answer this before a build is scoped.
Who hosts and maintains the site after launch?
That is not included automatically. Hosting, maintenance and post-launch support are agreed before the build, and the handover names who owns each one.
How much does a build cost and how long does it take?
Prices and timings are confirmed in a proposal, after the pages, content readiness, integrations and level of implementation are understood.
Tell us what the
new site needs to do.
Share the pages, content and tools involved. We agree the scope, editing workflow and handover before any build starts.