niram-css:0.2.0

[nandac]

I am submitting

• a new package
• an update for a package

Description:
Support different CSS color name conventions.

CSS color names appear in the wild in several forms — the spec uses concatenated lowercase (mediumvioletred), web tooling often uses camelCase or PascalCase (mediumVioletRed, MediumVioletRed), design tools and CLIs prefer kebab-case (medium-violet-red), and prose naturally reads as spaced Title Case (Medium Violet Red). Previously, niram-css only accepted the canonical lowercase form, forcing users to memorize or look up the exact spelling. Inputs are now normalized internally, so any common casing or separator (including snake_case and SCREAMING_SNAKE_CASE) resolves to the same color — letting authors write color names in whatever form reads most naturally in context.

Restructured and improved the manual and README to add more information about the package.

The initial release shipped with minimal documentation, which left common questions unanswered: why green in Typst differs from green in CSS, why the list contains 147 names but only 138 unique hex values, and where the names came from historically. The manual now covers usage examples across fills, strokes, underlines, and shapes; a side-by-side comparison of Typst's built-in palette against the CSS equivalents; the X11/CSS history behind the names; and a complete reference table. The README mirrors the introduction, so users land on the same framing whether they arrive from GitHub or the PDF.

I have read and followed the submission guidelines and, in particular, I

• selected a name that isn't the most obvious or canonical name for what the package does
• added a typst.toml file with all required keys
• added a README.md with documentation for my package
• have chosen a license and added a LICENSE file or linked one in my README.md
• tested my package locally on my system and it worked
• excluded PDFs or README images, if any, but not the LICENSE

• ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.