Repository navigation
One class per site-wide OPML file - #50
Merged
Merged
Conversation
pfefferle
force-pushed
the
refactor/site-files
branch
from
October 15, 2026 11:55
034b244 to
1dc4f57
Compare
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.
Opmlwas the page OPML, the discovery links, the feed namespace and every file of the whole site in one class. This gives each of those files a class of its own:Directory,RecommendationsandFollowing. The templates share their head now.Each of them answers to its own value of
?opmlon any URL:?opml=directory,?opml=recommendationsand?opml=following. That also works with plain permalinks, where the well-known paths do not.Opml::FILESmaps the values to the classes, andrender()just asks the right class toserve().The directory and the recommendations are the same file for now,
Recommendationsjust callsDirectory. With a class each they can go separate ways later.The well-known rule of the recommendations points to
opml=recommendationsnow. The stored rule no longer matches, so the check for stale rules flushes once after the update. Until then the old rule lands onopml=directory, which is the same file.Opml::directory()andOpml::DIRECTORYare gone, nothing outside the plugin uses them as far as I can tell.