Skip to content

Send OpenFuse readers to OpenBot from the top of the README - #233

Draft
jerelvelarde wants to merge 1 commit into
mainfrom
jerel/2026-11-19/readme-openbot-block
Draft

jerelvelarde wants to merge 1 commit into
mainfrom
jerel/2026-11-19/readme-openbot-block

Conversation

@jerelvelarde

Copy link
Copy Markdown
Collaborator
Before (main) After (this branch)
Top of the README on main Top of the README on this branch

The problem

OpenFuse is the one skin whose README never got its OpenBot pointer. #220 added one on November 4, but it was written under the old name and was closed unmerged after the rename (#224, #225). So on main, OpenBot first appears at line 213, in the architecture diagram, and nothing links to open.bot. The "OpenBot compatibility" paragraph below it also opens by calling OpenFuse "independent of OpenBot". That is true of this repo's client, but it reads as if OpenFuse has nothing to do with OpenBot, when OpenBot ships an OpenFuse skin.

The approach

This redoes #220 under the new name, in the same shape the OpenDots and OpenDuet READMEs now have:

  • Lead line under the tagline. "OpenFuse is now available as a UX skin in OpenBot", with OpenBot linked to open.bot, followed by two buttons in OpenBot's own colors: one to open.bot, and one to the OpenBot repository showing its live star count.
  • Badge. "also a skin in OpenBot" joins the CI and license badges, linked to open.bot.
  • Skin capture and call to action. The capture of OpenBot running the skin sits above the hero call to action, which now reads "Bringing OpenFuse to your company? Talk to us about OpenBot →", as Lead with OpenMuse as a skin in OpenBot, and show it #220 had it. Its link and ref=openfuse_hero are unchanged, so the CTA keeps its attribution.
  • "OpenFuse and OpenBot" section before Demo, with the same who-starts-where table as the other two repos.
  • "OpenBot compatibility" now says this repo's client runs without OpenBot, and that the skin in OpenBot is OpenBot's own app with OpenFuse's look. The adapter details are unchanged.

Links meant to send a reader to try or learn about OpenBot go to open.bot. The quick-start row goes to OpenBot on GitHub.

The capture is #220's image, renamed to assets/openbot-openfuse-skin.png. It was taken on OpenBot's main branch on November 4 and shows no project name, so it is still accurate after the rename.

What is not covered

  • The capture predates OpenBot 1.0. It matches the skin's layout, but it was not retaken.
  • docs/OPENBOT-INTEGRATION.md and the disabled adapter are untouched.
  • The repository has no About homepage. Setting one is a repo setting, so it is left for a separate decision.

Verification

  • CI on main has failed since Link to the repository under its new name #225 (November 17) in the browser job's pnpm test:browser, before this branch. This PR changes only README.md and adds one PNG.
  • Biome, the repo's formatter and linter, doesn't read Markdown, so no check covers README.md.
  • The screenshots above are GitHub's own render of README.md at 1280 px wide: before is main at 67580f1, after is this branch.
  • app/src/skins/openfuse ships in OpenBot v1.1.1, and the skin is picked under Settings → Skin.

Merge notes

#223, the duplicate rename PR, still rewrites README.md and now conflicts with main as well as with this branch. Main already has the rename, so #223 should close rather than merge.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant