You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nodejs-news-feeder is a "poc" to see if an internal infomation feed to the node project would be useful. For me it would.
But the problem is that it isn't highlighted enough. So what I propose is to have a page that contains:
a header with title, description + link to the rss feed
(we can start from the component used for the blog)
a small body of text explaining what it is and why ...
and a component that lists the latest news, a bit like calendar events
From a code point of view, we'll need to implement the feed generation code in next-data and add the feed, noting that this time we can't put it under the i18n url because the feed can't be translated as it's based on GitHub issue comments.
The text was updated successfully, but these errors were encountered:
My initial thoughts are that this is interesting...but its flooded with GitHub release notifications. Perhaps that's useful, but I don't understand if that will drown out other info.
If there's high enough volume (say at least a handful of items per day), it might be worth rendering in a tightly packed "river" style format as opposed to something more akin to a blog, as it'll make it easier to skim. For example: https://www.techmeme.com/river
My initial thoughts are that this is interesting...but its flooded with GitHub release notifications. Perhaps that's useful, but I don't understand if that will drown out other info.
I may have a solution: split this ‘nodejs-news-feeder’ into two feeds, one for hand-written news and one for releases.
nodejs-news-feeder is a "poc" to see if an internal infomation feed to the node project would be useful. For me it would.
But the problem is that it isn't highlighted enough. So what I propose is to have a page that contains:
(we can start from the component used for the blog)
From a code point of view, we'll need to implement the feed generation code in
next-data
and add the feed, noting that this time we can't put it under the i18n url because the feed can't be translated as it's based on GitHub issue comments.The text was updated successfully, but these errors were encountered: