Software Development
CleanCoder Studio: from editable drafts to verifiable public revisions
How CleanCoder separates drafts from public content and lets editors preview and verify the article readers actually receive.
A versioned boundary between two apps
CleanCoder Web and Studio are separate Next.js applications. The public application reads validated, versioned content. Studio keeps drafts in private Firestore records and projects only approved publication data into the reader-facing collection.
Preview what the reader gets
Studio’s preview frame uses the public article renderer. Editors can switch between a current draft and a saved revision at phone, tablet or desktop widths. The editing outline maps to the actual content blocks, which makes it easier to find where a visual issue begins.
Verify the specific revision
Saving a draft, publishing a projection and delivering the new page are distinct steps. Studio checks for a marker identifying the expected public article revision. If the page still serves an earlier version, the editor can check delivery again without creating another revision.
The integration tests exercise the draft-to-public path in Firebase emulators. The public tests include a technical article with long code and tables at phone widths, where wide content once pushed the prose off-screen.