Skip to content

feat: publish Atom feed of site updates - #22

Closed
xnoto wants to merge 3 commits into
mainfrom
add-atom-feed
Closed

feat: publish Atom feed of site updates#22
xnoto wants to merge 3 commits into
mainfrom
add-atom-feed

Conversation

@xnoto

@xnoto xnoto commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Summary

Publish a hand-maintained Atom feed of site updates at makeitwork.cloud/feed.xml and advertise it from the portal <head> for feed-reader autodiscovery. The feed gives external consumers (PieFed instance feeds, feed readers, automation triggers) a structured way to follow site updates; the driving use case is populating a community on a third-party PieFed instance through its Feeds feature, with zero new cluster workloads. No linked issue.

Type of change

  • Bug fix
  • Feature / enhancement
  • Documentation
  • Infrastructure (OpenTofu root or module)
  • GitOps desired state (manifests, kustomize, charts, SOPS/KSOPS secrets)
  • Container image
  • CI / reusable workflow
  • Refactor / cleanup
  • Breaking change

Validation

  • Required pull-request checks pass: ci runs the pre-commit hooks (end-of-file, trailing-whitespace, gitleaks, actionlint, prettier) and node --check makeitwork.cloud/sw.js.
  • No generated or centrally distributed files are touched; all three files are hand-authored repository content.

Intentionally not validated here: live serving of /feed.xml (only happens after merge triggers the S3 deploy) and ingestion by the target PieFed instance (manual post-merge step performed in that instance's UI).

Impact and rollout

Self-contained static-content change. On merge, the deploy workflow syncs feed.xml to the public S3 bucket and purges the Cloudflare zone cache; the feed is then served at https://makeitwork.cloud/feed.xml alongside sitemap.xml. The portal gains one <link rel="alternate"> line; the README documents the feed and the permanent-id rule for entries. Follow-up outside this repository: add the feed URL in the target PieFed instance's Feeds UI. Rollback: revert the merge; the next deploy's --delete sync removes feed.xml from the bucket.

Safety and secrets

  • Contains no plaintext secrets, decrypted SOPS values, state files, kubeconfigs, tokens, or private endpoints — public static content; the feed carries site-level metadata only, no personal data beyond what the portal already publishes
  • No local OpenTofu init/plan/apply/destroy/import/state operations were run or claimed — not an OpenTofu repository
  • Breaking or irreversible effects are described above with rollback notes — additive file plus a one-line head addition

This change was produced by the makeitwork OpenCode agent at the owner's direction.

Hand-maintained Atom feed at makeitwork.cloud/feed.xml so feed readers and
PieFed instance feeds (fastfeedparser) can follow site updates. Seed entry
covers the portal itself; entry ids are permanent tag URIs.
@xnoto
xnoto requested a review from a team as a code owner September 2, 2026 17:34
@xnoto xnoto closed this Sep 2, 2026
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