chore: rewire blog and RSS feed for 11ty#319
Conversation
✅ Deploy Preview for compilerla ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| <path d="M160 213h-34a82 82 0 0 0 -82 -82v-34a116 116 0 0 1 116 116z" fill="#FFF"/> | ||
| <path d="M184 213A140 140 0 0 0 44 73 V 38a175 175 0 0 1 175 175z" fill="#FFF"/> | ||
| </svg> | ||
| Web Feed Preview |
There was a problem hiding this comment.
Why isn't Compiler's Blog the <h1> title element here?
I note that is the value of the <title> element, and I reckon they should align?
There was a problem hiding this comment.
i'm glad you zeroed in on this. turns out the subtitle wasn't rendering either.
fa396ec looks/feels like an improvement to me. let me know what y'all think.
| </h1> | ||
| <h2><xsl:value-of select="atom:feed/atom:title"/></h2> | ||
| <p><xsl:value-of select="atom:feed/atom:description"/></p> | ||
| <p>This preview only shows titles, but the actual feed contains the full content.</p> |
There was a problem hiding this comment.
#175 was the original issue (submitted by an outside reader) that prompted us to publish a feed.
In the same issue, the requestor made the point that publishing the full post body in the feed was more desirable, as it lets folks read the post in their preferred reader app/interface. I don't see a strong reason to change this behavior.
There was a problem hiding this comment.
Ah maybe this is only the case in this XSLT transformation of the feed, displayed in browsers?
It seems like the feed as seen by feed readers still contains the full post body, as shown in your validator link: https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fdeploy-preview-319--compilerla.netlify.app%2Fblog%2Ffeed.xml
There was a problem hiding this comment.
unless i've lost the plot, the feed.xml still includes the entire body of each blog post and the .xsl file is just an additional skin to make it easier to skim the list of posts.
that said, i'll make a note to fire up an actual RSS reader to be absolutely certain this is the case before we merge #302
There was a problem hiding this comment.
I'm pretty sure I'm the one that lost the plot. Got confused between the actual feed and the XSLT styled version of the feed that shows up in the browser. Have to say, I've always hated XSLT 😅
This is the kind of change that I'd rather was either documented in a ticket and/or discussed ahead of implementation. It's a fairly big addition / change from where we were before. I think we can merge it but here are some additional thoughts it would have been worth discussing ahead of time:
- The content that shows up on this page, links out to external sites that we have no affiliation with, etc.
- The design/branding of this page, differing from Compiler's website and blog as a whole
- Accessibility considerations
- Our (potential) need to maintain an XSLT stylesheet going forward
There was a problem hiding this comment.
i hear that. if anyone else has reservations about merging as-is i don't mind yanking the .xslt file here and looping back to discuss it independently.
There was a problem hiding this comment.
Good discussion here, and I'm ok with merging as-is 👍
There was a problem hiding this comment.
Yeah, on second thought, maybe let's pull it for now and revisit later.
lalver1
left a comment
lalver1
left a comment
There was a problem hiding this comment.
I've been reading along and learned a lot, thanks for the comments y'all.
I just have one minor question below, John:
5 participants
closes #293
closes #307
old: https://compiler.la/blog/2026/remix-case-study
new: https://deploy-preview-319--compilerla.netlify.app/blog/2026/remix-case-study/
old: https://compiler.la/blog
new: https://deploy-preview-319--compilerla.netlify.app/blog/ 1
✅ Valid Atom 1.0 feed
1 the team picture won't match and /blog/2026/content-localization will be missing until/unless we get in sync with
main.