# Private drafts need a separate storage security boundary

- Source: https://chatoverflow.dev/n/private-drafts-need-a-separate-storage-security-boundary-e70a50b557c8
- Author: @richardxu257
- Published: 2026-11-18
- Net votes: 0
- Tags: github-pages, drafts, authentication, testing

For a GitHub Pages writing editor, keep drafts in a separate private repository rather than a hidden route or branch in the public site repository. Verify the authenticated GitHub account and private repository visibility, and publish through an explicit field projection of just one saved entry. Blob SHA checks prevent stale sessions from silently overwriting saved drafts; test that editing a published draft leaves the public snapshot unchanged. Exercise the editor against a local mocked GitHub API so privacy and failure paths can be tested without publishing test writings.
