a public dev journal · for everyone building

Your work,
posted. Automatically.

DayBy turns the things you do every day - ship a feature, run a sprint review, push a design - into a polished blog post on your own subdomain. Tell your AI agent what happened, or let it watch. It writes the rest.

No credit card Live in under a minute Free forever for one subdomain
Works with Claude Cursor ChatGPT & MCP GitHub
Built for everyone who ships something every day.
D
Developers
Commits, PRs, post-mortems
P
Product Managers
Launch notes, sprint recaps
D
Designers
Process posts, UI breakdowns
F
Founders
Build-in-public updates
M
Marketers
Campaign post-mortems
+
Anyone in tech
If you make things, you have a journal
how it works

Three steps. No blank page.

You already do the work. The hard part is sitting down to write about it. DayBy makes that part disappear - whether you're closing a PR, presenting a Figma file, or hitting send on a launch.

commit · renderer: footnote node type2 files · +312
figma · Onboarding v3 - final14 frames
linear · PM-241 shippedclosed today
notion · Launch retro notes8 min ago
01 You work

Do what you already do.

Code, design, plan, ship. DayBy doesn't change your day - it just listens for the moments worth writing about.

~ claude · mcp
you › write up what i shipped today
claude › reading your activity...
drafting via dayby.post()
published · 5 min read
02 You tell your agent

Or skip the telling.

Ask Claude, Cursor, ChatGPT - or any MCP-compatible tool - to draft the post. The DayBy editor and a clean form work too.

blog maya.dayby.dev
How We Built a Custom Markdown...
api 200 OK
{ "title": "How We Built..." }
portfolio your CV, auto
3 posts this week · 12 this month
03 It posts everywhere

One entry, three surfaces.

Public blog on your subdomain. Structured API for any tool that wants it. A living portfolio of what you've built.

the proof

One post. Three places it can live.

Write once in DayBy - in the editor, via API, MCP, or your IDE. The same entry becomes a piece on your subdomain, a structured API response, and a publishable article. Pick the routes; the source stays the same.

maya.dayby.dev/posts/markdown-renderer
Apr 25, 2026 · 5 min read · #engineering

How We Built a Custom Markdown Renderer with Rails in a Weekend

Maya R. · @maya

Most static-site renderers do a fine job - until you want one weird thing.

In my case the weird thing was inline footnote popovers that worked without JavaScript. So I sat down on Saturday morning and wrote my own.

The trick was treating footnote refs as a first-class node type during the parse pass, instead of patching them in afterward. The whole thing clocks in at 312 lines including tests - small enough to fit on one screen.

#rails #weekend-build #markdown
01 REST API

Hit /api/v2/posts - get the post as content, content_plain, and html_article. Every consumer renders fresh, no redeploys.

GET /api/v2/posts/markdown-renderer → 200
02 Public subdomain

Your own name.dayby.dev. A real public blog - every post you publish goes live automatically. No setup. No theme to pick.

maya.dayby.dev live since 2024
03 MCP & agents

Connect DayBy to Claude, Cursor, or any MCP-compatible tool. Create, edit and publish posts without leaving your editor or chat.

mcp dayby.post(...) 3 tools
input

Four ways in. Same beautiful result.

02

AI chat

Describe what you shipped in plain language. The AI drafts the post. You set the tone - tight, casual, technical, hype.

→ "write up what I did today"
03

API

POST to /api/v2/posts from scripts, CI, your bot, or any backend. Headless when you need it.

→ curl -H "Authorization: ..."
04

MCP

Connect to Claude, Cursor, or any MCP client. Post from your IDE without breaking flow.

→ mcp / dayby.post()
auto-pilot

Already shipping? Let DayBy write for you.

Connect GitHub, Linear, or Figma - DayBy turns commits, closed tickets, and shipped designs into draft posts on a schedule you set. Review, polish if you want, publish.

Daily digest, weekly recap, or per-PR posts
Sanitises secrets locally before anything leaves your machine
Plain-text version always available for API consumers
github · linear · figma · slack
~/your-app · post.sh
# post from anywhere -- CI, cron, your editor
curl -H "Authorization: Bearer $KEY" \
    "https://dayby.dev/api/v2/posts"

// → three formats, every time
{
  "content": "<p>Rich HTML...</p>",
  "content_plain": "Clean readable text...",
  "html_article": "<article>Full SEO...</article>",
  "excerpt": "Most static-site renderers...",
  "reading_time": 5,
  "tags": ["rails", "markdown"]
}
claim your subdomain

Pick a name. Start writing.
Be findable by Monday.

Your work deserves a record. Free to start - one subdomain, unlimited posts, full API. No credit card.

Your own .dayby.dev subdomain FREE
Editor, AI chat, API, MCP ALL TIERS
GitHub / Linear / Figma sync AUTO
Custom domain on Pro $8/mo
Live in under a minute PROMISE