jekyll-feed VS cloudcannon-jekyll

XML feeds are often generated by templating, rather than actual XML serialisation. The official Jekyll Feed plugin has this: https://github.com/jekyll/jekyll-feed/blob/master/lib/jekyll...

JSON is much more easily generated by a valid generator, and less likely to face serialisation issues.

Awesome. I was able to get this going easily enough on my jekyll-created site that uses the jekyll-feeds plugin. You just have to name the template right and it just works.

https://github.com/jekyll/jekyll-feed/#custom-styling

Disable Jekyll-feed plugin from _config.yml

It looks like this [1] plugin [2] is supported in jekyll / GitHub pages [3].

So, it seems like adding RSS / Atom feeds on a jekyll or GitHub pages site is pretty straightforward.

1. https://github.com/jekyll/jekyll-feed

2. https://docs.github.com/en/pages/setting-up-a-github-pages-s...

3. https://pages.github.com/versions/

Nice site! Another fellow note-taker inspired by Gilles Castel I see ;) Would you be willing to add an RSS feed to your site so people can follow it and get updates? It's been a while since I used jekyll but I think you just need to add jekyll-feed to the Gemfile and config.yml. See here

There is again an easy way out with the jekyll-feed plugin. Add the plugin, do a bundle install and the feed should start appearing at /feed.xml.

I was afraid of that. I was starting to think that how my Atom feed is created is not properly formed XML. I'm using this to build the feed, https://github.com/jekyll/jekyll-feed/blob/master/lib/jekyll-feed/feed.xml. See line number 66 for the content I'm talking about ({{ post.content | strip | xml_escape }}). Maybe I just can't do what I'm trying to accomplish using only XSLT. I just wanted to have the option for the user of having the summary or the full on content with HTML markup and all. BTW, the file I referenced is written with Liquid Template Language.

I have tried using the provided theme like Minima but, I just don’t like it after all. That’s why I think it’s better to create my own. I tried to create the simplest design as long as it is easy to be read. I used Coolors, Google Font, Rogue, Jekyll Paginate, Jekyll Feed, and write a bit of Ruby, CSS, and JS for creating the theme itself. I didn’t think creating this simple blog costs me 2 Saturdays, even though it only consists of as many as 3 pages.

For Jekyll sites, we created a custom Jekyll plugin. To make your site work with CloudCannon, you import the plugin as you would any other, and it runs at the end of your build step, extending the vanilla Jekyll process. Using a plugin has the advantage of using built-in Jekyll behavior to generate the correct data — ensuring that the plugin is working with the same information as Jekyll itself.