We built AutoBlogWriter to solve a recurring issue in dev-led teams: everyone agrees content matters, but the actual publishing workflow is brittle and inconsistent.
Our setup used to be a pile of tools:
- docs for notes,
- AI chats for drafts,
- manual SEO edits,
- ad-hoc scheduling,
- and custom integration work just to render on our site.
So we built a single workflow:
1. capture workspace context,
2. generate blog ideas,
3. produce drafts,
4. polish/optimize,
5. schedule and publish,
6. render in Next.js via SDK.
Current beta scope:
- AI idea + draft generation
- edit/polish workflow
- scheduling + publish pipeline
- TypeScript SDK for Next.js + React components
What I would like feedback on:
- Is this architecture useful enough to replace your current stack?
- Which integration concerns should we prioritize first?
- What would block you from using this weekly?
Our setup used to be a pile of tools:
- docs for notes, - AI chats for drafts, - manual SEO edits, - ad-hoc scheduling, - and custom integration work just to render on our site.
So we built a single workflow: 1. capture workspace context, 2. generate blog ideas, 3. produce drafts, 4. polish/optimize, 5. schedule and publish, 6. render in Next.js via SDK.
Current beta scope:
- AI idea + draft generation - edit/polish workflow - scheduling + publish pipeline - TypeScript SDK for Next.js + React components
What I would like feedback on:
- Is this architecture useful enough to replace your current stack? - Which integration concerns should we prioritize first? - What would block you from using this weekly?
Beta link: http://autoblogwriter.app/?utm_source=hackernews&utm_medium=...