-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RSS feed rendering issue in Slack #693
Comments
The Rust example is an Atom feed which is a bit different, but the AWS feed is RSS with entity encoded html and looks pretty much the same to me from a formatting perspective as the Clojure news feed (they also include the full post). How do those compare in the Slack reader? The FTL template for the current feed looks like this:
|
Thanks for looking into it! I created the #testing-rss-feed channel in Clojerians and added those feeds there to test how they look like. Feel free to add/remove feeds there using the Here's how they look like: |
Afaict, Slack displays a substring of One thing we could do is to substring <description>
<#escape x as x?xml>
- ${post.body}
+ ${post.body[0..*100]}
</#escape>
</description>
+
+ <content:encoded>
+ <#escape x as x?xml>
+ ${post.body}
+ </#escape>
+ </content:encoded> |
But Also, it doesn't solve the other problem of the extra whitespace between the lines. |
Slack's RSS feed reader does not render https://clojure.org/feed.xml properly. Some HTML tags are truncated. I think it would be a good idea to make sure the feed renders well in more places.
Reproduce
I have subscribed to the feed in https://clojurians.slack.com/archives/C076654T2LD/p1717409306089639 by seding this message in a Slack channel. Need to wait for the next blog post.
Solution
Here are some other RSS feeds that render well in Slack:
It might be worth experimenting with JBake templates (which are excluded via .gitignore). At the moment, the full blog body seems to be included in the
<description>
tag, but the feeds that render ok in Slack keep the description short and wrap the blog content inside a<content:encoded>
instead:The text was updated successfully, but these errors were encountered: