Skip to content

vibrant-color:0.1.0 #2426

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 9 commits into from
May 22, 2025
Merged

vibrant-color:0.1.0 #2426

merged 9 commits into from
May 22, 2025

Conversation

SHAfoin
Copy link
Contributor

@SHAfoin SHAfoin commented May 20, 2025

I am submitting

  • a new package
  • an update for a package

Description: A new template to create report with Typst, using vibrant colors and modern style. Used initially by myself for my student report, it became popular in my school for its modern design, multiple themes colors, ease of use and for using Typst which was not so much known. I would now like to share it with the Typst community as it could be useful for others, and I did not found any template like this.

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.

@SHAfoin SHAfoin closed this May 20, 2025
@SHAfoin SHAfoin reopened this May 20, 2025
@typst-package-check typst-package-check bot changed the title New template : Vibrant Color vibrant-color:0.1.0 May 20, 2025
@typst-package-check typst-package-check bot added the new A new package submission. label May 20, 2025
Copy link
Member

@elegaanz elegaanz left a comment

Choose a reason for hiding this comment

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

Nice template! On top of the errors and warnings reported by CI, I saw an import that needs to be updated. Once all that is fixed, it should be ready to be published.

@SHAfoin
Copy link
Contributor Author

SHAfoin commented May 21, 2025

Thank you for your help ! I thought it was because the package wasn't published that it could not use #import "@preview/vibrant-color-theme:0.1.0": * but it was just a typo haha, I'll correct it !

@elegaanz
Copy link
Member

You're welcome :) There is still the same issue in the template file, and the two other warnings that it would be nice to fix (at least the one about kebab-case, the one about the image size might be a bit harder to solve without loosing too much quality, so feel free to skip it if you don't find a good solution).

@SHAfoin
Copy link
Contributor Author

SHAfoin commented May 21, 2025

It would be better to have no warning so I'll deal with it, but I do not understand the critical error ; do I need to import it in another way ?
Thanks for your help

@elegaanz
Copy link
Member

It's just that the name in the import is wrong, like it was in your README, removing the -template at the end should fix it.

@SHAfoin
Copy link
Contributor Author

SHAfoin commented May 21, 2025

Oh I only modified it in the README, not the .typ lmao
I fixed it and every other errors + compressed the images, I think everything is okay now

@elegaanz
Copy link
Member

Yes, thank you!

@elegaanz elegaanz merged commit e775fad into typst:main May 22, 2025
2 checks passed
@SHAfoin SHAfoin deleted the vibrant-color branch May 22, 2025 08:23
John-Toohey pushed a commit to John-Toohey/typst-packages that referenced this pull request May 24, 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