Admin queue
Use Queue social post after unlocking the vault. Writes a queue file via the GitHub Contents API — not a place for Bluesky or Mastodon secrets.
Open /admin/Social
Social media hub
Short-form posts for Bluesky and Mastodon: enqueue on the site, publish via GitHub Actions, then review engagement on Stats. Sign-in required (same vault as Admin). No API tokens live on this page.
-
1
Queue
Schedule a post (text, networks, publish time) from the admin publisher. Items land as JSON under the public queue path on
main. -
2
Actions publish
GitHub Actions runs on a schedule (and on demand), picks up due queue items, posts to Bluesky / Mastodon, then archives the result. Credentials stay in Actions secrets only.
-
3
Metrics
A daily metrics workflow writes engagement data; the Stats page Social panel loads it for followers and recent posts.
This hub and Stats require the same sign-in as Admin (username, password, and authenticator). Blog publishing and social enqueue share that vault; network API tokens are never stored in the browser. This is a client-side lock only — not server-side privacy.
Stats · Social
Sign-in required
Follower counts and recent posts from the social-data branch, shown in the
Social panel on the stats dashboard.
GitHub Actions
Workflows in the repo
Social publish (due queue items), Social metrics (engagement), and Social tests. Configure secrets under the repo Settings → Actions; nothing secret is listed here.
View Actions runs