Allpub – Cross-Publish From Notion to Dev.to, Hashnode, Medium
Posted2 months ago
allpub.coTechstory
supportivepositive
Debate
0/100
NotionContent PublishingDeveloper Tools
Key topics
Notion
Content Publishing
Developer Tools
AllPub is a tool that allows users to cross-publish content from Notion to multiple platforms like Dev.to, Hashnode, and Medium, with a positive reception from the HN community.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
N/A
Peak period
1
Start
Avg / period
1
Key moments
- 01Story posted
Oct 27, 2025 at 4:26 PM EDT
2 months ago
Step 01 - 02First comment
Oct 27, 2025 at 4:26 PM EDT
0s after posting
Step 02 - 03Peak activity
1 comments in Start
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 27, 2025 at 4:26 PM EDT
2 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45725860Type: storyLast synced: 11/17/2025, 8:05:59 AM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
I built AllPub (https://allpub.co) to solve a personal problem: I write technical articles and waste 3+ hours manually copying them to Dev.to, Hashnode, Medium, Ghost.
Each platform has different: - Markdown flavors (syntax highlighting, embeds) - Image handling (CDN requirements, optimization) - SEO requirements (canonical URLs, meta tags) - Formatting quirks (tables, code blocks)
AllPub connects to your Notion workspace (notion, dev.to, hashnode)and handles all of this automatically.
*Tech stack:* - Next.js (frontend) - Supabase (backend) - clerk (auth) - Platform APIs: Dev.to, Hashnode, Notion - Vercel (hosting)
*Challenges I faced:*
1. Notion's API is powerful but complex - Block-based structure (not linear Markdown) - Nested content handling - Image URLs are ephemeral (expire after 1 hour)
2. Each platform's Markdown parser is different - Dev.to: Liquid tags, front matter - Hashnode: GraphQL API, custom syntax - Medium: HTML-based (not Markdown) - Ghost: JSON content format
3. Image hosting/CDN - Notion images expire - Had to proxy/re-upload to stable CDN - Optimization per platform (sizes, formats)
4. Rate limiting across 4+ APIs - Orchestrated parallel publishing - Retry logic for failures - Status tracking per platform
*Technical decisions:*
- Why Supabase? (Postgres + Realtime, great DX) - Why Next.js? (SSR for landing page, API routes for webhooks) - Why not build a Notion plugin? (API limitations, better UX as standalone)
*Current state:*
The product is live and functional. Launching on Product Hunt this week.