Add RSS feed to blog section

[sphinxc0re]

No description provided.

[happenslol]

Hey, thanks for the issue! I'm not sure how many people are using RSS feeds nowadays, so I didn't even think about this.

It should be rather easy to add an RSS feed using this plugin, we could even add tutorials or similar things that we might post in the future to that feed. I'll help if anyone wants to tackle this!

[sphinxc0re]

So, I actually tried implementing this and couldn't even get the simple example to work. Also I saw that over a thousand packages in this repo have security vulnerabilities so I ran npm audit fix and it fixed them all. But then the repo stopped building and even updating dependencies didn't solve this.

Because of all these issues I would like to know what the rationale was for choosing Gatsby over hugo, zola or jenkins (..or any other ssg).

[happenslol]

Heya,
I haven't had time to look at this in quite a while since I'm pretty busy at my new job. Just took 5 minutes to see what the problem is here:
Basically, some central dependency had an issue, which then caused all of its dependants to be marked insecure. In reality, it was probably a single package that had the problem.
After running npm audit fix, you'll have to update gatsby-plugin-manifest manually. After that you'll probably have conflicting graphql versions (as both the prismic plugin and gatsby itself have it listed as a peer dependency), but deleting the lockfile and the modules folder and doing a fresh install got me up and running again.

To be honest, "all of these issues" are really not as much of an issue and are very common with any javscript framework - Javascript projects need frequent dependency updates or they will gather vulnerabilities over time, as they are discovered in older package versions.
In our case, we don't really have to worry as much - since we're shipping static files and aren't talking to any backend, we're not in any danger of shipping active vulnerabilities.

And there were actually many reasons for choosing Gatsby! First and foremost, I chose it because of its speed, flexbility in development and the way it integrates with our content backend (prismic). Additionally, hugo, zola and jenkins are not as good with static pages that don't consist of mainly blog posts/repeatable pages. I've talked to the zola dev before about finding a better solution for this, but he was focused on i18n and so I switched at that time.

Do you have any other concerns regarding gatsby? I'm always open for criticism on my/our choice of framework, other than dependency update issues which can be resolved in a few minutes ;-)

[sphinxc0re]

At our agency, we had a lot of problems with Gatsby, so I might be a little biased here ;)

Admittedly, I've never heard of Prismic before and didn't know what it does or can do.

I would actually be totally fine if we could just work out the problems and activate the rss feed on the blog.

[clarfonthey]

Hey, I also use RSS and can't follow the blog. :(

RSS is still the # 1 decentralised means of following these sorts of sites, and I'd rather read a feed than follow on Twitter and get a bunch of other info alongside the actual posts.