Why Draft Articles Save to a Database Mid-Sentence, Not Just Your Browser Tab
The content writer persists article drafts to Firestore as you type, not just to your browser — a genuinely live, still-used data store, not a stale leftover from Editor's old Firebase auth.
"I lost three hours of work in [tool]" is a recurring complaint across productivity-tool reviews for a specific, avoidable reason: a draft that only exists in your browser tab is one crashed tab, one accidental close, one dead laptop battery away from gone. "Google Docs never lost my work" is the flip side of the same complaint — the expectation, once you've used a tool that saves centrally as you type, is that anything less feels like a step backward.
Where content-writer drafts actually live
Editor's content writer persists your draft to a database as you write, not just to local browser state. The relevant plugins are SaveToFirestorePlugin.tsx and LoadFirestoreArticlePlugin.tsx, in frontend/apps/editor/src/features/content-writer/plugins/ — the naming tells you directly what's happening: drafts save to and load from Firestore, Google's cloud document database, as part of normal editing, not as a manual "save" action you have to remember to trigger.
A distinction worth getting right
If you've read anything about Piskes' authentication history, you may know that Firebase Auth was removed platform-wide — login no longer runs through Firebase anywhere in the product, replaced by a Go-backend JWT flow. It would be a reasonable but wrong assumption to see "Firestore" in the content writer's code and read it as a leftover from that old auth system, still hanging around by accident. That's not what this is. Firestore and Firebase Auth are separate products under the same vendor umbrella — removing Firebase as an authentication method doesn't require removing Firestore as a data store, and Editor's client-side Firebase configuration is read specifically to initialize Firestore, not to authenticate anyone. This is a legitimate, currently-live use of Firestore for exactly what it's good at — storing documents with low-latency reads and writes — not a stale remnant of a system that's otherwise been retired.
What this means for you as a writer
Practically, it means a draft you're actively writing in the content writer isn't sitting only in your browser's memory, vulnerable to a crashed tab or an accidentally closed window. It's being written to a real database as you go, which is the same underlying promise that makes "autosave to the cloud" a trustworthy claim in any tool that makes it — not a vague reliability statement, but a specific mechanism you can point to: these two plugins, this data store, saving as you type.