Ashwin Maroli

Hello @RobertGauld, thank you for leaving feedback on the work so far. > prefer the structure like.. This structure is to maintain backwards-compatibility with established post filename pattern. > I...

Considering this as a "Minor Enhancement" to be shipped with v4.4. Will backport to `4.3-stable` and `3.10-stable` if @mattr- and @parkr decides this needs to be backported.

@parkr, the exact situation here is kind of flaky. I couldn't find any mention of unbundling `json` gem from `ruby/ruby` GH repo. But, ever since Ruby 3.0 dropped, there are...

Will have this on hold till a consensus is reached over CI on Windows

@olleolleolle If you have the time, may I ask for a PR that migrates CI on Windows to GitHub Actions? (*May or may not get merged*)

`page.last_modified_at` isn't an attribute introduced by Jekyll (core). So I agree with @chmaynard's comment — *outside the scope of Jekyll core docs*.

Hello @miry, does this `source` build with `liquid-4.0.4` but without the `RUBYOPT="--enable=frozen-string-literal` flag?

Hello @Mathiyarasy, Thank you for reporting this issue. However, I do not see a solution at arm's length. `github-pages` is [constrained](https://pages.github.com/versions/) to use the legacy Sass library via older version...

The issue here is primarily conflicting executables with the same name. `jekyll-sass-converter` (JSC) v3.0 allowed installing _older_ versions of `sass-embedded` (v1.54 and above) while JSC-3.1 requires at least `sass-embedded-1.75`. So,...

Hello @elyahw, thank you for reporting this issue. This is a known issue with Liquid versions older than `liquid-5.5.0`. However, Jekyll does not appear to be *fully compatible* with Liquid...