Number of posts at once
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 944
- Forks
- 673
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 9
Description
Hi,
recently we've had several posts (10) at one single day, so much that they even flooded the front page of ruby-lang.org.
This causes also quite a lot of translation work, especially given that the contents of the Ruby version release posts are mostly equal and much is copied around for no use. That's also error-prone. I want to suggest, therefore, that at least all posts of a Ruby releases that occur on the same day in the future are only made as one single post describing all versions, rather than one post per Ruby version, unless it's really something significant (like our Christmas release new versions that generally start a new series).
I'm not so sure about the security posts. It may be better if they stay separate (one post per vulnerability instead of one post for all vulnerabilities of a day), but I'm not strong on this.
Greetings
Marvin
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review how Ruby release and security posts are currently organized on the site, then determine whether same-day releases should be combined while security posts remain separate. Done means an agreed publishing approach is implemented consistently for future posts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jekyll, ruby
- Domain
- content, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100