feat: publish Atom feed of site updates - #22
Closed
xnoto wants to merge 3 commits into
Closed
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Publish a hand-maintained Atom feed of site updates at
makeitwork.cloud/feed.xmland 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
Validation
ciruns the pre-commit hooks (end-of-file, trailing-whitespace, gitleaks, actionlint, prettier) andnode --check makeitwork.cloud/sw.js.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.xmlto the public S3 bucket and purges the Cloudflare zone cache; the feed is then served athttps://makeitwork.cloud/feed.xmlalongsidesitemap.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--deletesync removesfeed.xmlfrom the bucket.Safety and secrets
This change was produced by the
makeitworkOpenCode agent at the owner's direction.