Changelog/Rubyevents News

[hschne]

There's a lot of cool stuff happening in this repo, but it's a bit hard to follow. I'm subscribed to issues/PRs, and even so, I miss tons of new features/additions (almost didn't see #1051, which I think is awesome!).

Apart from making it easier for interested parties to see what's happening, there's also the promotional angle. I'm fairly certain many Rubyists are unaware of the platform's capabilities, and making ongoing activity more transparent could be a great way to change that.

For starters, I can think of several solutions.

1. Automatically create GH releases with an auto-generated changelog (maybe on a weekly basis?)
2. Create a changelog page/link on rubyevents.org to the changelog
3. Create a curated list of changes (think newsletter/post) to be publish on rubyevents.org
4. Highlight new features on the platform itself (think something like driver.js)

Opening this issue to gather some input.

@marcoroth @adrienpoly thoughts?

[adrienpoly]

I fully agree

3. Create a curated list of changes (think newsletter/post) to be publish on rubyevents.org

I recently pitched the idea to Marco for an announcement page. Some kind of simple blog system with various categories (new features, new content etc)

at first I though this could be built on top of ActionText/Lexxy but maybe I was just trying a find an excuse to test Lexxy somewhere. Static pages in markdown is probably better as anyone can open a PR to create/review new content

Edit : and we already have some page rendered as markdown, it could be cool to add some embeds so that we could display in a post a talk, a collection of talks, an event by just addition some king of slug

[hschne]

Some kind of simple blog system with various categories (new features, new content etc)

Since y'all are using Avo already should be simple to get something like that up pretty quickly 🤔

IMO 3. & 4. are less of a technical challenge, but it's tricky because that kind of stuff requires constant maintenance - someone needs to write that content at least semi-regularly after all. Just something to keep in mind.

[adrienpoly]

I have been thinking more about this and for the announcement pages I think we should keep it as markdown content that gets updated with regular PR. This way anyone can contribute to this not just the admins

I really like the implementation @rossta did for https://github.com/joyofrails/joyofrails.com. I think we can probably take good part of it