Spacefast - Agent First Publishing  🔗 **Source:** [Spacefast - Agent First Publishing](https://www.youtube.com/watch?v=Nd1zRIe-M7k) > [!note]+ Document Notes > tags: [agent-first-publishing, static-site-hosting, ai-coding-agents, wordpress-static-export, developer-experience] > author: Jonathan Bossenger > source: Jonathan Bossenger (YouTube livestream) > reference: https://www.youtube.com/watch?v=Nd1zRIe-M7k > date created: 2026-09-14 > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > # 🏷️ Title: Spacefast - agent first publishing > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [Spacefast home page](https://spacefast.com/): "Home for what your agent makes," built by Automattic, research preview, pricing tiers. - [Spacefast FAQ](https://spacefast.com/faq/): WordPress.com account login, six-hour claim window. - [Spacefast docs: WordPress on every Space](https://github.com/spacefast/docs): source file `content/(dynamic)/wordpress.mdx`. - [Spacefast WordPress plugin README](https://github.com/spacefast/wordpress) - [Spacefast CLI README](https://github.com/spacefast/cli) - [Spacefast agent plugins README (Claude Code, Claude Desktop, Codex, Cursor)](https://github.com/spacefast/plugins) - [Jonathan Bossenger, About](https://jonathanbossenger.com/about/) - [The Repository, Sept. 14](https://www.therepository.email/matt-mullenweg-returns-as-automattic-ceo-with-full-support-of-the-board-but-whos-on-it-remains-unclear) ## 📝 Summary - **What happened:** Jonathan Bossenger, a Developer Advocate on Automattic's Developer Relations team, ran a 58-minute Friday livestream testing Spacefast, an Automattic publishing service for files and apps that AI agents build. They published a 3D browser game ("Cosmic Defender 3D," caption spelling; unverified) from the `sf` CLI, connected a GitHub repository through the dashboard, and tried the WordPress static-export path through the Spacefast WordPress plugin and Simply Static. - **Results in the stream:** The CLI login, the CLI publish, and the Git publish all produced live URLs. The game's assets failed to load until the speaker removed a base path hardcoded for GitHub Pages. The WordPress export of a site with three posts and three pages stalled and ended with an error the captions render as "excess updates to option publish state blocked" (caption spelling; unverified). - **Why it matters:** Spacefast's own docs say a WordPress install backs every Space, exposes WP-CLI through `sf wp`, and publishes Abilities callable with short-lived tokens. That makes it a WordPress-powered platform whose primary client is an AI agent, not a person in wp-admin. - **Key stakeholders:** Automattic's Spacefast team (GitHub org created 2026-06-07); Batuhan İçöz, named Head of Spacefast by The Repository; developers publishing agent-built apps; WordPress site owners who want static output; the Simply Static plugin maintainers, whose plugin does the crawl. - **Risks and tradeoffs:** Static WordPress export drops dynamic features. The plugin README states "Dynamic WordPress features still need a static-compatible replacement." Remote `sf wp` returns only success or failure, not WP-CLI output. The WordPress plugin ships as a GitHub release zip, and a WordPress.org directory search for "spacefast" returned 0 results on 2026-09-14. - **Bottom line:** The speaker's verdict is that the static and Git paths worked on the first or second try and the WordPress path didn't finish. Their main feedback is progress visibility and a way to reach the dashboard from the CLI. ## 📖 Main Content - **The core argument.** The speaker frames Spacefast as "agent first, dashboard second." In their description of traditional hosting you add a site in a dashboard, then upload files by FTP or SSH. In Spacefast you publish from the agent or CLI first and add custom domains in the dashboard later. - **What Spacefast is, per its own pages.** The home page calls it "The publishing layer for your agents" and says Automattic builds it. The FAQ says login uses "A WordPress.com account." Both pages say it's in research preview with a waitlist. Late in the stream the speaker says it has "been around for maybe a month." - **Pricing, per the home page and FAQ (fetched 2026-09-14).** Free is $0 with 10 GB storage and 3 custom domains. Plus is $4.99/month or $49.99/year with 50 GB and 10 domains. Pro is $49.99/month or $499/year with 200 GB and unlimited domains. The FAQ says "Static serving is not metered on any plan." The speaker didn't discuss pricing. - **How agents publish.** - CLI: install with `curl -fsSL https://spacefast.com/install.sh | bash` or `npm install -g spacefast`, then run `sf publish ./dist`. The CLI README lists package version `0.0.1`. - Agent plugins: the `spacefast/plugins` repo ships plugins for Claude Code, Claude Desktop, Codex, and Cursor. Each one "includes the instructions and MCP configuration its client needs." - MCP: Glama's third-party registry lists a Spacefast MCP connector at `https://mcp.spacefast.com` using Streamable HTTP and OAuth. At 46:13 the speaker says Spacefast isn't "an MCP for static GitHub agents" but "a way to quickly publish to a thing." - Anonymous publish: the docs say an unclaimed Space serves for 6 hours, the key stays valid 7 more days, and no anonymous Space lives past 30 days. - Git: connect a repository, and pushes publish. - **The WordPress path, per the plugin README.** The plugin has two modes. Static WordPress uses Simply Static to generate files, then a Spacefast delivery step hashes and uploads them as a version. Headless CMS mode triggers a repository build when public content changes, after a 60-second quiet window. The plugin "never reads drafts, WordPress credentials, or the database." - **Data sources, per the docs.** A data source is a public WordPress site that a repository build reads over the REST API, exposed to the build as `WORDPRESS_URL`. The docs say data sources reach "repository builds only," so a local `sf publish` never sees them. The speaker read this page aloud at 38:02 and 38:29. - **WordPress behind every Space.** The docs page "WordPress on every Space" says "Every Space is backed by a WordPress install." The same page says Storage is its media library, Database is its MySQL, and Zero apps run on it. At 54:23 and 56:00 the speaker reacts to this and asks why a Space can't host a regular WordPress site. - **Terms.** - *Space*: one published site or app with its own versions. - *Claim link*: a URL fragment carrying the `sfc_` key that moves an anonymous Space into a team. - *Simply Static*: a WordPress.org plugin (version 3.8.13, 30,000+ active installs per the WordPress.org API) that crawls a site into static files. - *Zero*: Spacefast's runtime for apps with a database, per its docs. - **Context.** [[3. Resources/Readwise/Articles/Matt Mullenweg Returns as Automattic CEO With ‘Full Support of the Board’ — But Who’s on It Remains Unclear|The Repository, Sept. 14]] names Batuhan İçöz as Head of Spacefast and calls it "a new agent-first hosting service at Automattic." Their GitHub profile lists their company as "@Spacefast (an @Automattic execution)." The vault copy of that note doesn't contain the Spacefast sentence. This analysis relies on a search-result excerpt of the article because the page returned HTTP 403 to a direct fetch. - **Uncertainties and contested claims.** - Telex sunset: at 3:01 a viewer named Cameron asks about Telex (captioned "TX") being sunset. The speaker says they weren't involved in that decision. On 2026-09-14 the telex.automattic.ai page showed no shutdown notice, and web searches found no announcement. The sunset stays unverified. - Frameworks: the speaker lists "Astro, Viprace, Gatsby, Angular, Vine, Solola, Jekal" (caption spelling). The docs table lists Astro, VitePress, Gatsby, Angular, Vite, SolidStart, and Jekyll among 25 rows. - Laravel: the speaker guesses Laravel apps could work at 49:52, then doubts it at 55:11. Every row in the docs frameworks table produces static output, and no Laravel row appears. - Dashboard link: the speaker guesses the docs and dashboard links on the home page were added mid-stream. That's unverified. ### ✔️ What was and wasn't verified - **Verified against first-party pages:** - Spacefast's description, builder, pricing, and research-preview status (spacefast.com, /faq). - The CLI install commands, `sf open [TARGET]` ("Open a space in your browser"), and `sf versions ls` (CLI README and CLI.md). - The agent plugins and MCP configuration (spacefast/plugins). - The WordPress plugin's `GPL-2.0-or-later` header and version 0.5.7 (spacefast-wordpress.php). - The WordPress plugin modes and the data-flow limits (spacefast/wordpress). - WordPress behind every Space, anonymous-publish timing, data sources, and the frameworks table (spacefast/docs source files). - Jonathan Bossenger's role (jonathanbossenger.com/about). - Simply Static's version and install count (WordPress.org API). - Telex's existence (WordPress.com blog, 2025-09-23). - Studio Code (developer.wordpress.com docs). - **Checked only that the URL resolves (HTTP 200), content not reviewed:** - WordPress Abilities API docs. - WordPress/abilities-api and WordPress/mcp-adapter on GitHub. - WordPress.com MCP docs. - The `@wordpress/create-block` package page. - **Not verified:** - The Telex sunset. - The error string at 53:29. - The app names "Cosmic Defender 3D" and "Consilium," and the viewer name "Cameron." - Which AI assistant fixed the base path. The captions say "co-pilot" at 23:33 and "Claude in the terminal" at 10:38. - Whether the WordPress publish completed after the stream ended. - **Video frames weren't checked.** This analysis uses the auto-caption transcript only. Where the speaker clicks through the dashboard without narrating, these notes don't describe what they clicked. ## 🗒️ Notes #### ⏱️ [0:51](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=51) Introducing Spacefast - The speaker describes Spacefast as a publishing platform built by Automattic colleagues. You connect it to your agent, and the agent publishes with a live URL. - Their default for publishing web apps is GitHub Actions. #### ⏱️ [2:31](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=151) Four publish paths - The speaker names four publish paths: no account, git, CI, and a WordPress site. > [!quote] ID:rw_01m2g44yserte41v01m59f64vq > you can publish without an account, you can publish from git, you can publish from CI, but you can also build from a WordPress site. #### ⏱️ [3:01](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=181) Viewer question on Telex - A viewer asks about Telex (captioned "TX") being sunset. The speaker says they weren't on the Telex team or part of the sunset decision. - The speaker's own Telex stream a year earlier built a Minesweeper block. Their feedback then was that Telex should scaffold with the `create-block` tool. - They say Telex learnings went into the WordPress.com AI site builder and WordPress Studio. For people who miss Telex, they suggest Studio Code. #### ⏱️ [9:18](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=558) Tools become recommendations, not workflow - The speaker says their job is to "explore, try, show." Tools land on a recommendation list, such as an MCP plugin they reviewed one or two weeks earlier. - They edit personal sites locally and have also made changes through the WordPress.com MCP. #### ⏱️ [12:21](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=741) Product-use policy (speaker's statements) - The speaker says Automattic doesn't require staff to use Automattic products. - They say their hosting is with Pressable (captioned "Pressible") and that they run some sites on WordPress.com. These are the speaker's statements about their own setup. #### ⏱️ [14:05](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=845) Install and login - The speaker installs the CLI and confirms `sf` works. - Login asks for an email address and sends a one-time code. - A consent screen lists permissions: create and publish sites, manage domains and DNS, invite team members. The speaker reads aloud that deleting sites needs temporary approval and that the tool can't remove team members. - The approval lasts 30 days, per the speaker's reading at 16:19. #### ⏱️ [17:32](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=1052) First publish - `sf publish` of only `index.html` creates a Space and a version in seconds. The live URL loads a page, but the game needs more files. - Publishing a folder with extra arguments fails with "Unexpected arguments." - After building the app, the published game still can't find `assets/index`. #### ⏱️ [23:33](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=1413) Base-path fix - An AI assistant finds that the build is "hardcoded for pages," meaning GitHub Pages. - After removing that base path and rebuilding, the republished game loads. #### ⏱️ [26:55](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=1615) Versions and finding the dashboard - `sf versions` lists four versions of the Space. - The speaker can't find the dashboard from the CLI and reaches `my.spacefast.com` by logging in again during the 28:25 segment. - The CLI reference includes `sf open [TARGET]`, which the speaker didn't use. #### ⏱️ [32:42](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=1962) Dashboard features - The speaker reads out the dashboard features: custom domains, storage, an enableable database, environment variables, a code view, and builds. #### ⏱️ [35:09](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=2109) Git publish - The speaker connects a GitHub repository for a school festival app through a GitHub app install. - Enabling "publish on every push" publishes the app live with no build settings. #### ⏱️ [38:02](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=2282) WordPress data sources - The speaker reads the docs: point a repository build at a public WordPress site, read content over the REST API, and publish static output. - They learn a Space needs a connected repository before a data source does anything. #### ⏱️ [40:13](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=2413) WordPress plugin install - The speaker downloads the Spacefast WordPress plugin, installs it on a test site, and chooses static WordPress. The plugin installs Simply Static. - They note the plugin quick start doesn't require the waitlist. #### ⏱️ [43:37](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=2617) Waiting on the export - Progress sits at 16%, then 44%. - The speaker wants a clearer status overview. They ask how forms and other dynamic features would work, and whether the WordPress install needs its own subdomain. #### ⏱️ [45:36](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=2736) Agent-first feedback - The speaker says command-line use fits agent-first, "But for the WordPress stuff, you do need to be able to do some dashboardy things." - Their definition: "AI first publishing." You build locally with an agent, say "publish to space fast," and add a custom domain later. #### ⏱️ [47:16](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=2836) Home page and Vercel - The speaker reads the home page line "ship whatever your agent makes in seconds." - They compare the idea to Vercel (captioned "Versel") while saying they've never used Vercel. #### ⏱️ [48:33](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=2913) Dashboard-first versus agent-first - The speaker contrasts cPanel-style hosting (add site, `public_html`, FTP or SSH upload) with agent-first publishing. > [!quote] ID:rw_01m2g457t99mf9r611k6733aqn > So it's kind of agent first, dashboard second whereas traditional web hosting is kind of dashboard first um and then all the other stuff second. #### ⏱️ [49:52](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=2992) Laravel speculation - The speaker compares Spacefast with the GitHub Pages base-path problem from earlier: "this just works." - They guess Laravel and Ruby apps could publish. The docs framework table lists static builders only. #### ⏱️ [51:25](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=3085) Database, auth, email - The speaker points to the home page's MySQL-compatible database, built-in authentication, and transactional email. - Their planned next test is an app with signup, email, and a customer database, built after an upcoming WordCamp trip and leave. #### ⏱️ [53:29](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=3209) WordPress publish stalls - The export of three posts and three pages runs long and ends with a blocked-update error. - The speaker then reads that every Space runs WordPress. > [!quote] ID:rw_01m2g453vtaqfhhg8nn1kxhrxd > apparently every space runs a WordPress site behind it. Static files, so it's actually using it's actually using WordPress to power all of this. #### ⏱️ [56:31](https://www.youtube.com/watch?v=Nd1zRIe-M7k&t=3391) Wrap-up - The speaker says Spacefast started as "upload a file, drop a file" and has grown since. - Everything worked except the WordPress site. They want to know why a Space can't host a WordPress, Laravel, or Drupal site. - The stream pauses for at least three weeks. ## 📚 References - [Spacefast home](https://spacefast.com/): first-party product description and pricing. - [Spacefast FAQ](https://spacefast.com/faq/): first-party account and claim rules. - [Spacefast docs site](https://spacefast.com/docs/), with source at [spacefast/docs](https://github.com/spacefast/docs). Pages used: WordPress on every Space, Build from a WordPress site, Frameworks and builds, Database, Publish without an account. - [spacefast/wordpress](https://github.com/spacefast/wordpress): plugin README with the Static WordPress and Headless CMS modes. - [spacefast/cli](https://github.com/spacefast/cli): install commands and CLI reference. - [spacefast/plugins](https://github.com/spacefast/plugins): agent plugins with MCP configuration. - [Glama MCP connector listing for Spacefast](https://glama.ai/mcp/connectors/io.github.spacefast/mcp): third-party registry; endpoint and transport only. - [Jonathan Bossenger, About](https://jonathanbossenger.com/about/): Developer Advocate, Automattic Developer Relations since March 2025. - [batuhan on GitHub](https://github.com/batuhan): company field "@Spacefast (an @Automattic execution)." - [Simply Static on WordPress.org](https://wordpress.org/plugins/simply-static/) - [Telex Turns Everyone into a WordPress Block Developer, WordPress.com News, 2025-09-23](https://wordpress.com/blog/2025/09/23/telex-turns-everyone-into-a-wordpress-block-developer/) - [Studio Code, WordPress.com Developer Resources](https://developer.wordpress.com/docs/developer-tools/studio/studio-code/) - [@wordpress/create-block package reference](https://developer.wordpress.org/block-editor/reference-guides/packages/packages-create-block/) - [Abilities API, WordPress Developer Resources](https://developer.wordpress.org/apis/abilities/) - [WordPress/mcp-adapter](https://github.com/WordPress/mcp-adapter) ## 🗣️ Paraphrase - **Opening (0:51–2:31).** The speaker is trying an Automattic-built service that takes whatever an agent builds and puts it at a live URL. They normally deploy with GitHub Actions. They want to test four paths: no account, git, CI, and WordPress. - **Telex detour (3:01–9:18).** Asked about Telex, the speaker says they had no role in it and last used it a year ago. Their feedback then was to scaffold with `create-block`. They now point people to Studio Code. - **Workflow and product policy (9:18–14:05).** The speaker's job is trying tools and showing them, so most tools become recommendations, not daily use. They say Automattic doesn't require staff to use its own products. - **CLI publish (14:05–26:55).** Login is an emailed code plus a consent screen. The first publish works in seconds, but the game's assets fail until a GitHub Pages base path comes out of the build. - **Dashboard and Git (26:55–38:02).** Versions list from the CLI, but reaching the dashboard takes a re-login. Connecting a GitHub repo publishes a second app with no build settings. - **WordPress (38:02–45:36).** The plugin installs Simply Static and starts an export. Progress stays unclear, and the speaker asks how forms would work. - **Assessment (45:36–53:29).** The speaker calls the model agent first, dashboard second, compared with dashboard-first hosting. They want better progress feedback and plan to test auth, email, and a database next. - **Close (53:29–58:38).** The WordPress export errors out. The speaker learns WordPress backs every Space and asks why it can't host a full WordPress site. ## 📰 Newsletter - **Spacefast gets a first live test.** In a 58-minute stream, Automattic developer advocate Jonathan Bossenger publishes a browser game from the `sf` CLI, a festival app from a GitHub repo, and a small WordPress site through Simply Static. Two of the three went live; the WordPress export stalled at a blocked-update error. - **For WordPress developers:** Spacefast's docs say a WordPress install backs every Space, with WP-CLI through `sf wp` and Abilities callable with short-lived tokens. [Read the plugin README](https://github.com/spacefast/wordpress) for the Static WordPress and Headless CMS modes, including its 60-second rebuild window. - **Gotcha worth a bookmark:** if an app built for GitHub Pages loads a blank page elsewhere, check for a hardcoded base path. That's the fix the stream needed at 25:27. - **Pricing and status, per [spacefast.com](https://spacefast.com/):** research preview with a waitlist. The free tier has 10 GB storage and 3 custom domains. ## ✅ Action Items #### DevRel - Developer advocacy: record a host-agnostic 15-minute demo that takes one Studio-built site through Simply Static to static files. Show the base-path check from 25:27 as the first debugging step. Measure it by counting viewer questions about blank pages in the first 30 days. - Education: write an office-hours prompt set on "agent publishes, human configures domains," using the stream's four publish paths (no account, git, CI, WordPress) as the lesson outline. - Developer experience: turn the stream's four friction points into a checklist for reviewing any agent-publishing tool. The four: CLI to dashboard access (the speaker missed `sf open`), export progress (stuck at 16% and 44%), argument errors ("Unexpected arguments"), and base-path detection. - Developer marketing: Not applicable to this source. The stream markets no WordPress.org program, and hosting neutrality rules out promoting the product. - Community management: log the viewer's Telex sunset question (3:01) as an unresolved community rumor. Check it against a first-party announcement before repeating it; telex.automattic.ai showed no notice on 2026-09-14. - Internal/external/cross-project: send the Spacefast docs team (spacefast/docs, last pushed 2026-09-13) the gap between the data sources page and the plugin flow. The speaker read about data sources before learning that plugin static mode doesn't use them. #### OSPO - Policy & Governance: Not applicable to this source. It covers no contribution policy or charter. - License Compliance: GitHub's license detector reports `NOASSERTION` for spacefast/wordpress, but the plugin header in `spacefast-wordpress.php` declares `GPL-2.0-or-later` (version 0.5.7, requires WordPress 6.5 and PHP 8.1), and its LICENSE file carries GPL text. spacefast/cli, plugins, and docs report no license (checked 2026-09-14); clear that before reusing their docs or code in WordPress.org material. - Security Management: review the OAuth scope model in the plugin README ("authorize exactly one Team"; tokens "stored in non-autoloaded options"). Also review the consent screen the speaker read at 15:36 as a reference pattern for scoped agent credentials. - Software Inventory: the plugin is installed from a GitHub release zip, not WordPress.org (directory search returned 0 results). Inventories should record its update channel. - Developer Support: Not applicable to this source. No internal tooling or legal guidance is discussed. - Community Engagement: Simply Static (30,000+ active installs) does the crawl in Spacefast's WordPress mode. Track whether Spacefast upstreams fixes or funding to Simply Static. - Strategic Alignment: Not applicable to this source. No KPIs or OKRs are stated. #### Community - Maintainers: Simply Static maintainers can use the stalled 3-post, 3-page export at 53:29 as a report lead once someone reproduces it with logs. - Contributors: Not applicable to this source. It offers no contribution path. - Sponsors: Not applicable to this source. It includes no budgets or sponsorship. - Ecosystem: Not applicable to this source. It describes no incident or disclosure. #### WordPress - Core: Not applicable to this source. No Core ticket or release is discussed. - Core Performance: Not applicable to this source. The stream reports no timing numbers beyond "seconds" for a publish. - Core AI: collect Spacefast's documented use of Abilities ("call the Abilities its runtime publishes with a token you mint from the API") as a third-party adoption case. Check it against the [Abilities API docs](https://developer.wordpress.org/apis/abilities/): which abilities it registers and how the short-lived token maps to capabilities. Draft one eval task for AI evaluation sets: "agent publishes a static build and reports the live URL," scored on whether the URL loads assets. - Core Program Team: Not applicable to this source. No cross-team release work is involved. - Mobile: Not applicable to this source. No mobile app is involved. - Playground: build a Playground blueprint with Simply Static and three posts and three pages. Time the export offline to separate Simply Static crawl time from the delivery step that stalled at 53:29. - Community: Not applicable to this source. The speaker mentions travel to a WordCamp but no event program. - Training: draft a Learn WordPress lesson outline on reading content over the REST API during a static build. Base it on the `WORDPRESS_URL` pattern and keep it host-agnostic. - Marketing: Not applicable to this source. Hosting neutrality applies, and no WordPress.org campaign is discussed. - Support: add a forum reply snippet for "my exported static site has no forms," quoting the plugin README line that dynamic features "still need a static-compatible replacement." - Design: note the progress-feedback gap (16% and 44% with no stage names) as a UX pattern to avoid in wp-admin long-running tasks. - Documentation: check whether DevHub's REST API handbook has an example of fetching posts during a static build. If not, draft one. Add a HelpHub note on relative asset paths for static exports, citing the GitHub Pages base-path failure at 23:33. - Photos: Not applicable to this source. No media library content is involved. - TV: Not applicable to this source. It's a YouTube livestream, not a WordPress.tv submission. - Polyglots: Not applicable to this source. It's English only, with no translation discussion. - Accessibility: the auto-captions mangle product names ("Space Fast," "Pressible," "Versel," "Jekal"). Any clip reused in WordPress training needs corrected captions. - Meta: track the pattern of WordPress plugins distributed only as GitHub release zips (the Spacefast plugin is one) as input for plugin directory discovery and update-channel tooling. - CLI: Spacefast's docs say remote `sf wp` returns only success or failure, never WP-CLI output. File this as a use case for the WP-CLI team: remote command runners that need structured output. - Hosting: add "does remote WP-CLI return command output?" to cross-host checklists. Spacefast's docs answer no for remote runs. - Tide: Not applicable to this source. No plugin scoring is discussed. - Openverse: Not applicable to this source. No openly licensed media is involved. - Themes: Not applicable to this source. No theme work is shown or narrated. - Plugins: review the Spacefast WordPress plugin (v0.5.7, GPL-2.0-or-later) for provenance: it ships as a GitHub release zip and, per its README, can install and activate Simply Static for you. Do this before any directory-related guidance. #### The WPOCC - Programs: Not applicable to this source. No fellowship or grant program is involved. - Projects: Not applicable to this source. No governance clinic topic is raised. - Funding experiments: Not applicable to this source. No funding model is discussed. #### FAIR - Technical independence: the Spacefast WordPress plugin ships outside WordPress.org via GitHub releases. Check whether its release zips carry checksums or signatures FAIR tooling could verify. - Policies and covenants: Not applicable to this source. No funding or anti-capture policy is discussed. - Productized governance artifacts: Not applicable to this source. No charter or scorecard is involved. ## 🧪 Hypotheses - H1: An app built with a hardcoded GitHub Pages base path fails to load assets on any root-path static host. Removing the base path fixes it on 100% of those hosts. - H2: Adding `sf open` to the output of `sf publish` cuts the time a first-time user needs to reach the dashboard, measured against the roughly 5 minutes between 26:55 and 31:45. - H3: Spacefast's Static WordPress stall scales with the Simply Static background step count, not content size. A 6-item site stalls at the same stage as a 600-item site. - H4: Named stage labels in export progress ("crawling," "uploading," "activating") reduce "is it done?" support questions against percent-only progress. - H5: Agents asked to "publish this project" pick the correct output directory from the docs framework table for 25 listed frameworks without human correction. ### 📊 Methodology - H1: build the same Vite app with and without `base: '/repo/'`, publish to three root-path static hosts, and record asset 404 counts. - H2: run a moderated usability test with 10 developers new to the CLI, timing from first publish to the dashboard page with and without a printed dashboard link. - H3: export WordPress sites of 6, 60, and 600 posts through the plugin, logging each Simply Static step and the stage where the publish state changes. - H4: A/B test two progress UIs in a wp-admin prototype and count help-link clicks and abandoned exports. - H5: give an agent 25 sample repos, one per framework row, and score output-directory choices against the docs table. ### ❓ Questions - Why does a Space that already runs WordPress not offer a hosted WordPress site mode, and is that a product choice or a technical limit? - Which Abilities does a Space's WordPress register, and are they documented in the Abilities API format? - What did "publish state blocked" mean at 53:29, and did the version go live after the stream ended? - Will the WordPress plugin, already GPL-2.0-or-later, go to the WordPress.org directory? - How does Headless CMS mode's 60-second quiet window behave under bulk imports of thousands of posts? ### 🔮 Future Research - Test the database, authentication, and transactional email features with a signup app, which is the speaker's own planned next step. - Compare the stream's first-hour experience with the docs once the research-preview waitlist opens. Measure friction, not vendors. - Audit the MCP connector at `mcp.spacefast.com` against the MCP spec, since Glama listed it "Unhealthy" on 2026-09-14. - Track whether the Telex sunset question gets a first-party answer. ### 💡 Implications - **Practice:** WordPress becomes a backend that agents reach through WP-CLI and Abilities, with no human in wp-admin. DevRel material needs agent-facing examples alongside screenshots. - **Policy:** plugins shipped only as GitHub zips sit outside WordPress.org review. Site owners carry the provenance check. - **Security:** Spacefast's scoped OAuth (one team, non-autoloaded tokens, approval before site deletion) is a concrete pattern for agent credentials that plugin authors can compare against application passwords. - **Education:** the base-path bug is a recurring static-hosting failure worth teaching in any static export lesson. - **Funding models:** Simply Static does the crawl in Spacefast's WordPress mode, so a commercial service depends on a community plugin with 30,000+ installs. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade Level 3.8 and Flesch Reading Ease 86.6. Computed on the auto-caption transcript: 6,277 words, 592 sentence breaks, and 8,120 estimated syllables. Caption punctuation is machine-inserted, so sentence counts are approximate. #### 👀 Visual learners - Present: a live product walkthrough. The video frames weren't checked, so this analysis can't say which steps appear visually. - Improve: a publish-flow diagram (agent → `sf publish` → Space → version → custom domain) and a labeled image of the WordPress plugin settings. #### 🔊 Aural learners - Present: 58 minutes of continuous narration with the speaker reading docs aloud (38:02, 38:29, 40:13). - Improve: a 3-minute audio recap of the four publish paths and the three results. #### 🗣️ Verbal learners - Present: the speaker defines "agent first, dashboard second" in plain words at 49:12. - Improve: a glossary for Space, claim link, data source, and Zero. #### 🧩 Kinesthetic learners - Present: a follow-along CLI session with real errors and fixes. - Improve: a checklist for the base-path fix and a sandbox repo to publish. #### 🧠 Logical learners - Present: a sequence of attempt, error, and fix at 17:32–25:27. - Improve: a decision table (static folder, Git repo, WordPress static, WordPress headless) with prerequisites for each. #### 🧑‍🤝‍🧑 Social learners - Present: live chat questions from a viewer at 3:01 and 7:30. - Improve: a follow-up thread collecting viewers' own publish attempts. #### 🧘‍♀️ Solitary learners - Present: the speaker explicitly figures things out alone ("I was able to figure everything out by myself"). - Improve: self-check questions such as "why did assets 404?" #### 🌿 Naturalistic learners - Present: Not applicable to this source. No environmental framing appears. - Improve: note that static serving avoids running PHP per request, per the docs line that a static Space "never touches" its WordPress. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: YouTube auto-captions exist, and this transcript came from them. Chapter markers weren't checked. - Improve: add YouTube chapters at the 21 timestamps in these notes. #### Keyboard navigation - Present: Not applicable to this source. It's a video on YouTube's player; no custom interface was evaluated. - Improve: Not applicable to this source. #### Contrast and readability - Present: not assessed. The video frames weren't checked, so terminal and dashboard contrast is unknown. - Improve: use a large terminal font and a high-contrast theme for CLI streams (WCAG 1.4.3, 4.5:1). #### Text resizing and reflow - Present: Not applicable to this source. Video text doesn't reflow. - Improve: publish command snippets as text in the description so viewers can zoom (WCAG 1.4.4). #### Media and captions - Present: auto-captions with name errors ("Space Fast," "Pressible," "Versel," "Jekal," "work campus" for WordCamp). - Improve: upload corrected captions (WCAG 1.2.2, 1.2.4 for live) and a downloadable transcript. #### Forms and interactions - Present: the speaker reads the login consent screen aloud (15:36), which helps non-visual viewers. - Improve: read error messages verbatim; the 53:29 error survives only as a garbled caption. #### Standards reference - Gaps map to WCAG 2.2 AA 1.2.2 Captions (Prerecorded), 1.2.4 Captions (Live), 1.2.5 Audio Description (Prerecorded), and 1.4.3 Contrast (Minimum). ### 🌍 DEIB Assessment #### Cultural breadth - Present: the speaker is based in Cape Town and mentions a WordPress South Africa community site and a Durban school festival app. - Improve: link the WordPress South Africa community for viewers in the region. #### Inclusive language - Present: plain language, and jargon ("CI," "DNS," "static") mostly goes undefined. - Improve: define "static site" and "CI" once for new viewers. #### Neurodiversity support - Present: the speaker narrates each step and names their own mistakes ("I can't spell today"). Topic jumps between Telex, product policy, and the demo break the structure. - Improve: chapters and a short agenda at the start. #### Representation - Present: one speaker, plus viewer chat from one named participant. - Improve: invite a Spacefast team member or a WordPress user testing the static export as a guest. #### Psychological safety - Present: the speaker says staff aren't required to use company products and contrasts that with a former employer where carrying a competitor's shopping bag caused "trouble." - Improve: Not applicable to this source. No moderation issue arises in the transcript. ### ✅ Logical Validity #### Strong reasoning - Causal diagnosis (23:33–25:27): the speaker hypothesizes that the GitHub Pages base path breaks asset loading, removes it, republishes, and the game loads. The test confirms the cause. Clarify it by naming the config key changed, which the captions don't give. - Inductive, bounded (56:31): "I haven't had any issues getting things to work except for the WordPress the actual WordPress site." The claim is limited to what the speaker tested: two static apps and one WordPress site. - Analogical (48:33–49:12): dashboard-first hosting versus agent-first publishing compares the order of steps, which the speaker lists concretely (add site, folder, FTP or SSH). Strengthen it with a timed comparison. #### Fallacies - **Hasty generalization (49:52).** After two static publishes, the speaker says "you could probably publish Laravel apps to this" and "Ruby apps." The docs framework table lists only static-output builders, and the speaker reverses the guess at 55:11. Fix: limit the claim to the tested static builds, or cite the framework table. Highlight: rw_01m2g45jexzr5e5yas6ez7eg20. - **Hasty generalization, trend form (49:52–50:43).** "It's kind of the way we're probably going to be publishing in the future" rests on one product tried for under an hour. Fix: frame it as a personal expectation and name what evidence would confirm it. #### Tone of voice - Exploratory and self-deprecating: "Good grief. I can't spell today" (20:50) and "Who knows?" (54:23). - Candid about limits: "I don't know anything about this, but I was able to figure everything out by myself" (50:43) and "I've never used the cell, so I can't say" (47:16). ### 🛡️ DARVO Analysis - Deny: Not applicable to this source. No accusation is made. The speaker's statement that they weren't involved in the Telex sunset decision (3:01) answers a question and discloses their role; it doesn't deny wrongdoing. - Attack: Not applicable to this source. No accuser or critic is addressed. - Reverse victim/offender: Not applicable to this source. No conflict framing appears. - Emotional cues: none relevant to DARVO. The tone stays curious and upbeat, with laughter at 4:45, 8:12, and 28:25. ## 🎯 Conclusion - **Bottom line:** in one hour, Spacefast's CLI and Git paths published two apps to live URLs. The WordPress static path didn't finish. Spacefast's own docs confirm the finding that surprised the speaker: WordPress backs every Space. - **Next steps for readers:** - Read the [WordPress plugin README](https://github.com/spacefast/wordpress) for the plugin's data limits before planning a static export. - Check apps built for GitHub Pages for a hardcoded base path. - Watch for the speaker's follow-up test of auth, email, and database features, which they say is at least three weeks away. ## 🔄 Refactor Appendix — Spacefast - agent first publishing ### 📚 Literature Atoms #### [H1] Spacefast offers four publish paths including WordPress > [!quote] ID:rw_01m2g44yserte41v01m59f64vq > you can publish without an account, you can publish from git, you can publish from CI, but you can also build from a WordPress site. **Context & use**: - 2:31, the stream's stated test plan. - Frames the WordPress path as one of four entry points, which the Spacefast docs confirm: anonymous publish, Git, CI, and the WordPress plugin. **Tags**: #xref **Highlight**: [view highlight](https://read.readwise.io/read/01m2g44yserte41v01m59f64vq) <!-- atomicity: 1 idea ✓ --> #### [H2] WordPress runs behind every Spacefast Space > [!quote] ID:rw_01m2g453vtaqfhhg8nn1kxhrxd > apparently every space runs a WordPress site behind it. Static files, so it's actually using it's actually using WordPress to power all of this. **Context & use**: - 54:23, right after the WordPress export errors. - Spacefast's "WordPress on every Space" doc confirms it. This is the fact that ties the product to WP-CLI and the Abilities API. **Tags**: #xref #share **Highlight**: [view highlight](https://read.readwise.io/read/01m2g453vtaqfhhg8nn1kxhrxd) <!-- atomicity: 1 idea ✓ --> #### [H3] Agent-first publishing puts the dashboard second > [!quote] ID:rw_01m2g457t99mf9r611k6733aqn > So it's kind of agent first, dashboard second whereas traditional web hosting is kind of dashboard first um and then all the other stuff second. **Context & use**: - 49:12, the speaker's summary definition. - A reusable framing for DevRel talks about AI agents and WordPress; attribute it to the speaker when quoted. **Tags**: #xref #articleseed **Highlight**: [view highlight](https://read.readwise.io/read/01m2g457t99mf9r611k6733aqn) <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates #### [P1] Agent-first publishing inverts the hosting setup order **Claim** (one sentence, Courtney's voice): When an agent is the publisher, the live URL comes first and account, domain, and dashboard configuration follow it. **Evidence pointer**: [[#H3]] **Scope & conditions**: Holds for static and Git publishes, which went live before any dashboard step in the stream. Fails for the WordPress plugin path, which needed wp-admin and dashboard steps first (45:36). **Links** (≥1 with annotation): - [[3. Resources/Readwise/Articles/Matt Mullenweg Returns as Automattic CEO With ‘Full Support of the Board’ — But Who’s on It Remains Unclear|The Repository, Sept. 14]] — because evidence-for Spacefast being described as an agent-first hosting service <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Confirm or drop the Telex sunset claim from the 3:01 viewer question — https://telex.automattic.ai/ #fleeting #inbox - [F2] Read the Abilities a Space's WordPress registers, per the "WordPress on every Space" doc — https://github.com/spacefast/docs #fleeting #inbox - [F3] Check whether Spacefast WordPress plugin release zips carry checksums or signatures — https://github.com/spacefast/wordpress #fleeting #inbox ### → Things 3 - [ ] Draft a DevHub REST API example for reading posts during a static build — Spacefast data sources doc, `WORDPRESS_URL` pattern #things - [ ] Map Spacefast's documented Abilities use against the Abilities API docs for Core AI — spacefast/docs wordpress.mdx #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Spacefast - Agent First Publishing.md|Spacefast - Agent First Publishing by Jonathan Bossenger]] ## Highlights - [2:31] things is number one apparently it's really easy to publish with this. Um there's like you can publish without an account, you can publish from git, you can publish from CI, but you can also build from a WordPress site. Um so I kind of want to check that out as well. Um, I don't know if I'm going to have enough time for that. [laughter] I just want to see I just want to kind of see how this works. This has been, you know, this has been something that that people have been building and I've kind of heard about and I haven't really had a chance to look at it. So, that's [3:01] the plan today is just to have a look at it. Um, so it looks like I need to have a space CLI installed. Um, sign in option option sign in publish folder put on my domain. So that's what I looks like I need to go. Cameron says thoughts on TX being sunset. Um, so I was never part of the original like project team that built TX. Um, so I I wasn't involved in the in the decision to sunset it. Um, I do know that it was intended to be an experiment in the world of like AI block building. ([View Highlight](https://read.readwise.io/read/01m2g44yserte41v01m59f64vq)) - Note: Four publish paths named at the top of the stream: no account, git, CI, and a WordPress site. Spacefast docs confirm anonymous publish, Git, CI, and the WordPress plugin. - Tags: atom/literature/h1 - [45:36] Um, my big piece of feedback now is just that the and maybe that's just the way I am, but I like to be able to go through the processes and see all the things working. Feel like this is very much like agent first, which I guess is the way things are right now. So, you wouldn't worry about going to the dashboard. you would just, you know, run things from the from the command line. But for the WordPress stuff, you do need to be able to do some dashboardy things. [46:13] Um, so Uh, I wouldn't say it's an MCP for static GitHub agents. It's more like a way to quickly publish to a thing. Um, so it's kind of it's kind of AI first publishing, if you will. Um, so you've built something with your agent, you have an app that works on your local host, you now want to stick it somewhere on the web. Um, you could then just say publish to space fast and it would be there. And then once you're ready for a custom domain, you can add a custom domain and that kind of thing. ([View Highlight](https://read.readwise.io/read/01m2g45crjcyrsysdw1hs89xjt)) - Note: DX feedback to act on: the WordPress path needs dashboard steps and progress visibility that the CLI-first path doesn't. The CLI does ship `sf open [TARGET]`, which the stream didn't use. - Tags: action/h1 - [48:33] Yeah, there we go. There we go. So, if you look at traditional hosting, it's a case of login and then you have like x amounts of sites and yeah, I have 10 sites that I can create. So, first I add a site. um if it was C panel you know you create you create a folder or you create a site or whatever it has a public HTML this you know and then from there then you upload your files via FTP or SSH or whatever the case is but you do everything in the dashboard first and then you upload what you want. This is very much like my take on this is very [49:12] much you work from your agent. Um you then publish to spacefast and then your custom domains and all that kind of stuff comes later through the dashboard. So it's kind of agent first, dashboard second whereas traditional web hosting is kind of dashboard first um and then all the other stuff second. Um, I like the fact that you can kind of just publish it. Like if you've ever tried to publish something to GitHub pages, it is a pain to get it working. ([View Highlight](https://read.readwise.io/read/01m2g457t99mf9r611k6733aqn)) - Note: The speaker's own framing: agent first, dashboard second, against a dashboard-first order of add site, create folder, upload by FTP or SSH. - Tags: atom/zettel/z1, atom/literature/h3 - [49:52] Um, as you saw when I first started, I had to like hardcode a subdomain to get it to work. Whereas this just works. You know, it just takes whatever the root stuff is, publishes it to the space, and it seems to just work. Um, it's it it it's capable of doing a lot. So, you could probably publish Laravel apps to this. You could probably publish Ruby apps to this, you know, as long as I mean, it has all of these frameworks as options. Astro, Viprace, Gatsby, Angular, Vine, Solola, Jekal doesn't have Laravel in here, but it probably could work with the Laravel app. Um, so it's kind of it's kind of the way [50:43] we're probably going to be publishing in the future. Um, well that's GitHub pages with extra steps I wouldn't say is a good explanation, but that's kind of how people are publishing apps now. Like when you build an app, you don't want to have to worry about where it's going. You just want it to go. which you want to be published. Um, so it's like turning the whole the whole way publish on its head. Um, what I do like about it is how fairly simple everything was. Like I don't know anything about this, but I was able to figure everything out by myself. Um, I just feel like like giving me better ([View Highlight](https://read.readwise.io/read/01m2g45jexzr5e5yas6ez7eg20)) - Note: Two static publishes lead to "could probably publish Laravel apps." The Spacefast frameworks doc lists static-output builders only, and the speaker walks it back at 55:11. - Tags: fallacy/hasty-generalization - [53:29] um that would require some kind of customer database and then try and ship that and see how that process works. Um because I don't think my examples are very good [snorts] to be honest. Um this is still going forever. I wouldn't have expected this site to take so long because there's hardly any content on it. There's like three posts, three pages. Um, excess updates to option publish state blocked. Okay, something went wrong somewhere. [54:23] Um, what does that mean? Who knows? Okay, I'm going to call it a wrap there, folks. Um, that was interesting. Um, the WordPress stuff, I I I hope that it was the case that I could actually host a WordPress site here. Um, this doesn't seem to be the case. Um, apparently every space runs a WordPress site behind it. Static files, so it's actually using it's actually using WordPress to power all of this. ([View Highlight](https://read.readwise.io/read/01m2g453vtaqfhhg8nn1kxhrxd)) - Note: The WordPress static publish of a 3-post, 3-page site didn't finish on stream. Spacefast's "WordPress on every Space" doc confirms a WordPress install backs every Space. - Tags: atom/literature/h2