jekyll-sqlite VS Jekyll

I’ve been working on a Jekyll SQLite plugin: https://github.com/captn3m0/jekyll-sqlite.

Jekyll let’s you use CSV/YAML/JSON files as data source, but they’re unwieldy since the schema is fixed.

The plugin is meant to let you reshape your data before you use it within Jekyll. You get complete flexibility of SQLite, to let you join tables, use indexes etc.

What I can’t figure out is how to best do “dynamic” queries, say a query that needs to show the number of reviews on the restaurant page (restaurants is the table). Each of these page will need to run a dynamic query with the page.id variable.

SQLite Injection isn’t a big issue, since this is all trusted input. But I’d like something better than just Templating queries using liquid.

I’m doing some parameterized queries on the global level (see README). Need to find a nice way to do them locally.

Maybe just putting them in metadata would be a good way?

After writing your posts in Markdown you can then display them however you'd like on your site through the built in Postwave Ruby client. This is where Postwave differs from static blog engines like Jekyll or Hugo which take the Markdown posts and generate a site for you.

Jekyll Official Website

But that's not the case. The blog is a simple static generated website using Jekyll, it is built and served through GitHub Pages. With that in mind it makes more sense to use tools and leverage tool calling.

And apparently it's front matter, not frontmatter?

Jekyll is one of the oldest and most established static site generators. It’s tightly integrated with GitHub Pages, making deployment super easy.

I wanted to automate this boring and repetitive workflow: my idea is that every time a YouTube video is published on my channel I want to have an associated post on my personal Jekyll blog.

The static site generator (SSG) landscape is crowded with feature-rich but increasingly complex solutions. As I looked at and used tools like lume, 11ty, lektor, or jekyll, I found myself drowning in configuration options, plugins, and middleware. What started as a simple desire to convert Markdown content into HTML had evolved into learning complex frameworks with steep learning curves.

Jekyll

If you don't want to use Jekyll as your static site generator for GitHub Pages and you want to have a custom domain for your GitHub Pages. This post is for you!