Skip to content

feat: enable standard.site publishing (blog + material) - #108

Merged
fmalcher merged 1 commit into
mainfrom
feat/standard-site-publisher
Jul 22, 2026
Merged

feat: enable standard.site publishing (blog + material)#108
fmalcher merged 1 commit into
mainfrom
feat/standard-site-publisher

Conversation

@fmalcher

Copy link
Copy Markdown
Member

Enables the site's standard.site (AT Protocol) publishing by adopting the publisher from website-articles-build and wiring angular-buch.com's config into CI. Publishes both blog posts and material chapters as site.standard.document records.

Changes

Before this goes live

Add the repo secret BSKY_APP_PASSWORD (Settings → Secrets and variables → Actions) — a Bluesky app password for the angular-buch.com account. Until it's set, the publish step is a no-op, so merging this alone changes nothing.

What happens once the secret exists

On each article-data build, the publisher upserts one site.standard.publication record + one site.standard.document per non-hidden blog post and material chapter (rkey = slug) to the angular-buch.com PDS, and prunes stale ones. The existing trigger-website-rebuild chain then redeploys the website, whose verification artifacts are added in angular-schule/angular-buch-website#64.

Dry run against current content: 1 publication + 53 blog + 10 material = 63 documents.

Details & config keys: build/STANDARD-SITE.md.

Bump the build submodule to the version that publishes standard.site records,
and wire angular-buch.com's publication config into the article-data build.

- build: 0bb1055 -> 775a3d1 (standard.site publisher, blog + material)
- build-article-data.yml: add BSKY_APP_PASSWORD secret + publication env

Publishing is a no-op until the BSKY_APP_PASSWORD repo secret is added.
@fmalcher
fmalcher force-pushed the feat/standard-site-publisher branch from 311656d to 2fbd964 Compare July 22, 2026 13:00
@fmalcher
fmalcher merged commit 51c81fa into main Jul 22, 2026
@fmalcher
fmalcher deleted the feat/standard-site-publisher branch July 22, 2026 13:01
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