Problem
Writing tools and public websites often become the same system. That makes publishing brittle: theme changes, platform rules, and editor workflows all compete in one codebase.
BlogSync keeps the private authoring workflow separate from the public site. It stores articles, renders Markdown, and publishes content into the source repository that owns the presentation layer.
Architecture
The current direction is:
BlogSync -> JessyHome -> jessyhhh.github.ioBlogSync writes Markdown into src/content/blog. JessyHome builds the Astro site. The Pages repository only receives static output.
Engineering Notes
- Go owns the publishing pipeline and platform adapters.
- Node handles BlockNote-to-Markdown rendering.
- The public site stays static and easy to cache.
- Deployment credentials are isolated to repository automation.