Skip to content

Conversation

@CrossDark
Copy link
Contributor

@CrossDark CrossDark commented Nov 12, 2025

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 Nov 12, 2025
@elegaanz elegaanz self-assigned this Nov 13, 2025
@elegaanz
Copy link
Member

Can you please fix the CI errors? Also, I would prefer if you could wait until you have a somewhat working version of your packages before submitting PRs, I feel like you opened and closed a lot of them without any getting merged. I can offer some guidance if you have questions.

@CrossDark
Copy link
Contributor Author

I’ve updated my branch, but it can’t be synced

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