We are pleased to announce microfeed v1.0.7, bringing together the deployment, theme, editing, and browser-agent improvements introduced across versions 1.0.6 and 1.0.7.
These releases let people deploy and manage microfeed from any folder through the published CLI, expand the Built-in theme catalog to seven purpose-built designs, make remote GitHub theme installation and activation more reliable, and add experimental draft-only tools for compatible browser agents.
Deploy and manage microfeed from any folder
The official @microfeed/cli now includes the complete management launcher. Run npx @microfeed/cli manage without first Git-cloning the microfeed source repository yourself. The launcher downloads the exact tagged release into a private persistent cache, installs its locked dependencies, and keeps saved deployment state separately so later cache repairs cannot erase connected instances.
When a coding agent starts the launcher, it receives the exact deployment skill and management-reference paths to read. It begins with Cloudflare account discovery, distinguishes a new installation from an existing compatible Worker, asks before ambiguous account or site choices, preserves resource-reuse and confirmation safeguards, and continues until status verifies the deployment.
Every existing management command remains available through the same prefix, including account discovery, initialization, connection, deployment, status, local development, themes, snapshots, domains, authentication, Cloudflare Access guidance, and guarded destruction.
Seven Built-in themes and richer previews
microfeed now includes Default, Podcast, Editorial Blog, Photo Grid, Video Channel, Link Digest, and Product Changelog Built-in themes. Each design has its own source, immutable package release, representative demo content, and media-license inventory.
Initialization and deployment synchronize Built-in releases without changing the active theme. New versions are installed inactive so administrators can preview them with either theme-owned demo content or current site content before choosing whether to activate them. Built-ins remain protected from manual deletion, while the Custom-theme version quota increases to 100.
Format v2 themes can also choose whether an Item search result opens its local microfeed page, original URL, or media attachment. Missing destinations fall back safely, Page results remain local, and stable CSS hooks let themes style search details without supplying arbitrary result HTML.
The visual editor now makes newly inserted images and videos responsive on narrow screens while preserving their intended desktop maximum. Existing authored media remains unchanged.
Reliable remote theme workflows
Version 1.0.7 makes public GitHub theme installation independent of GitHub's shared unauthenticated REST API quota. microfeed now resolves public branches, tags, and commits with an anonymous shallow Git fetch while preserving exact-commit installation, declared-file limits, regular-file validation, and symlink rejection.
Remote theme activation, deactivation, rollback, and deletion now reach microfeed correctly instead of being rejected as cross-site form submissions. One-time authorization grants, inactive installation, cleanup, instance selection, confirmation, and verification safeguards remain in place.
Admin theme details now prioritize copyable prompts for an AI coding agent that can run shell commands, such as Codex or Claude Code. An update prompt names the current site and original source, asks the agent to connect the existing site if needed, installs the update inactive, pauses before activation, and verifies the site afterward. Export prompts preserve the exact installed package identity and stop before committing or publishing.
See the theme guide and @microfeed/theme-kit reference for the complete workflows.
Experimental draft-only browser-agent tools
When a signed-in protected dashboard runs in a compatible browser with the native document.modelContext API, microfeed automatically exposes seven concise WebMCP tools. A browser agent can read Items and Pages and save only the visible new or unpublished editor as a draft.
The Worker enforces the result as unpublished again. Publishing, deletion, uploads, settings, default-404 content, published or unlisted content, public pages, and unsupported browsers remain outside the WebMCP surface. Webhook events record webmcp as explicit provenance.
Updating an existing Workers deployment
Open an AI coding agent that can run local shell commands and ask:
Update my existing microfeed site to v1.0.7.\n\nStart by running `npx @microfeed/cli manage`, connect the existing\nsite if needed, deploy the update, and continue until `status`\nverifies the deployment.The launcher requires Node.js 22.12 or newer with npm, plus Git and Corepack. Complete any Cloudflare browser-authorization handoffs it requests, but never paste a Cloudflare token, password, or private password-setup link into the conversation.
If the intended instance is already saved and unambiguous, the equivalent direct commands are:
npx @microfeed/cli manage deploy --instance <instance-name>npx @microfeed/cli manage status --instance <instance-name>The update applies the theme-preview-fixture and WebMCP-provenance migrations, synchronizes the seven-theme Built-in catalog without changing the active theme, runs project checks, builds and deploys the Worker, and verifies the result. Ordinary deployment does not activate a new theme or enable webhooks that were never provisioned.
See the update guide and AI-agent deployment guide for details.
Read the complete notes for v1.0.6 and v1.0.7, or see the combined changelog for every change.
","content_text":"We are pleased to announce microfeed v1.0.7 , bringing together the deployment, theme, editing, and browser-agent improvements introduced across versions 1.0.6 and 1.0.7.\nThese releases let people deploy and manage microfeed from any folder through the published CLI, expand the Built-in theme catalog to seven purpose-built designs, make remote GitHub theme installation and activation more reliable, and add experimental draft-only tools for compatible browser agents.\nDeploy and manage microfeed from any folder\nThe official @microfeed/cli now includes the complete management launcher. Run npx @microfeed/cli manage without first Git-cloning the microfeed source repository yourself. The launcher downloads the exact tagged release into a private persistent cache, installs its locked dependencies, and keeps saved deployment state separately so later cache repairs cannot erase connected instances.\nWhen a coding agent starts the launcher, it receives the exact deployment skill and management-reference paths to read. It begins with Cloudflare account discovery, distinguishes a new installation from an existing compatible Worker, asks before ambiguous account or site choices, preserves resource-reuse and confirmation safeguards, and continues until status verifies the deployment.\nEvery existing management command remains available through the same prefix, including account discovery, initialization, connection, deployment, status, local development, themes, snapshots, domains, authentication, Cloudflare Access guidance, and guarded destruction.\nSeven Built-in themes and richer previews\nmicrofeed now includes Default, Podcast, Editorial Blog, Photo Grid, Video Channel, Link Digest, and Product Changelog Built-in themes. Each design has its own source, immutable package release, representative demo content, and media-license inventory.\nInitialization and deployment synchronize Built-in releases without changing the active theme. New versions are installed inactive so administrators can preview them with either theme-owned demo content or current site content before choosing whether to activate them. Built-ins remain protected from manual deletion, while the Custom-theme version quota increases to 100.\nFormat v2 themes can also choose whether an Item search result opens its local microfeed page, original URL, or media attachment. Missing destinations fall back safely, Page results remain local, and stable CSS hooks let themes style search details without supplying arbitrary result HTML.\nThe visual editor now makes newly inserted images and videos responsive on narrow screens while preserving their intended desktop maximum. Existing authored media remains unchanged.\nReliable remote theme workflows\nVersion 1.0.7 makes public GitHub theme installation independent of GitHub's shared unauthenticated REST API quota. microfeed now resolves public branches, tags, and commits with an anonymous shallow Git fetch while preserving exact-commit installation, declared-file limits, regular-file validation, and symlink rejection.\nRemote theme activation, deactivation, rollback, and deletion now reach microfeed correctly instead of being rejected as cross-site form submissions. One-time authorization grants, inactive installation, cleanup, instance selection, confirmation, and verification safeguards remain in place.\nAdmin theme details now prioritize copyable prompts for an AI coding agent that can run shell commands, such as Codex or Claude Code. An update prompt names the current site and original source, asks the agent to connect the existing site if needed, installs the update inactive, pauses before activation, and verifies the site afterward. Export prompts preserve the exact installed package identity and stop before committing or publishing.\nSee the theme guide and @microfeed/theme-kit reference for the complete workflows.\nExperimental draft-only browser-agent tools\nWhen a signed-in protected dashboard runs in a compatible browser with the native document.modelContext API, microfeed automatically exposes seven concise WebMCP tools. A browser agent can read Items and Pages and save only the visible new or unpublished editor as a draft.\nThe Worker enforces the result as unpublished again. Publishing, deletion, uploads, settings, default-404 content, published or unlisted content, public pages, and unsupported browsers remain outside the WebMCP surface. Webhook events record webmcp as explicit provenance.\nUpdating an existing Workers deployment\nOpen an AI coding agent that can run local shell commands and ask:\nUpdate my existing microfeed site to v1.0.7.\n\nStart by running `npx @microfeed/cli manage`, connect the existing\nsite if needed, deploy the update, and continue until `status`\nverifies the deployment. The launcher requires Node.js 22.12 or newer with npm, plus Git and Corepack. Complete any Cloudflare browser-authorization handoffs it requests, but never paste a Cloudflare token, password, or private password-setup link into the conversation.\nIf the intended instance is already saved and unambiguous, the equivalent direct commands are:\nnpx @microfeed/cli manage deploy --instanceWe are pleased to announce microfeed v1.0.5, an update focused on signed webhooks and content automation.
microfeed 1.0.5 adds opt-in, cost-bounded webhook delivery through Cloudflare Queues, exact event contracts, Admin and CLI testing tools, and guarded infrastructure lifecycle controls. It also improves the public Default theme, Admin collection loading, theme asset delivery, bundled-theme maintenance, and coding-agent guidance.
Signed, cost-bounded webhooks
Webhooks let an integration react when content changes without polling. Version 1.0.5 provides 22 versioned channel, item, Page, Site File, theme, and webhook events. Every delivery uses Standard Webhooks headers and a unique encrypted signing secret for its endpoint.
Content mutations and their matching webhook outbox records are committed atomically in D1, then delivered through a dedicated Cloudflare Queue. Delivery is at least once, with bounded retries, reconciliation, retention, and automatic endpoint pausing after repeated failures.
Administrators can configure up to 20 endpoints from Admin, choose the exact event subscriptions for each one, reveal or rotate its signing secret, disable or delete integrations, inspect delivery attempts, and manually redeliver an event. An owner-controlled UTC daily delivery budget provides a cost guard, while the Overview and Deliveries screens show usage, Queue-operation estimates, backlog, retries, alerts, and endpoint health.
Webhook events carry stable content snapshots plus explicit causation, correlation, idempotency, and test: true metadata. The generated OpenAPI document, interactive API reference, and self-contained llms-full.txt publish the exact webhook operation, event union, Standard Webhooks headers, schemas, and named examples.
Event Explorer and integration tooling
Admin now includes a Webhook Event Explorer. It can preview generated examples or current site content, display the exact Payload, Schema, and Headers, print a preview locally without side effects, or send a signed test through the normal delivery path.
The official @microfeed/cli adds webhook sample for exact contract examples, webhook scaffold for offline JavaScript and Python receiver starters, and webhook listen for inspecting or forwarding verified deliveries. The optional webhook listen --tunnel workflow receives tests from a deployed site through a temporary Cloudflare Quick Tunnel using a pinned, checksum-verified cloudflared binary.
Local yarn dev automatically provides isolated Queue, consumer, maintenance-trigger, and signing-secret simulation. It creates no Cloudflare resources and incurs no deployed Queue usage, so receivers and signed tests can be developed before production infrastructure is enabled.
The new content-automation documentation explains how the API, webhooks, and CLI work together. It includes n8n and Zapier guides, a no-code webhook testing path, production receiver guidance, automation examples, and coding-agent prompts grounded in each instance's generated contract.
Safe and reversible webhook infrastructure
Deployed webhooks remain explicitly opt-in. Production and preview use separate dedicated Queues, and enabling one environment does not enable the other. An ordinary deployment preserves the saved lifecycle state: enabled remains enabled, disabled remains detached, and never-provisioned remains off.
The new yarn manage deploy --disable-webhooks workflow pauses and purges the dedicated Queue, cancels pending deliveries, and removes producer, consumer, and Cron configuration while retaining the Queue identity, encrypted endpoint secrets, endpoint settings, and delivery history. Re-enabling later reuses those exact resources without replaying events from the disabled interval.
Enable, disable, status, connection, and destruction operations now verify the exact Queue identity and consumer, preflight Cloudflare authorization, retry one credential refresh when needed, preserve resumable transitions, and fail closed rather than changing an unexpected resource.
Publishing, Admin, and theme improvements
The bundled Default theme adds persistent System, Light, and Dark modes, improved desktop and mobile navigation, a more focused search experience, refined typography and rich-content spacing, and a better mobile layout.
Items, Pages, and Site Files now load through lightweight Admin shells and private summary endpoints. Filtering, sorting, and pagination update in place while retaining useful loading, stale-request cancellation, and retry states instead of performing a full route reload.
Immutable theme assets now use a configured R2 custom domain and Cloudflare CDN when available, with the existing same-origin /media/ route as a fallback. Deployment keeps the newest bundled Default-theme candidate available without forcing activation and safely prunes superseded inactive versions while preserving active, rollback, draft, origin, and asset references.
This release also expands Claude Code and coding-agent guidance across the application repository, theme starters, documentation, and agent workflows.
Updating an existing Workers deployment
If your local repository clone is already connected to a microfeed Worker, protect any local work, update the clone, and run:
yarn install --immutable\nyarn manage deploy\nyarn manage statusThe deployment applies the webhook storage, named API-key scope, delivery-budget, and reversible-infrastructure migrations; reconciles bundled theme versions; runs project checks; builds and deploys the Worker; and verifies the result.
Ordinary updates do not enable webhooks on a site that has never provisioned them. Existing enabled or disabled state is preserved. After reviewing the additional Cloudflare resources and usage, enable an exact production site with:
yarn manage deploy --enable-webhooks --instance <instance-name>\nyarn manage status --instance <instance-name>You can also open the connected repository in a local coding agent and ask:
Deploy to Cloudflare.See the update guide, webhook guide, content automation overview, and theme guide for details.
Version 1.0.5 makes microfeed ready for signed, event-driven integrations while keeping webhook infrastructure optional and owner-controlled. See the full changelog for every change.
","content_text":"We are pleased to announce microfeed v1.0.5 , an update focused on signed webhooks and content automation.\nmicrofeed 1.0.5 adds opt-in, cost-bounded webhook delivery through Cloudflare Queues, exact event contracts, Admin and CLI testing tools, and guarded infrastructure lifecycle controls. It also improves the public Default theme, Admin collection loading, theme asset delivery, bundled-theme maintenance, and coding-agent guidance.\nSigned, cost-bounded webhooks\nWebhooks let an integration react when content changes without polling. Version 1.0.5 provides 22 versioned channel, item, Page, Site File, theme, and webhook events. Every delivery uses Standard Webhooks headers and a unique encrypted signing secret for its endpoint.\nContent mutations and their matching webhook outbox records are committed atomically in D1, then delivered through a dedicated Cloudflare Queue. Delivery is at least once, with bounded retries, reconciliation, retention, and automatic endpoint pausing after repeated failures.\nAdministrators can configure up to 20 endpoints from Admin, choose the exact event subscriptions for each one, reveal or rotate its signing secret, disable or delete integrations, inspect delivery attempts, and manually redeliver an event. An owner-controlled UTC daily delivery budget provides a cost guard, while the Overview and Deliveries screens show usage, Queue-operation estimates, backlog, retries, alerts, and endpoint health.\nWebhook events carry stable content snapshots plus explicit causation, correlation, idempotency, and test: true metadata. The generated OpenAPI document, interactive API reference, and self-contained llms-full.txt publish the exact webhook operation, event union, Standard Webhooks headers, schemas, and named examples.\nEvent Explorer and integration tooling\nAdmin now includes a Webhook Event Explorer. It can preview generated examples or current site content, display the exact Payload, Schema, and Headers, print a preview locally without side effects, or send a signed test through the normal delivery path.\nThe official @microfeed/cli adds webhook sample for exact contract examples, webhook scaffold for offline JavaScript and Python receiver starters, and webhook listen for inspecting or forwarding verified deliveries. The optional webhook listen --tunnel workflow receives tests from a deployed site through a temporary Cloudflare Quick Tunnel using a pinned, checksum-verified cloudflared binary.\nLocal yarn dev automatically provides isolated Queue, consumer, maintenance-trigger, and signing-secret simulation. It creates no Cloudflare resources and incurs no deployed Queue usage, so receivers and signed tests can be developed before production infrastructure is enabled.\nThe new content-automation documentation explains how the API, webhooks, and CLI work together. It includes n8n and Zapier guides, a no-code webhook testing path, production receiver guidance, automation examples, and coding-agent prompts grounded in each instance's generated contract.\nSafe and reversible webhook infrastructure\nDeployed webhooks remain explicitly opt-in. Production and preview use separate dedicated Queues, and enabling one environment does not enable the other. An ordinary deployment preserves the saved lifecycle state: enabled remains enabled, disabled remains detached, and never-provisioned remains off.\nThe new yarn manage deploy --disable-webhooks workflow pauses and purges the dedicated Queue, cancels pending deliveries, and removes producer, consumer, and Cron configuration while retaining the Queue identity, encrypted endpoint secrets, endpoint settings, and delivery history. Re-enabling later reuses those exact resources without replaying events from the disabled interval.\nEnable, disable, status, connection, and destruction operations now verify the exact Queue identity and consumer, preflight Cloudflare authorization, retry one credential refresh when needed, preserve resumable transitions, and fail closed rather than changing an unexpected resource.\nPublishing, Admin, and theme improvements\nThe bundled Default theme adds persistent System, Light, and Dark modes, improved desktop and mobile navigation, a more focused search experience, refined typography and rich-content spacing, and a better mobile layout.\nItems, Pages, and Site Files now load through lightweight Admin shells and private summary endpoints. Filtering, sorting, and pagination update in place while retaining useful loading, stale-request cancellation, and retry states instead of performing a full route reload.\nImmutable theme assets now use a configured R2 custom domain and Cloudflare CDN when available, with the existing same-origin /media/ route as a fallback. Deployment keeps the newest bundled Default-theme candidate available without forcing activation and safely prunes superseded inactive versions while preserving active, rollback, draft, origin, and asset references.\nThis release also expands Claude Code and coding-agent guidance across the application repository, theme starters, documentation, and agent workflows.\nUpdating an existing Workers deployment\nIf your local repository clone is already connected to a microfeed Worker, protect any local work, update the clone, and run:\nyarn install --immutable\nyarn manage deploy\nyarn manage status The deployment applies the webhook storage, named API-key scope, delivery-budget, and reversible-infrastructure migrations; reconciles bundled theme versions; runs project checks; builds and deploys the Worker; and verifies the result.\nOrdinary updates do not enable webhooks on a site that has never provisioned them. Existing enabled or disabled state is preserved. After reviewing the additional Cloudflare resources and usage, enable an exact production site with:\nyarn manage deploy --enable-webhooks --instanceWe are pleased to announce microfeed v1.0.4, an update focused on turning the public site into a more complete website with standalone Pages, credential-free Item-and-Page search, and editable root-level Site Files.
microfeed 1.0.4 also introduces the format v2 theme contract needed to present these features, improves standalone theme exports, and makes content creation from coding agents safer to validate, retry, and verify.
Standalone Pages and website navigation
Pages provide a dedicated home for website-only content such as About, Contact, or Resources without adding those documents to RSS or JSON Feed. The Page editor uses the familiar rich-text experience and adds an explicit top-level URL path, a search and social description, visibility controls, and an optional website-navigation label.
Published Pages can appear in website navigation, and their order can be arranged by dragging or with keyboard controls. Unlisted Pages remain available at their public URL but stay out of navigation and public search, while Draft Pages remain private.
New installations include a Published About Page at /about/. Eligible existing sites receive the same starter only when that path has never been used, so an update never overwrites an existing or previously deleted About Page.
Page URLs remain dependable over time. When a published path changes, microfeed permanently redirects the old path to the new one. Previous and deleted paths stay reserved so they cannot later point to unrelated content.
Every site also has a protected, editable Default 404 Page. Administrators can customize its title, description, and rich content, preview it at /404/, and use the same themed result for missing public URLs while preserving the correct 404 response.
Public Item-and-Page search
The public website can now search Published feed items and standalone Pages without credentials. Draft and Unlisted Pages, including the special 404 Page, stay out of public results.
The bundled Default theme includes a responsive typeahead search dialog that opens from its search control or with Command/Ctrl-K. Visitors can move through suggestions from the keyboard, open a result directly, or continue to the dedicated /search/ page for complete results and detailed excerpts.
Search ranks exact matches first, tolerates minor title typos, and uses a unified D1-backed corpus shared with Admin workflows. Because the corpus is derived from durable content, deployment and snapshot restore can rebuild it safely.
Theme authors can add the same experience through the format v2 webSearch slot, shared search controls, navigation_pages data, and representative Page and Search previews in Theme Kit.
Editable Site Files
Site Files make root-level text responses manageable from Admin. microfeed provides generated defaults for robots.txt, llms.txt, and sitemap.xml, and administrators can add supported custom files such as security.txt.
The generated files keep crawler and machine-readable discovery current automatically. robots.txt advertises the sitemap, llms.txt summarizes the site, Published Pages, and recent items for AI tools and links enabled API documentation, and sitemap.xml includes the home page, Published Pages, Published items, and supported image or video metadata.
Each file has a private Mustache draft with Source and Preview tabs. Format-aware highlighting helps with JSON, XML, Markdown, YAML, CSS, CSV, and other text formats, while Preview renders the exact unsaved response bytes with current site data. JSON and XML output must validate before it can be published.
Templates can use channel data, up to 100 newest Published items, and up to 100 most recently updated Published Pages. microfeed also stores the last valid rendered result for a published override, so a later content change that produces invalid output falls back safely instead of breaking the public file.
Generated files can be overridden, saved as Draft, or restored to the current microfeed default. Custom files can be created and deleted. Pages, Page path history, Site File drafts, and published overrides are included in portable snapshots and are available through the documented versioned API.
Theme compatibility and safer automation
Format v2 extends the theme contract from six to eight slots with webPage and webSearch, website navigation data, editable 404 support, and complete Feed, Item, Page, Search, and RSS previews. The bundled Default theme is the reference implementation, with responsive navigation, modern search controls and results, a shared footer, and consistent rich-text spacing.
Installed format v1 themes remain compatible and continue rendering Feed and Item pages. Administrators can draft Pages under v1, but publishing Pages and exposing public search require an active format v2 theme. During an update, microfeed installs the bundled v2 Default theme without changing the active design, so it can be previewed and activated separately.
Theme exports are now complete standalone Git-ready repositories. An active or specific installed theme can be exported, installed, validated, tested, and previewed independently from the microfeed application checkout.
The official @microfeed/cli also adds compact summary output, unwrapped reads, server-side validation-only checks, post-create verification, framed JSON input, and 24-hour idempotency keys. These options make agent-driven item creation smaller, safer to retry, and easier to recover when a request is interrupted.
Updating an existing Workers deployment
If your local repository clone is already connected to a microfeed Worker, protect any local work, update the clone, and run:
yarn install --immutable\nyarn manage deploy\nyarn manage statusThe deployment applies the item-idempotency, Page, public-search, editable-404, and Site File migrations; creates the starter About Page only when its path is available; rebuilds the unified search corpus; runs project checks; builds and deploys the Worker; and verifies the result.
You can also open the connected repository in a local coding agent and ask:
Deploy to Cloudflare.See the update guide, Pages and Site Files guide, and theme guide for details.
Version 1.0.4 makes microfeed more useful as a complete public website while preserving its feed-first, self-hosted foundation. See the full changelog for every change.
","content_text":"We are pleased to announce microfeed v1.0.4 , an update focused on turning the public site into a more complete website with standalone Pages, credential-free Item-and-Page search, and editable root-level Site Files.\nmicrofeed 1.0.4 also introduces the format v2 theme contract needed to present these features, improves standalone theme exports, and makes content creation from coding agents safer to validate, retry, and verify.\nStandalone Pages and website navigation\nPages provide a dedicated home for website-only content such as About, Contact, or Resources without adding those documents to RSS or JSON Feed. The Page editor uses the familiar rich-text experience and adds an explicit top-level URL path, a search and social description, visibility controls, and an optional website-navigation label.\nPublished Pages can appear in website navigation, and their order can be arranged by dragging or with keyboard controls. Unlisted Pages remain available at their public URL but stay out of navigation and public search, while Draft Pages remain private.\nNew installations include a Published About Page at /about/ . Eligible existing sites receive the same starter only when that path has never been used, so an update never overwrites an existing or previously deleted About Page.\nPage URLs remain dependable over time. When a published path changes, microfeed permanently redirects the old path to the new one. Previous and deleted paths stay reserved so they cannot later point to unrelated content.\nEvery site also has a protected, editable Default 404 Page. Administrators can customize its title, description, and rich content, preview it at /404/ , and use the same themed result for missing public URLs while preserving the correct 404 response.\nPublic Item-and-Page search\nThe public website can now search Published feed items and standalone Pages without credentials. Draft and Unlisted Pages, including the special 404 Page, stay out of public results.\nThe bundled Default theme includes a responsive typeahead search dialog that opens from its search control or with Command/Ctrl-K. Visitors can move through suggestions from the keyboard, open a result directly, or continue to the dedicated /search/ page for complete results and detailed excerpts.\nSearch ranks exact matches first, tolerates minor title typos, and uses a unified D1-backed corpus shared with Admin workflows. Because the corpus is derived from durable content, deployment and snapshot restore can rebuild it safely.\nTheme authors can add the same experience through the format v2 webSearch slot, shared search controls, navigation_pages data, and representative Page and Search previews in Theme Kit.\nEditable Site Files\nSite Files make root-level text responses manageable from Admin. microfeed provides generated defaults for robots.txt , llms.txt , and sitemap.xml , and administrators can add supported custom files such as security.txt .\nThe generated files keep crawler and machine-readable discovery current automatically. robots.txt advertises the sitemap, llms.txt summarizes the site, Published Pages, and recent items for AI tools and links enabled API documentation, and sitemap.xml includes the home page, Published Pages, Published items, and supported image or video metadata.\nEach file has a private Mustache draft with Source and Preview tabs. Format-aware highlighting helps with JSON, XML, Markdown, YAML, CSS, CSV, and other text formats, while Preview renders the exact unsaved response bytes with current site data. JSON and XML output must validate before it can be published.\nTemplates can use channel data, up to 100 newest Published items, and up to 100 most recently updated Published Pages. microfeed also stores the last valid rendered result for a published override, so a later content change that produces invalid output falls back safely instead of breaking the public file.\nGenerated files can be overridden, saved as Draft, or restored to the current microfeed default. Custom files can be created and deleted. Pages, Page path history, Site File drafts, and published overrides are included in portable snapshots and are available through the documented versioned API.\nTheme compatibility and safer automation\nFormat v2 extends the theme contract from six to eight slots with webPage and webSearch , website navigation data, editable 404 support, and complete Feed, Item, Page, Search, and RSS previews. The bundled Default theme is the reference implementation, with responsive navigation, modern search controls and results, a shared footer, and consistent rich-text spacing.\nInstalled format v1 themes remain compatible and continue rendering Feed and Item pages. Administrators can draft Pages under v1, but publishing Pages and exposing public search require an active format v2 theme. During an update, microfeed installs the bundled v2 Default theme without changing the active design, so it can be previewed and activated separately.\nTheme exports are now complete standalone Git-ready repositories. An active or specific installed theme can be exported, installed, validated, tested, and previewed independently from the microfeed application checkout.\nThe official @microfeed/cli also adds compact summary output, unwrapped reads, server-side validation-only checks, post-create verification, framed JSON input, and 24-hour idempotency keys. These options make agent-driven item creation smaller, safer to retry, and easier to recover when a request is interrupted.\nUpdating an existing Workers deployment\nIf your local repository clone is already connected to a microfeed Worker, protect any local work, update the clone, and run:\nyarn install --immutable\nyarn manage deploy\nyarn manage status The deployment applies the item-idempotency, Page, public-search, editable-404, and Site File migrations; creates the starter About Page only when its path is available; rebuilds the unified search corpus; runs project checks; builds and deploys the Worker; and verifies the result.\nYou can also open the connected repository in a local coding agent and ask:\nDeploy to Cloudflare. See the update guide , Pages and Site Files guide , and theme guide for details.\nVersion 1.0.4 makes microfeed more useful as a complete public website while preserving its feed-first, self-hosted foundation. See the full changelog for every change.","date_published":"2026-08-14T02:50:54.479Z","date_modified":"2026-08-15T02:57:33.453Z","_microfeed":{"web_url":"https://www.microfeed.org/i/new-release-v104-pages-search-and-editable-si-CSX2lDMJA5H/","json_url":"https://www.microfeed.org/i/CSX2lDMJA5H/json/","rss_url":"https://www.microfeed.org/i/CSX2lDMJA5H/rss/","guid":"CSX2lDMJA5H","status":"published","date_published_short":"Thu Aug 13 2026","date_published_ms":1786675854479}},{"id":"YcMPefM8Ote","title":"New release v1.0.3: Versioned themes and agent-friendly publishing","content_html":"We are pleased to announce microfeed v1.0.3, an update focused on versioned themes, agent-friendly content publishing, and faster content workflows.
microfeed 1.0.3 introduces immutable theme versions with isolated drafts and previews, the new @microfeed/theme-kit, an official content-management CLI with browser-controlled authorization, D1-backed item search, improved editing and media workflows, and faster public pages.
Versioned themes and modern authoring
The new theme system stores immutable theme versions in D1. Administrators can create an isolated draft, preview changes without affecting the public site, and explicitly activate a new version or roll back to an earlier one.
The yarn manage theme workflow can create, install, list, export, and activate themes, including themes hosted in public GitHub repositories. Portable snapshots now include installed theme versions and their assets.
Theme developers can use @microfeed/theme-kit to generate a starter theme, validate the theme contract, run fixture-based tests, preview a theme locally, and download JSON Feed fixtures from a microfeed site. The documented theme contract includes packaged assets, design tokens, custom fixtures, RSS stylesheets, and generic or bundled-default starting points.
Content publishing from the CLI and coding agents
Version 1.0.3 introduces the official @microfeed/cli client for managing content from a terminal or local coding agent.
The CLI uses per-instance OAuth authorization with administrator consent in the browser. Credentials stay out of prompts, and each computer appears as its own connection under Account settings. After authorization, yarn microfeed can list, search, read, create, update, and delete items; upload standalone media, cover images, and RSS enclosures; or call documented REST operations directly.
Deterministic JSON output and the bundled content-management agent skill make these workflows reliable for automation while keeping administrator passwords and API credentials private.
Faster search, editing, and publishing
Item search now runs against titles and stored plain-text content in D1. It is available from the Admin dashboard, the GET /api/v1/search/ endpoint, and the content CLI, with filters and cursor pagination.
The editor now autosaves item changes, provides clearer save and publication feedback, and improves rich-media insertion, dragging, sizing, alignment, captions, links, and native video embeds. The new Account area also provides one place to manage the administrator email and password, passkeys, active sessions, and connected CLI applications.
Public website pages, RSS, JSON Feed, and sitemap responses now use Workers Cache with content-aware invalidation. This improves response times without serving stale content after an update.
Smaller improvements
This release adds {{current_year}} for copyright text that stays current automatically, clearer guidance for built-in login and disabled API access, earlier focused deployment tests, and expanded documentation for deployment, content automation, account security, item search, theme development, and both CLIs.
Updating an existing Workers deployment
If your local repository clone is already connected to a microfeed Worker, protect any local work, update the clone, and run:
yarn install --immutable\nyarn manage deploy\nyarn manage statusThe deployment applies the OAuth, account-security, item-search, and versioned-theme migrations; normalizes existing item text for search; runs project checks; builds and deploys the Worker; and verifies the result.
You can also open the connected repository in a local coding agent and ask:
Deploy to Cloudflare.See the update guide and theme guide for details.
Version 1.0.3 makes microfeed easier to customize, automate, and operate while preserving its self-hosted foundation. See the full changelog for every change.
","content_text":"We are pleased to announce microfeed v1.0.3 , an update focused on versioned themes, agent-friendly content publishing, and faster content workflows.\nmicrofeed 1.0.3 introduces immutable theme versions with isolated drafts and previews, the new @microfeed/theme-kit , an official content-management CLI with browser-controlled authorization, D1-backed item search, improved editing and media workflows, and faster public pages.\nVersioned themes and modern authoring\nThe new theme system stores immutable theme versions in D1. Administrators can create an isolated draft, preview changes without affecting the public site, and explicitly activate a new version or roll back to an earlier one.\nThe yarn manage theme workflow can create, install, list, export, and activate themes, including themes hosted in public GitHub repositories. Portable snapshots now include installed theme versions and their assets.\nTheme developers can use @microfeed/theme-kit to generate a starter theme, validate the theme contract, run fixture-based tests, preview a theme locally, and download JSON Feed fixtures from a microfeed site. The documented theme contract includes packaged assets, design tokens, custom fixtures, RSS stylesheets, and generic or bundled-default starting points.\nContent publishing from the CLI and coding agents\nVersion 1.0.3 introduces the official @microfeed/cli client for managing content from a terminal or local coding agent.\nThe CLI uses per-instance OAuth authorization with administrator consent in the browser. Credentials stay out of prompts, and each computer appears as its own connection under Account settings. After authorization, yarn microfeed can list, search, read, create, update, and delete items; upload standalone media, cover images, and RSS enclosures; or call documented REST operations directly.\nDeterministic JSON output and the bundled content-management agent skill make these workflows reliable for automation while keeping administrator passwords and API credentials private.\nFaster search, editing, and publishing\nItem search now runs against titles and stored plain-text content in D1. It is available from the Admin dashboard, the GET /api/v1/search/ endpoint, and the content CLI, with filters and cursor pagination.\nThe editor now autosaves item changes, provides clearer save and publication feedback, and improves rich-media insertion, dragging, sizing, alignment, captions, links, and native video embeds. The new Account area also provides one place to manage the administrator email and password, passkeys, active sessions, and connected CLI applications.\nPublic website pages, RSS, JSON Feed, and sitemap responses now use Workers Cache with content-aware invalidation. This improves response times without serving stale content after an update.\nSmaller improvements\nThis release adds {{current_year}} for copyright text that stays current automatically, clearer guidance for built-in login and disabled API access, earlier focused deployment tests, and expanded documentation for deployment, content automation, account security, item search, theme development, and both CLIs.\nUpdating an existing Workers deployment\nIf your local repository clone is already connected to a microfeed Worker, protect any local work, update the clone, and run:\nyarn install --immutable\nyarn manage deploy\nyarn manage status The deployment applies the OAuth, account-security, item-search, and versioned-theme migrations; normalizes existing item text for search; runs project checks; builds and deploys the Worker; and verifies the result.\nYou can also open the connected repository in a local coding agent and ask:\nDeploy to Cloudflare. See the update guide and theme guide for details.\nVersion 1.0.3 makes microfeed easier to customize, automate, and operate while preserving its self-hosted foundation. See the full changelog for every change.","date_published":"2026-08-11T21:21:13.912Z","date_modified":"2026-08-15T02:58:49.653Z","_microfeed":{"web_url":"https://www.microfeed.org/i/new-release-v103-versioned-themes-and-agent-fri-YcMPefM8Ote/","json_url":"https://www.microfeed.org/i/YcMPefM8Ote/json/","rss_url":"https://www.microfeed.org/i/YcMPefM8Ote/rss/","guid":"YcMPefM8Ote","status":"published","date_published_short":"Tue Aug 11 2026","date_published_ms":1786483273912}},{"id":"DFh7_ZXOoMS","title":"New release v1.0.1: microfeed moves to Cloudflare Workers","url":"https://www.microfeed.org/i/DFh7_ZXOoMS/","content_html":"We are pleased to announce microfeed v1.0.1, a major foundation update to our self-hosted, open-source publishing system.
microfeed 1.0.1 replaces the runtime from Cloudflare Pages to Cloudflare Workers, and introduces a simpler deployment workflow, a rebuilt admin dashboard, portable backups, and a versioned API designed for people, applications, and AI coding agents.
The biggest change is how microfeed is deployed. Previous versions relied on Cloudflare Pages and GitHub Actions, requiring users to manually locate Cloudflare API keys and copy them into GitHub. The process was often brittle, error-prone, and required more configuration work than it should.
Starting with v1.0.1, microfeed deploys directly to Cloudflare Workers through either an AI coding agent or the yarn manage CLI. This streamlined deployment flow removes much of the manual setup and makes it faster and easier to get microfeed up and running.
Why do we move away from Cloudflare Pages? Cloudflare Pages is still supported by Cloudflare, but the platform direction has shifted. Cloudflare now recommends starting new full-stack applications on Workers and says future platform investment, optimization, and feature development will focus on Workers. Workers can serve static assets and server-rendered pages while connecting directly to D1, R2, and other Cloudflare services from one project. Cloudflare explains this direction in its Workers announcement and provides an official Pages-to-Workers migration guide.
Moving microfeed to Workers gives us a stronger foundation while making installation and day-to-day operation much easier.
Ask your coding agent for deploying and managing microfeed
microfeed’s new management workflow is designed to work naturally with local coding agents such as OpenAI Codex, Claude Code, and Cursor.
1) Start by copying microfeed to your computer:
git clone https://github.com/microfeed/microfeed.git2) Open the new microfeed folder in your coding agent and ask:
Deploy microfeed to Cloudflare.The agent can run the necessary yarn manage commands, explain each decision, initialize the required Cloudflare resources, deploy the Worker, and verify the result.
3) Stay nearby while it works. Cloudflare will open a browser page for you to sign in, and the agent may ask you to select an account or approve an important choice. You remain in control of Cloudflare authorization and your private dashboard password—never paste a Cloudflare API key, private password-creation link, or dashboard password into the conversation.
4) After deployment, open the private one-time setup page to choose your dashboard password. The agent can then run yarn manage status to confirm that the Worker, dashboard protection, D1 database, and R2 media storage are configured correctly. If setup is interrupted, ask it to continue the same deployment; the installer is designed to resume safely.
The agent can help with ongoing administration as well. For example, you can ask:
Update my microfeed instance to the latest version and verify the deployment.or
Create a backup of my microfeed site.or
Connect this repository to my existing microfeed Worker.or
Help me configure a custom domain for this microfeed site.Under the hood, the agent uses the same documented yarn manage workflow available to everyone. There is no separate agent-only deployment system, and you can run every command yourself whenever you prefer.
A rebuilt admin experience
The admin dashboard has been rebuilt around an Astro server-rendered shell with more consistent navigation, responsive layouts, accessible controls, and dark mode.
![](\"https://media-cdn.microfeed.org/production/media/rich-editor/items/DFh7_ZXOoMS/image-d6cc089aa24a17ace00a56f9acd4ee14.png\")
Portable backups and safer migrations
microfeed can now create portable snapshots containing:
- D1 data and schema history
- R2 media objects
- File checksums
- The migration information required to validate a restore
A snapshot can be restored into a verified clean deployment or pulled into a new local instance for testing. This makes it easier to test production data safely, move an installation, and maintain independent backups.
A versioned API foundation
The microfeed API now has a canonical, versioned base path:
/api/v1/The new API foundation includes:
- Multiple named API keys
- Generated OpenAPI 3.1 documentation
- A self-hosted interactive API explorer
- Self-contained LLM.txt for AI coding agents
- Separate controls for API access and public API documentation
Existing unversioned API endpoints remain available as backward-compatible aliases.
New documentation
We have also launched docs.microfeed.org, a new documentation site.
The documentation is designed for people using microfeed directly and for AI coding agents helping them operate or extend an installation via Markdowns.
Updating an existing Workers deployment
If your git-cloned repo is already connected to a microfeed Worker, update the code and run:
yarn install --immutable\nyarn manage deploy\nyarn manage statusOr simply ask your ai coding agent:
Deploy microfeed to cloudflare for [your custom domain name]The deployment command automatically applies database migrations, runs project checks, builds and deploys the Worker, and verifies the result.
See the complete update guide for more information.
Migrating an older Cloudflare Pages installation
If your microfeed instance still runs on Cloudflare Pages, begin with:
yarn manage migrate-pagesThe migration creates a new Worker connected to your existing D1 database and R2 bucket. It does not immediately remove the original Pages project. Both projects can remain connected to the same data while you test the Worker and decide when to move the custom domain.
See the snapshot and migration guide for the complete process.
What remains the same
microfeed remains an open-source, self-hosted publishing system designed to help you own your content and domain.
You can continue publishing text, images, audio, video, and documents through a customizable website, podcast-compatible RSS, and JSON Feed. Your metadata remains in D1, your media remains in R2, and your site runs on Cloudflare’s global network.
Version 1.0.1 gives that original idea a much stronger foundation for future improvements.
","content_text":"We are pleased to announce microfeed v1.0.1 , a major foundation update to our self-hosted, open-source publishing system.\nmicrofeed 1.0.1 replaces the runtime from Cloudflare Pages to Cloudflare Workers, and introduces a simpler deployment workflow, a rebuilt admin dashboard, portable backups, and a versioned API designed for people, applications, and AI coding agents.\nThe biggest change is how microfeed is deployed. Previous versions relied on Cloudflare Pages and GitHub Actions, requiring users to manually locate Cloudflare API keys and copy them into GitHub. The process was often brittle, error-prone, and required more configuration work than it should.\nStarting with v1.0.1, microfeed deploys directly to Cloudflare Workers through either an AI coding agent or the yarn manage CLI . This streamlined deployment flow removes much of the manual setup and makes it faster and easier to get microfeed up and running.\nWhy do we move away from Cloudflare Pages? Cloudflare Pages is still supported by Cloudflare, but the platform direction has shifted. Cloudflare now recommends starting new full-stack applications on Workers and says future platform investment, optimization, and feature development will focus on Workers. Workers can serve static assets and server-rendered pages while connecting directly to D1, R2, and other Cloudflare services from one project. Cloudflare explains this direction in its Workers announcement and provides an official Pages-to-Workers migration guide .\nMoving microfeed to Workers gives us a stronger foundation while making installation and day-to-day operation much easier.\nAsk your coding agent for deploying and managing microfeed\nmicrofeed’s new management workflow is designed to work naturally with local coding agents such as OpenAI Codex, Claude Code, and Cursor.\n1) Start by copying microfeed to your computer:\ngit clone https://github.com/microfeed/microfeed.git 2) Open the new microfeed folder in your coding agent and ask:\nDeploy microfeed to Cloudflare. The agent can run the necessary yarn manage commands, explain each decision, initialize the required Cloudflare resources, deploy the Worker, and verify the result.\n\n3) Stay nearby while it works. Cloudflare will open a browser page for you to sign in, and the agent may ask you to select an account or approve an important choice. You remain in control of Cloudflare authorization and your private dashboard password—never paste a Cloudflare API key, private password-creation link, or dashboard password into the conversation.\n4) After deployment, open the private one-time setup page to choose your dashboard password. The agent can then run yarn manage status to confirm that the Worker, dashboard protection, D1 database, and R2 media storage are configured correctly. If setup is interrupted, ask it to continue the same deployment; the installer is designed to resume safely.\nThe agent can help with ongoing administration as well. For example, you can ask:\nUpdate my microfeed instance to the latest version and verify the deployment. or\nCreate a backup of my microfeed site. or\nConnect this repository to my existing microfeed Worker. or\nHelp me configure a custom domain for this microfeed site. Under the hood, the agent uses the same documented yarn manage workflow available to everyone. There is no separate agent-only deployment system, and you can run every command yourself whenever you prefer.\nA rebuilt admin experience\nThe admin dashboard has been rebuilt around an Astro server-rendered shell with more consistent navigation, responsive layouts, accessible controls, and dark mode.\n\nPortable backups and safer migrations\nmicrofeed can now create portable snapshots containing:\nD1 data and schema history\nR2 media objects\nFile checksums\nThe migration information required to validate a restore\nA snapshot can be restored into a verified clean deployment or pulled into a new local instance for testing. This makes it easier to test production data safely, move an installation, and maintain independent backups.\nA versioned API foundation\nThe microfeed API now has a canonical, versioned base path:\n/api/v1/ The new API foundation includes:\nMultiple named API keys\nGenerated OpenAPI 3.1 documentation\nA self-hosted interactive API explorer\nSelf-contained LLM.txt for AI coding agents\nSeparate controls for API access and public API documentation\nExisting unversioned API endpoints remain available as backward-compatible aliases.\nNew documentation\nWe have also launched docs.microfeed.org , a new documentation site.\nThe documentation is designed for people using microfeed directly and for AI coding agents helping them operate or extend an installation via Markdowns .\nUpdating an existing Workers deployment\nIf your git-cloned repo is already connected to a microfeed Worker, update the code and run:\nyarn install --immutable\nyarn manage deploy\nyarn manage status Or simply ask your ai coding agent:\nDeploy microfeed to cloudflare for [your custom domain name] The deployment command automatically applies database migrations, runs project checks, builds and deploys the Worker, and verifies the result.\nSee the complete update guide for more information.\nMigrating an older Cloudflare Pages installation\nIf your microfeed instance still runs on Cloudflare Pages, begin with:\nyarn manage migrate-pages The migration creates a new Worker connected to your existing D1 database and R2 bucket. It does not immediately remove the original Pages project. Both projects can remain connected to the same data while you test the Worker and decide when to move the custom domain.\nSee the snapshot and migration guide for the complete process.\nWhat remains the same\nmicrofeed remains an open-source, self-hosted publishing system designed to help you own your content and domain.\nYou can continue publishing text, images, audio, video, and documents through a customizable website, podcast-compatible RSS, and JSON Feed. Your metadata remains in D1, your media remains in R2, and your site runs on Cloudflare’s global network.\nVersion 1.0.1 gives that original idea a much stronger foundation for future improvements.","date_published":"2026-08-06T22:37:41.167Z","date_modified":"2026-08-15T03:00:23.886Z","_microfeed":{"web_url":"https://www.microfeed.org/i/new-release-v101-microfeed-moves-to-cloudflare-DFh7_ZXOoMS/","json_url":"https://www.microfeed.org/i/DFh7_ZXOoMS/json/","rss_url":"https://www.microfeed.org/i/DFh7_ZXOoMS/rss/","guid":"DFh7_ZXOoMS","status":"published","itunes:episodeType":"full","date_published_short":"Thu Aug 06 2026","date_published_ms":1786055861167}},{"id":"frJLel6J2W-","title":"New release v0.1.5: Upgrade to Wrangler v4 and Tailwind v4","url":"https://www.microfeed.org/i/new-release-v015-upgrade-to-wrangler-v4-and-tai-frJLel6J2W-/","content_html":"Since the inception of the microfeed project, we've been using Cloudflare Wrangler v2.x. With the recent update, Wrangler now runs on v4, and we've upgraded accordingly. Sticking with the older version would have led to a cascade of breaking changes that would be increasingly difficult to manage over time. By upgrading incrementally now, we reduce future technical debt and ensure a smoother transition for upcoming updates.
Additionally, we've upgraded Tailwind CSS—the framework we use to style the admin UI—to its latest version. This update also introduces breaking changes that we need to address. Upgrading now positions us to avoid more complex challenges down the road.
","content_text":"Since the inception of the microfeed project , we've been using Cloudflare Wrangler v2.x. With the recent update, Wrangler now runs on v4, and we've upgraded accordingly . Sticking with the older version would have led to a cascade of breaking changes that would be increasingly difficult to manage over time. By upgrading incrementally now, we reduce future technical debt and ensure a smoother transition for upcoming updates.\n\nAdditionally, we've upgraded Tailwind CSS —the framework we use to style the admin UI—to its latest version. This update also introduces breaking changes that we need to address. Upgrading now positions us to avoid more complex challenges down the road.","date_published":"2025-03-14T23:39:48.424Z","date_modified":"2025-03-14T23:47:03.558Z","_microfeed":{"web_url":"https://www.microfeed.org/i/new-release-v015-upgrade-to-wrangler-v4-and-tai-frJLel6J2W-/","json_url":"https://www.microfeed.org/i/frJLel6J2W-/json/","rss_url":"https://www.microfeed.org/i/frJLel6J2W-/rss/","guid":"frJLel6J2W-","status":"published","itunes:episodeType":"full","date_published_short":"Fri Mar 14 2025","date_published_ms":1741995588424}},{"id":"Asz44We3XZP","title":"Migrating Your Microfeed Instance from D1 Alpha to D1 Production","url":"https://www.microfeed.org/i/migrating-your-d1-database-before-cloudflare-depre-Asz44We3XZP/","content_html":"Microfeed relies on Cloudflare's D1 database to store metadata. If you set up a Microfeed instance last year or earlier, it's likely running on the D1 alpha version. Recently, Cloudflare announced plans to discontinue and eventually delete databases created with D1 alpha. To keep your existing Microfeed instances functioning, migration from the alpha to the production version of D1 is necessary.
This guide will walk you through the process of migrating your Microfeed D1 alpha database to the production version.
Email Notification from Cloudflare
Cloudflare has sent out notifications regarding the depreciation and subsequent deletion of D1 alpha databases. This announcement necessitates action from our users to prevent any loss of functionality.
![](\"https://media-cdn.microfeed.org/microfeed-org/production/media/rich-editor/items/Asz44We3XZP/image-97339ae28bc966fa30f7b22424ab6ae7.png\")
Migration Steps
Migrating your database involves two primary steps:
- Copying your existing D1 database to a new one.
- Configuring your Microfeed instance to connect to the new database.
Step 1: Copy Your Existing D1 Database
The migration process begins with creating a copy of your current database:
- Export your existing database to SQL: Use the Wrangler CLI to authenticate with wrangler login.
- Identify your existing database: Run wrangler d1 list and wrangler d1 info <database_name> to confirm it's an alpha version.
- Create a backup: Execute wrangler d1 backup create <database_name> and download the backup with wrangler d1 backup download <database_name> <backup_id> --output db.sqlite3.
- Generate an SQL dump: Convert the downloaded SQLite3 database file into an SQL dump using sqlite3 db.sqlite3 .dump > db.sql.
With the SQL dump ready, proceed to set up a new D1 production database:
- Create a new database: Run wrangler d1 create <new_database_name>, appending _v1 (or _new) to differentiate from the alpha version.
- Restore data: Import your SQL dump into the new database with wrangler d1 execute <new_database_name> --remote --file=./db.sql.
- Verify creation: Confirm the new database setup by checking with wrangler d1 info <new_database_name> and manually inspecting data via your Cloudflare dashboard.
Step 2: Update Your Microfeed Instance
Reconfigure your Microfeed instance to connect to the new database:
1) Update your codebase: Ensure your Microfeed fork is up-to-date on GitHub.
![](\"https://media-cdn.microfeed.org/microfeed-org/production/media/rich-editor/items/Asz44We3XZP/image-fc704755e3b2d7990cc80c128becec9c.png\")
2) Set a new environment secret: Add the D1_DATABASE_NAME secret on GitHub with the name of your new D1 database (<new_database_name>).
![](\"https://media-cdn.microfeed.org/microfeed-org/production/media/rich-editor/items/Asz44We3XZP/image-372ae0af69c70a7e05c0382bdef12a9f.png\")
3) Deploy changes: Re-deploy your Microfeed instance by triggering the deploy GitHub action.
![](\"https://media-cdn.microfeed.org/microfeed-org/production/media/rich-editor/items/Asz44We3XZP/image-c7e2e6be9f8211cebd8850b84bce7b68.png\")
Testing and Validation
After migration, create an unlisted item in your Microfeed admin panel to verify that the new item appears in the new D1 database. This test confirms that the migration was successful.
Conclusion
Unfortunately, Cloudflare does not provide a one-click solution for this migration. However, following these detailed steps should guide you through the process smoothly. If you encounter any issues or have questions, please reach out to us at support@microfeed.com. We're here to help ensure your transition is as seamless as possible.
","content_text":"Microfeed relies on Cloudflare's D1 database to store metadata. If you set up a Microfeed instance last year or earlier, it's likely running on the D1 alpha version. Recently, Cloudflare announced plans to discontinue and eventually delete databases created with D1 alpha. To keep your existing Microfeed instances functioning, migration from the alpha to the production version of D1 is necessary.\nThis guide will walk you through the process of migrating your Microfeed D1 alpha database to the production version.\nEmail Notification from Cloudflare\nCloudflare has sent out notifications regarding the depreciation and subsequent deletion of D1 alpha databases. This announcement necessitates action from our users to prevent any loss of functionality.\n\nMigration Steps\nMigrating your database involves two primary steps:\nCopying your existing D1 database to a new one.\nConfiguring your Microfeed instance to connect to the new database.\nStep 1: Copy Your Existing D1 Database\nThe migration process begins with creating a copy of your current database:\nExport your existing database to SQL: Use the Wrangler CLI to authenticate with wrangler login .\nIdentify your existing database: Run wrangler d1 list and wrangler d1 infoWe are pleased to announce the release of microfeed v0.1.2.
With the introduction of a comprehensive CRUD API in this new release, microfeed empowers users to seamlessly create, update, and delete content programmatically.
To harness the power of the new CRUD API, users must navigate to the /admin/settings/ page in their microfeed dashboard. Here, a simple toggle option allows you to enable the API, unlocking a world of possibilities for content management automation. Once enabled, you can begin integrating microfeed into your existing workflows or build entirely new applications that interact with the platform.
![](\"https://media-cdn.microfeed.org/microfeed-org/production/media/rich-editor/items/ZQxgQnG71PC/image-05caf1d8f526c0e964db776e91fd2634.png\")
To ensure a smooth integration process, microfeed has provided a comprehensive documentation page for the new API release. Accessible at /json/openapi on a microfeed instance (e.g., https://www.microfeed.org/json/openapi), the documentation guides users through the various endpoints, request structures, and response formats supported by the API.
We encourage all users to update their forked repo to the latest version of microfeed and re-deploy to Cloudflare. Thank you for your continued support, and we look forward to hearing your feedback on the latest release of microfeed: support@microfeed.org
","content_text":"We are pleased to announce the release of microfeed v0.1.2 .\nWith the introduction of a comprehensive CRUD API in this new release, microfeed empowers users to seamlessly create, update, and delete content programmatically.\nTo harness the power of the new CRUD API, users must navigate to the /admin/settings/ page in their microfeed dashboard. Here, a simple toggle option allows you to enable the API, unlocking a world of possibilities for content management automation. Once enabled, you can begin integrating microfeed into your existing workflows or build entirely new applications that interact with the platform.\n\nTo ensure a smooth integration process, microfeed has provided a comprehensive documentation page for the new API release. Accessible at /json/openapi on a microfeed instance (e.g., https://www.microfeed.org/json/openapi ), the documentation guides users through the various endpoints, request structures, and response formats supported by the API.\nWe encourage all users to update their forked repo to the latest version of microfeed and re-deploy to Cloudflare . Thank you for your continued support, and we look forward to hearing your feedback on the latest release of microfeed: support@microfeed.org","date_published":"2023-05-15T02:42:00.081Z","date_modified":"2026-08-15T03:04:07.114Z","_microfeed":{"is_audio":true,"is_document":false,"is_external_url":false,"is_video":false,"is_image":false,"web_url":"https://www.microfeed.org/i/new-release-v012-introducing-microfeeds-powerf-ZQxgQnG71PC/","json_url":"https://www.microfeed.org/i/ZQxgQnG71PC/json/","rss_url":"https://www.microfeed.org/i/ZQxgQnG71PC/rss/","guid":"ZQxgQnG71PC","status":"published","duration_hhmmss":"00:01:32","itunes:episodeType":"full","date_published_short":"Sun May 14 2023","date_published_ms":1684118520081}},{"id":"BprBswbLr1y","title":"New release v0.1.1: Follow-up improvements after the initial launch of v0.1.0","attachments":[{"url":"https://media-cdn.microfeed.org/microfeed-org/production/media/audio-bd99c7997f0e181e3c4ad411a1160292.mp3","mime_type":"audio/mpeg","size_in_byte":1014845,"size_in_bytes":1014845,"duration_in_seconds":89}],"url":"https://www.microfeed.org/i/new-release-v011-followup-improvements-after-th-BprBswbLr1y/","content_html":"We are pleased to announce the release of microfeed v0.1.1.
We launched the first version of microfeed (v0.1.0) around 50 days ago, and since then, we've received numerous bug reports, feature requests, and other useful feedbacks . We would like to express our gratitude to all our users for their valuable contributions.
This latest release (v0.1.1) brings three main categories of changes, which include bug fixes, DevOps-related improvements, and adding the OpenAPI spec for json feed. Specifically, we have added the OpenAPI spec in YAML and HTML, which will provide greater clarity and ease of use for our users.
One notable use case of microfeed is as a headless CMS. With our admin dashboard, human editors can easily publish content, while custom code (such as scripts or mobile apps) or third-party software (such as Zapier or Hugo) can consume content via microfeed's JSON feed. For example, you can find our website's JSON feed at microfeed.org/json.
We encourage all users to update their forked repo to the latest version of microfeed and re-deploy to Cloudflare. Thank you for your continued support, and we look forward to hearing your feedback on the latest release of microfeed: support@microfeed.org
","content_text":"We are pleased to announce the release of microfeed v0.1.1 .\nWe launched the first version of microfeed (v0.1.0) around 50 days ago, and since then, we've received numerous bug reports , feature requests, and other useful feedbacks . We would like to express our gratitude to all our users for their valuable contributions.\nThis latest release (v0.1.1) brings three main categories of changes, which include bug fixes, DevOps-related improvements, and adding the OpenAPI spec for json feed. Specifically, we have added the OpenAPI spec in YAML and HTML , which will provide greater clarity and ease of use for our users.\nOne notable use case of microfeed is as a headless CMS. With our admin dashboard, human editors can easily publish content, while custom code (such as scripts or mobile apps) or third-party software (such as Zapier or Hugo ) can consume content via microfeed's JSON feed. For example, you can find our website's JSON feed at microfeed.org/json .\nWe encourage all users to update their forked repo to the latest version of microfeed and re-deploy to Cloudflare . Thank you for your continued support, and we look forward to hearing your feedback on the latest release of microfeed: support@microfeed.org","date_published":"2023-02-17T23:21:28.106Z","date_modified":"2026-08-15T03:03:54.447Z","_microfeed":{"is_audio":true,"is_document":false,"is_external_url":false,"is_video":false,"is_image":false,"web_url":"https://www.microfeed.org/i/new-release-v011-follow-up-improvements-after-t-BprBswbLr1y/","json_url":"https://www.microfeed.org/i/BprBswbLr1y/json/","rss_url":"https://www.microfeed.org/i/BprBswbLr1y/rss/","guid":"BprBswbLr1y","status":"published","duration_hhmmss":"00:01:29","itunes:episodeType":"full","date_published_short":"Fri Feb 17 2023","date_published_ms":1676676088106}},{"id":"uhbQEmArlC2","title":"Introducing microfeed: A Self-Hosted, Open-Source CMS on Cloudflare (open alpha)","attachments":[{"url":"https://media-cdn.microfeed.org/microfeed-org/production/media/audio-ae5b0090a232669a014b073b3c793501.mp3","mime_type":"audio/mpeg","size_in_byte":1512767,"size_in_bytes":1512767,"duration_in_seconds":160}],"url":"https://www.microfeed.org/i/ntroducing-microfeed-uhbQEmArlC2/","content_html":"In today's digital world, feeds play a vital role in the way we consume and share information. Whether it's a podcast feed of audio content, a YouTube channel full of videos, or a social media account with tweets or photos, feeds have become a cornerstone of the internet.
However, with the increasing importance of freedom of speech, it's easy to get de-platformed from centralized hosting services like YouTube, Twitter, and Instagram. These services have the power to delete your account and all of your content, leaving you with no way to share your message.
That's where microfeed comes in. As a self-hosted, open-source CMS on Cloudflare, microfeed allows you to create your own feed of content (text, audio, video, images, etc.) and host it under your own custom domain. This way, you can own your data and your domain name, reducing the risk of being de-platformed and giving you the ability to migrate your data to a different platform if needed.
microfeed is currently in open alpha, so use it at your own risk. However, it's already a powerful tool that makes it easy to create and manage your own feed. The self-hosted microfeed instance is deployed via GitHub Actions and runs on Cloudflare's serverless platform, taking advantage of products like Pages, R2, D1, and Zero Trust.
Your microfeed instance can distribute content through a customizable website, an RSS feed (compatible with podcast RSS), and a JSON feed. And with the simple, yet powerful admin dashboard, adding new content to your feed is a breeze.
To get started with microfeed, you'll need to fork the repository to your personal or organizational GitHub account and set up Cloudflare API tokens as secrets. From there, you can use a predefined GitHub Action to deploy the code to Cloudflare Pages and set up custom domains and security settings in the Cloudflare dashboard.
While the initial setup may sound complex, future deployments are as easy as clicking a button on GitHub Actions. In the future, we hope to see Cloudflare offer a \"Login with Cloudflare\" OAuth feature to make the process even easier for users.
For detailed installation instructions, visit the microfeed repository on GitHub:
If you have any questions or feedback, don't hesitate to reach out to us at support@microfeed.org. We're excited to see what you create with microfeed!
","content_text":"In today's digital world, feeds play a vital role in the way we consume and share information. Whether it's a podcast feed of audio content, a YouTube channel full of videos, or a social media account with tweets or photos, feeds have become a cornerstone of the internet.\nHowever, with the increasing importance of freedom of speech, it's easy to get de-platformed from centralized hosting services like YouTube, Twitter, and Instagram. These services have the power to delete your account and all of your content, leaving you with no way to share your message.\nThat's where microfeed comes in. As a self-hosted, open-source CMS on Cloudflare , microfeed allows you to create your own feed of content (text, audio, video, images, etc.) and host it under your own custom domain. This way, you can own your data and your domain name, reducing the risk of being de-platformed and giving you the ability to migrate your data to a different platform if needed.\nmicrofeed is currently in open alpha, so use it at your own risk. However, it's already a powerful tool that makes it easy to create and manage your own feed. The self-hosted microfeed instance is deployed via GitHub Actions and runs on Cloudflare's serverless platform, taking advantage of products like Pages , R2 , D1 , and Zero Trust .\nYour microfeed instance can distribute content through a customizable website, an RSS feed (compatible with podcast RSS ), and a JSON feed . And with the simple, yet powerful admin dashboard, adding new content to your feed is a breeze.\nTo get started with microfeed, you'll need to fork the repository to your personal or organizational GitHub account and set up Cloudflare API tokens as secrets. From there, you can use a predefined GitHub Action to deploy the code to Cloudflare Pages and set up custom domains and security settings in the Cloudflare dashboard.\nWhile the initial setup may sound complex, future deployments are as easy as clicking a button on GitHub Actions. In the future, we hope to see Cloudflare offer a \"Login with Cloudflare\" OAuth feature to make the process even easier for users.\nFor detailed installation instructions, visit the microfeed repository on GitHub :\n\nIf you have any questions or feedback, don't hesitate to reach out to us at support@microfeed.org . We're excited to see what you create with microfeed!","date_published":"2022-12-27T08:25:00.000Z","date_modified":"2026-08-15T03:03:32.879Z","_microfeed":{"is_audio":true,"is_document":false,"is_external_url":false,"is_video":false,"is_image":false,"web_url":"https://www.microfeed.org/i/introducing-microfeed-a-self-hosted-open-source-uhbQEmArlC2/","json_url":"https://www.microfeed.org/i/uhbQEmArlC2/json/","rss_url":"https://www.microfeed.org/i/uhbQEmArlC2/rss/","guid":"uhbQEmArlC2","status":"published","duration_hhmmss":"00:02:40","itunes:episodeType":"full","date_published_short":"Tue Dec 27 2022","date_published_ms":1672129500000}}],"_microfeed":{"microfeed_version":"1.0.7","base_url":"https://www.microfeed.org","categories":[{"name":"Technology"}],"subscribe_methods":[{"name":"RSS","type":"rss","url":"https://www.microfeed.org/rss/","image":"https://www.microfeed.org/assets/brands/subscribe/rss.png","enabled":true,"editable":false,"id":"eeYmI-JX4Xp"},{"name":"JSON","type":"json","url":"https://www.microfeed.org/json/","image":"https://www.microfeed.org/assets/brands/subscribe/json.png","enabled":true,"editable":false,"id":"xIyGLXyRTdt"}],"description_text":"microfeed is an agentic, lightweight, open-source CMS that runs in your Cloudflare account. microfeed gives you a website, RSS and JSON feeds, a private dashboard, and an API for integrations or coding agents.","copyright":"©2017 - 2026 Listen Notes, Inc.","itunes:type":"episodic","itunes:email":"support@microfeed.org","items_sort":"published_at","items_order":"desc"}}