Evidence available
Editorial drafts are stored in the editor's browser. Shared publishing is not part of the demonstrated scope. Business performance figures are not claimed.
The operating constraints
- Preserve the original company identity
- Make technical services accessible to prospective clients
- Keep draft editorial content separate from published pages
Digigen’s role
Website redesign, Next.js development, service presentation, search metadata and an editorial drafting preview.
Design and delivery decisions
- Rebuilt the public experience around the consultancy's services and identity
- Created responsive company and service pages with structured search metadata
- Built a browser-local article drafting and preview workflow with explicit review states
The delivered scope
A modern consultancy website with structured service pages and an editorial drafting preview.
What the workflow enables
The business has a coherent company and services presentation, while the separate preview allows article preparation before a shared publishing system is introduced.
Technical approach
Next.js, responsive interfaces, structured metadata and IndexedDB editorial drafts.
Possible next steps
Connect an authenticated shared publishing workflow when the editorial process and ownership are agreed.
Does your team face a similar problem?
Describe the workflow, the people involved and the change you need. We will help you decide what to investigate before committing to a build.
