AUTOMATION PIPELINE
One flow from conversation to publication
Connect authentication, writing styles, image uploads, and publishing through five MCP tools.
MIT-LICENSED PUBLISHING STACK
Start with solid CRUD, editing, media, and operations. Add MCP auto-publishing, shape the brand, and extend it into a personal blog, a community, or a commercial fork.
AUTOMATION PIPELINE
Connect authentication, writing styles, image uploads, and publishing through five MCP tools.
A public foundation you can run, modify, and develop into a product of your own.
A CURATED PRODUCT DEMO
Blog articles and community posts are discovered in one feed. The content below is a reviewed, static example for a reliable landing page.
Turn an AI-assisted solution into a reviewable article, connect its media and sources, and make it useful again later.
Development · Auto-publishing · 6 min read
A practical record from authentication to WebP upload and cover attachment.
Bimmo
12 min ago · 8 replies
Manage the cover, logo, icon, and primary color in one place.
Jooli
28 min ago · 31 saves
Run an interest-based space with roles, replies, votes, and reporting tools.
LumoPop
1 hour ago · 14 replies
FROM CRUD TO A PRODUCT
This is not a one-use demo. Publishing, automation, branding, and community operations belong to the same working system.
01
Personal blogs, drafts, rich text and Markdown, categories, tags, media, and related posts.
02
Direct MCP and OAuth MCP, writing styles, immediate publication, and signed image uploads.
03
Shape names, covers, logos, icons, brand colors, and public URLs around your identity.
04
Memberships, roles, posts, replies, votes, reports, widgets, discovery, and reputation.
MCP AUTO-PUBLISHING
The public contract verifies real authentication and tool responses instead of trusting a browser success screen.
Connect direct MCP or OAuth MCP from Codex or another compatible client.
Confirm the user, blog access, and actual authentication mode before any write.
Load reusable rules for tutorials, research, essays, and other writing styles.
Request a signed URL, upload WebP bytes, and finalize the file ID.
Publish the reviewed title, body, category, tags, and media to the blog.
Keep a stable blog URL, appear in the home feed, and continue the conversation in a relevant community.
BLOG DESIGN
No invented themes. These previews use the cover, logo, icon, brand color, and placement controls that exist today.
COVER FIRST
@build-notes
Lessons learned and the reasoning behind product decisions.
INLINE IDENTITY
@field-journal
Observations and research collected in the field.
BADGE IDENTITY
@studio-log
Creative processes and practical studio knowledge.
FROM BLOG TO COMMUNITY
Start with a personal record, create topic spaces, and give members and moderators the tools for healthy discussion.
OPEN SOURCE OPERATORS
c/selfhost
14 replies · 9 participants · Operations guide linked
OPEN SOURCE / MIT
The application code, deployment configuration, auto-publishing skill, and operations documentation are public. You control the data, brand, and deployment model.
Use the Docker Compose setup flow with diagnostics, backup guidance, and operations documentation.
Adapt the brand, content workflow, and product surface to your users and operating model.
Build a commercial fork under the MIT terms and define the operating policies it needs.
START WITH A SOLID FOUNDATION
Run the code, inspect the architecture, then adapt it to your brand and operating model.