Blog (Content Publishing Node)
<div class="post-category"><span class="cat-badge cat-nodes">Nodes</span></div>
<p class="lead"><strong>The Blog node is the content publishing surface of the 1BZ ecosystem. It powers both long-form articles and this Knowledge Base, and it cross-posts automatically to Dev.to and Hashnode.</strong></p>
<h2>Overview</h2>
<p>Hosted at https://blog.1bz.biz on PHP and MySQL, the blog accepts posts via an authenticated API. Posting limits are tier-gated: Admin is unlimited, Pro posts 5 articles per month, Basic posts 1 per month.</p>
<h2>Key components</h2>
<ul><li>PHP front end with MySQL storage</li><li>POST /api/publish.php with API key auth</li><li>Auto cross-post to Dev.to and Hashnode</li><li>Featured image upload via /api/upload.php</li><li>KB upsert endpoint (this seeder) for idempotent facts</li></ul>
<h2>Related</h2>
<ul><li>[RAG Knowledge Base](/post.php?slug=rag-knowledge-base)</li><li>[Ecosystem Overview](/post.php?slug=ecosystem-overview)</li></ul>
Powered by BizNode™
Related Posts
Add a Command to Your Bot in 10 Lines of YAML
Adding a new bot feature used to mean editing Python, wiring a `CommandHandler`, and redeploying. With the Feature Manifest Framework it is four steps and about ten lines of YAML — and you get a slash command and a paid network handle from
How 1BZ Bots Define Features via Manifest
1BZ bots used to hand-wire every capability as a Python `CommandHandler`. That put even a trivial command one code change and a redeploy away from production. The Feature Manifest Framework replaces that with a declarative YAML file at `bot
Slash Command vs Handle — what each is for
Slash commands and handles are related but not identical. A slash command is the owner-facing UI inside a single bot; a handle is a network-facing service endpoint that any other bot, workflow, or API on the 1BZ network can call. The same u