Use RSS to update the weekly publication updates (or any method to prevent commits for updates every week)

[diagramatics]

I guess we're not going to clutter the commit history with commits for updating the weekly publications.

I would suggest using RSS. Here's io.js Medium RSS, for example. We can parse it to JSON and use it to get the latest post every time the website loads.

Hopefully the translation teams are using Medium or hosting them on GitHub. As long as they can give an RSS link to the publications this should go smoothly. iojs_id is using Medium, FYI.

[subfuzion]

👍 I think this is a great idea. I don't know if this solution for parsing the RSS feed is the best one, but it seems straightforward enough. The weekly update posts are part of this feed.

[snostorm]

I'd rather something like this happen server-side. Not that Medium specifically needs a search engine bump, it still helps the search engines to see the cross link and our homepage commonly updated (even if just a minor way.)

With https://github.com/iojs/website/blob/master/source/templates/home.html now in place (the old PR was against the i18n that feeds it) we should be able to modify this automatically, per-i18n that wants it. But, also, maybe we want to leave that space as a bit of a "free space" for i18n groups to post whatever recent updates/links they see as the most relevant and allow some copy change flexibility week-by-week?

Edited: the file link above (home, not main.)

[diagramatics]

Well, one (potentially awful) solution could be having a separate json file on each localization team's repo that controls this, and the website can get the values. Not really a solution since it moves the commits to each l10n repo, but it fits your requirements of making it flexible to change.

[snostorm]

The i18n folders already support what I've described, https://github.com/iojs/website/blob/master/source/templates/home.html uses a news_link which can be set per i18n. For example, the French localization at https://iojs.org/fr/index.html is using alternative messaging to point at the French Medium page and Twitter. Via https://github.com/iojs/website/blob/master/content/fr/template.json#L24

[diagramatics]

Ah, I misunderstood that completely.

The drawback of this would be lots of commits coming from each l10n team if they followed a weekly update post schedule, hence why I suggested RSS (I should've made a better title). If we're planning to trim these down, using RSS or referencing an external json file is what I could come up with.

[fhemberger]

This has already been taken care of on new.nodejs.org (using the local blog instead of Medium). I don't think we're going to invest the time to build that feature for iojs.org as well.