Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

RSS feed rendering issue in Slack

Open
#693 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Domain
content

Research direction

Start with the generated https://clojure.org/feed.xml and the JBake templates mentioned in the issue; check .gitignore for how generated files are handled. Compare its description structure with the AWS and Rust feeds, then verify the revised feed in Slack. Done means the blog content renders without truncated HTML tags.

Written by the indexing model from the issue text.

Description

backlog

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.

Screenshot 2024-06-03 at 10 56 34

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.

/feed add https://clojure.org/feed.xml
/feed add https://aws.amazon.com/blogs/aws/feed/

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 content:encoded element can be used in conjunction with the description element to provide an item's full content along with a shorter summary. Under this approach, the complete text of the item is presented in content:encoded and the summary in description.
https://www.rssboard.org/rss-profile#namespace-elements-content-encoded

Dominant language
HTML
Stars
259
Forks
275
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from clojure/clojure-site

All issues in clojure/clojure-site

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.