Replace custom text-Nxl-Mxl utilities with Tailwind prefixes#619
Merged
Conversation
Contributor
|
I'm not familiar with Tailwind, but anything to simplify this repo is good in my books! |
LaurentRDC
approved these changes
Jul 13, 2026
Collaborator
Author
|
Thanks. I am still simplifying the templates. This is all a bit "clunky" to say the least. |
Swap each hand-kept text-Nxl-Mxl class in templates/content pages for standard text-* + responsive prefixes, adding leading-* where the old ramp's explicit line-height didn't match Tailwind's default, then drop the now-unused rules from main.css.
The comment/table was copy-pasted from events/tile.html but never got the tr/td content filled in; partnerships items have no date/location fields, so it was rendered as a meaningless empty <table>.
Neither templates/event.html nor templates/partnerships.html is referenced from site.hs or any $partial$ call; they're leftover drafts superseded by templates/events/page.html and templates/partnerships/page.html.
Drop the responsive leading-snug/leading-tight stepping and leading-relaxed on paragraphs; Tailwind's per-size line-heights are close enough that the explicit overrides were mostly redundant. Keep a single leading-tight on headings that render unbounded template content ($title$/$episode$/$category$), since those can wrap. Add explicit margin around the projects/list.html status labels, which had been relying on line-height as a spacing hack.
Collaborator
Author
|
I am merging this, since it does not contain any change of content. It does, however, change the CSS, so if you detect any glitches, let me know. (I couldn't find any). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the mentioned followup:
Swap each hand-kept text-Nxl-Mxl class in templates/content pages for standard text-* + responsive prefixes, adding leading-* where the old ramp's explicit line-height didn't match Tailwind's default, then drop the now-unused rules from main.css.
Also: