Project Details
Home/Project Details
AlimsWrite
Project description
A publishing platform where the writer owns the machinery
The Challenge
A writer publishing through a hosted platform is renting the three things that matter: the audience list, the archive and the search visibility. The platform decides what the page looks like, what it costs to keep, and what happens to years of work if the terms change.
It has to be credible to a business audience as well as a reading one, which means the same system carries editorial content and commercial pages without either looking bolted on. And the editing experience has to be good enough that a non-technical writer never needs to touch the markup.
The Solution
One Next.js application serving both a publication and a business site: editorial content as the front door, service pages behind it, and a rich-text editor with a draft-to-published workflow that the owner drives. The writing lives in the owner's own database and ships from the owner's own domain, which is the entire argument for building it rather than renting it.
Skills and deliverables
Features delivered
The hard part
Keeping a publication and a business site coherent in one system. They want different things — one is optimised for reading and searching, the other for answering a buyer's questions — and the easy answer is two sites that duplicate each other. The build keeps them as one content model with different templates, so a change to the way an article renders cannot silently break a service page.
The Impact
Live with the editorial archive and the commercial pages running from one deployment, and the publishing workflow in the owner's hands: drafts, scheduling, and the full control over layout that was the reason to build it.
