Upvoting @arknave ’s suggestion . Doesn’t look like it has been revisited in a number of years. With v1.1 in development, is opportunity calling?
WTH, I forked the spec. I’ll take a stab at it and open a PR. Any open PRs? No, but quite a few stale ones. Really stale ones.
Some PRs do get landed, so don’t lose hope!
-Fred
1 Like
For your convenience… an example of what this looks like.
PR 1580 was merged this morning by @dgeb ! Thanks Dan for the feedback and consideration. I didn’t see the CSS3 counters leaking while running the local bundle. I was just looking at the spec pages and didn’t see “the forest for the trees.” Hopefully, the community benefits from the new numbering scheme. I know my own use and internal discussions will!
json-api:gh-pages
← timothystone:gh-pages
opened 01:40AM - 31 Aug 21 UTC
Address oversight of specification numbering scope issue in #1574.
The Liqui… d template now applies a CSS class to the body element. The Sass
was updated to scope the changes to the class `.spec_page`, supporting
both 1.0 and 1.1. Confirmed the numbering does not appear on other pages
outside the scoped class.
From the original PR:
Citing the specification can be cumbersome. Following RFC numbering
formats, the specification is numbered following ISO 2145 at each HEADER
element, e.g., `h1`, `h2`, &tc. The numbers are CSS "generated" content
and provide support for the additive focus of the specification.
The paragraph glyph is repositioned absolutely, relative to the header.
The `_config.yml` is updated to support building. bundle otherwise
failed on Ruby 2.7.x. Updated the exclusions file for IntelliJ.
Regarding the `_config.yml` change, I followed the README instructions and
found that the site would not build with Ruby 2.3 installed on the Mac.
I upgraded to Ruby 2.7 via homebrew—required as the Jekyll markdown gem
would not compile—and encountered the same problem. Some research, i.e.,
SO-fu, found numerous posts regarding the vendor gem path with regards to
Jekyll test files.
Adding this line corrected the problem. The move to Ruby 2.7 appears to
have generated updates to the map file.
1 Like
dgeb
August 31, 2021, 4:15pm
7
Thanks for all your work on this @timothy.stone !
1 Like