Generate and render Atom feed
Open
area:content
enhancement
proposal
- Dominant language
- Elixir
- Stars
- 1.3k
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
Notes:
- Templates should be rendered by calling the `render_template` lifecycle since apps may apply transformations before rendering it.
- Cache
- Limit (default and/or configurable)
Ref:
* https://www.rfc-editor.org/rfc/rfc4287
* https://validator.w3.org/feed/docs/atom.html
Contributor guide
Research direction
Start by locating the feed-generation and template-rendering entry points in the Beacon codebase, then read the `render_template` lifecycle notes in this issue. Use RFC 4287 and the W3C Atom validator to define the output requirements. Done means a valid Atom feed with caching and a documented default or configurable item limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend, content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100