Atom syndication, pages, and archives for indexes and tag indexes #1677
Conversation
| @@ -557,7 +557,7 @@ INDEX_READ_MORE_LINK = ${INDEX_READ_MORE_LINK} | |||
| RSS_READ_MORE_LINK = ${RSS_READ_MORE_LINK} | |||
|
|
|||
| # Append a URL query to the RSS_READ_MORE_LINK and the //rss/item/link in | |||
| # RSS feeds. Minimum example for Piwik "pk_campaign=rss" and Google Analytics | |||
| # Atom and feeds. Minimum example for Piwik "pk_campaign=rss" and Google Analytics | |||
Kwpolska
May 3, 2015
Member
make it clear: Atom and RSS feeds.
make it clear: Atom and RSS feeds.
| <body> | ||
| <h1><xsl:value-of select="feed/title"/> (Atom feed)</h1> | ||
| <p>This is an Atom feed. To subscribe to it, copy its address and paste it when your feed reader asks for it. It will be updated periodically in your reader. New to feeds? <a href="https://duckduckgo.com/?q=how+to+get+started+with+rss+feeds" title="Search on the web to learn more">Learn more</a>.</p> | ||
| <p> |
Kwpolska
May 3, 2015
Member
The search query still says rss.
On a side note, could you make it possible to discourage people from using feeds for subpages (index-1 etc.)? I have absolutely no idea how this all works and if this is possible; maybe you could create two XSL files with different text for the two cases.
The search query still says rss.
On a side note, could you make it possible to discourage people from using feeds for subpages (index-1 etc.)? I have absolutely no idea how this all works and if this is possible; maybe you could create two XSL files with different text for the two cases.
da2x
May 3, 2015
Author
Contributor
Intentional. The results were better than when changing the query to Atom. You’d be hard-pressed to find something calling itself an RSS reader that didn’t support Atom anyways.
That is the job of <link rel="current"> inside the non-current feeds. Could display the current address itself. Would be a bit more complicated as current doesn’t contain current only self.
Intentional. The results were better than when changing the query to Atom. You’d be hard-pressed to find something calling itself an RSS reader that didn’t support Atom anyways.
That is the job of <link rel="current"> inside the non-current feeds. Could display the current address itself. Would be a bit more complicated as current doesn’t contain current only self.
Paginated current and archived feeds for indexes. New option GENERATE_ATOM is off by default.
Substitutions for RSS_LINKS_APPEND_QUERY for identifying the source feed address (feedRelUri) and the kind of feed (feedFormat).
| @@ -753,12 +757,21 @@ COMMENT_SYSTEM_ID = ${COMMENT_SYSTEM_ID} | |||
| # links to it. Set this to False to disable everything RSS-related. | |||
| # GENERATE_RSS = True | |||
|
|
|||
| # By default, Nikola does not generates Atom files for indexes and links to | |||
| # them. Generate Atom for tags by setting TAG_PAGES_ARE_INDEXES to True. | |||
| # Atom feeds are built based on INDEX_DISPLAY_POST_COUNT and not FEED_LENGHT | |||
Kwpolska
May 4, 2015
Member
LENGTH*
fixed
LENGTH*
fixed
| # Switch between plain-text summaries and full HTML content using the | ||
| # RSS_TEASER option. RSS_LINKS_APPEND_QUERY is also respected. Atom feeds | ||
| # are generated even for old indexes and have pagination link relations | ||
| # between each other. Old Atom feeds were no changes are marked as archived. |
Kwpolska
May 4, 2015
Member
with no changes*?
fixed
with no changes*?
fixed
| <meta charset="UTF-8"/> | ||
| <meta name="viewport" content="width=device-width"/> | ||
| <title><xsl:value-of select="feed/title"/> (Atom feed)</title> | ||
| <style><![CDATA[html{margin:0;pdding:0;}body{color:hsl(180,1%,31%);font-family:Helvetica,Arial,sans-serif;font-size:17px;line-height:1.4;margin:5%;max-width:35rem;padding:0;}input{min-width:20rem;margin-left:.2rem;padding-left:.2rem;padding-right:.2rem;}ol{list-style-type:disc;padding-left:1rem;}h2{font-size:22px;font-weight:inherit;}]]></style> |
Kwpolska
May 4, 2015
Member
padding*
(also broken in rss.xsl)
both fixed
padding*
(also broken in rss.xsl)
both fixed
|
Couldn’t we handle the tags without forcing tag indexes? |
Signed-off-by: Chris Warrick <kwpolska@gmail.com>
* Autodiscoverable feeds for archive and tag index pages * Generate paginated and properly archived feeds for archive indexes
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.
https://tools.ietf.org/html/rfc4287
plus extensions:
https://tools.ietf.org/html/rfc5005#section-3 (pagination)
https://tools.ietf.org/html/rfc5005#section-4 (archives)