Skip to content

Conversation

@TomPlanche
Copy link
Contributor

I am submitting

  • a new package
  • an update for a package

Description

This is version 1.5.0 of the clean-cnam-template package, introducing enhanced font customization capabilities.

What's New in 1.5.0

Breaking Changes

  • Font parameters now use objects: All font parameters (default-font, body-font, title-font, code-font) now accept objects with name and weight properties instead of strings
    • Font object structure: (name: "Font Name", weight: 400)
    • weight can be an integer (100-900) or string ("regular", "bold", etc.)
    • Migration path: Change default-font: "Font Name" to default-font: (name: "Font Name", weight: 400)

New Features

  • Advanced font customization: New optional body-font and title-font parameters in clean-cnam-template()
    • Both default to default-font when not specified
    • Allows independent font selection for body text and titles/headings
    • Each can specify different font families and weights
    • Enables fine-grained typography control across different document sections

Why This Update is Useful

This update significantly improves typography flexibility by:

  1. Allowing users to specify font weights directly in configuration
  2. Enabling different fonts for body text vs. titles/headings
  3. Providing a hierarchical font system with sensible defaults
  4. Maintaining backwards compatibility through the default-font fallback mechanism

All changes have been tested and documented in the README.md and CHANGELOG.md files.

@typst-package-check typst-package-check bot added the update A package update. label Dec 23, 2025
@saecki saecki self-assigned this Jan 5, 2026
@saecki
Copy link
Member

saecki commented Jan 6, 2026

Thanks for the update!

@saecki saecki merged commit a618231 into typst:main Jan 6, 2026
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

update A package update.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants