Skip to content

Conversation

virgiling
Copy link
Contributor

I am submitting

  • a new package
  • an update for a package

Description: Explain what the package does and why it's useful.

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.

@typst-package-check typst-package-check bot added the new A new package submission. label Sep 14, 2025
@saecki saecki self-assigned this Sep 16, 2025
Copy link
Member

@saecki saecki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this package! I've some comments regarding the name and an outdated version of codly. If you don't strongly prefer snake case, could you also fix the snake-case warnings from the package check?

@virgiling
Copy link
Contributor Author

Thanks for reviewing! I will update and modify this package as soon as possible.

@typst-package-check typst-package-check bot changed the title nenu-thesis:0.1.0 modern-nenu-thesis:0.1.0 Sep 16, 2025
@saecki
Copy link
Member

saecki commented Sep 18, 2025

Thanks!

@saecki saecki merged commit 4c2ea1f into typst:main Sep 18, 2025
2 of 3 checks passed
GIBZ-GIPE pushed a commit to gibz-informatik/typst-packages that referenced this pull request Sep 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new A new package submission.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants