planetperl VS Jekyll

planetperl has the code that drives Planet Perl (ok, actually, it contains the configuration for that site – most of the actual work is done by Perlanet – and see below for more about that)

title: Planet Perl description: There's More Than One Way To Aggregate It url: https://perl.theplanetarium.org/ author: name: Dave Cross email: [email protected] twitter: davorg entries: 75 entries_per_feed: 5 opml_file: docs/opml.xml page: file: docs/index.html template: index.tt feed: file: docs/atom.xml format: Atom google_ga: G-HD966GMRYP cutoff_duration: months: 1 feeds: - feed: https://www.perl.com/article/index.xml title: perl.com web: https://perl.com/ - feed: https://news.perlfoundation.org/atom.xml title: Perl Foundation News web: https://news.perlfoundation.org/

Previously, my workflows for these sites just needed a single job (called build) but now I added a deploy job which depended on build. For example, the workflow that builds Planet Perl now looks like this:

A little bit more hacking on Planet Perl. You can now filter the sources that you want to see (and those choices are remembered for the next time you visit the site). Thanks to Gabor for suggesting it.

If you'd like to suggest new feeds to add, then raise an issue or submit a pull request on the GitHub repo.

This blog is running on Hugo. It had previously been running on Jekyll. Both these SSGs ship with the ability to create excerpts from your markdown content in 1 line or thereabouts.

Jekyll

In future, if you want to move from Jekyll to something else, you just have to worry about that `_posts` and `_assets` folder. They may have different naming convention but you can just config-managed it or change it to your choice. This is why I suggested owning that two yourself.

You also may not worry about FrontMatter[3] (meta in the header) and its accompanying jazz by asking Jekyll to use the plugins `jekyll-optional-front-matter` and `jekyll-titles-from-headings`. These comes as part of the officially supported Jekyll plugins[4] by Github. That way, you are just writing a human-readable plain-text spiced up with Markdown and readable by almost every other Static Site Generator.

Now, play with the `_config.yml` that Jekyll generates for you from the theme above to define your post dates, navigation, and others. Jekyll is one of the OGs — the Gandalf of Static Site Generators. If you have a problem, someone somewhere has solved that.

Did I missed something? I was supposed to write a blog article for my website on this one and this comment will serve as my starting bullet points.

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

2. https://jekyllrb.com

3. https://frontmatter.codes/docs/markdown

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

"Using the Chirpy theme for Jekyll."

I would suggest looking into static site generators. Some popular examples, which are used myself are: - Hugo: https://gohugo.io/ - Jekyll: https://jekyllrb.com

In terms of GitHub stars, SSGs like Next.js, Hugo, Gatsby, Docusaurus, Nuxt.js, and Jekyll top the list. Some popular SSGs even host conferences and workshops, providing resources and networking opportunities for those looking to explore more advanced topics in depth.

I created my blog using Jekyll, a great open-source tool that can transform your markdown content into a simple, old-fashioned-but-trendy, static site. What are the advantages of this approach? The site is super-light, super-fast, super-secure and SEO-friendly. Of course, it’s not always the best solution, but for some use cases, like a simple personal blog, it’s really a good option.

Yes, it's Markdown and I use https://jekyllrb.com with the theme "jekyll-theme-hacker" to generate the site. I quite like how simple it is.