brmbh — landing page

Marketing site for the brmbh agentic WordPress suite.

Static HTML/CSS/JS. No build step, no dependencies — open index.html to work on it.

index.html      the landing page
docs.html       command reference
assets/         styles.css, main.js, logos/
deploy.sh       rsync to all-inkl

Deploying

Hosted on all-inkl, on its own vhost:

https://wordpress.brombach.de/
→ /www/htdocs/w00bc6c9/wordpress.brombach.de/

./deploy.sh          # dry run — shows the diff, writes nothing
./deploy.sh --live   # upload

rsync over the allinkl SSH alias. --delete is destructive, so the script refuses to run unless the target is the wordpress.brombach.de vhost.

Why its own vhost

It used to live at brombach.de/wordpress-suite/ — a subdirectory of a vhost deployed from a different repo with rsync --delete. Every deploy of that site silently deleted this one (live 2026-07-24, gone by 2026-07-29), and the URL kept returning HTTP 200 because the parent site's index.html was served as a fallback. Nothing looked broken.

Verify content, not status codes

curl -sS https://wordpress.brombach.de/ | grep -o '<title>[^<]*</title>'

A 200 alone proves nothing on shared hosting — check what came back.

Keeping copy honest

The install commands shown here must match what actually works. They have drifted before — npx create-brmbh was advertised for weeks while returning a 404, because it was never published as its own package.

Current truth:

Path	Command
Agent	npx skills add brmbh/wordpress, then ask for a new brmbh theme
Command	npx @brmbh/cli create my-site
Clone	git clone https://github.com/brmbh/wordpress.git then npm install

If the CLI's interface changes, update this site in the same pass — the README, the hero, and docs.html are three separate surfaces and they have fallen out of sync before.

History

Extracted from brmbh/cli on 2026-07-29 with git subtree split, so the 33 commits of site history came along. That repo is being archived.