Skip to content

polycv:0.2.0 - #5825

Open
bbinet wants to merge 1 commit into
typst:mainfrom
bbinet:polycv-0.2.0
Open

bbinet wants to merge 1 commit into
typst:mainfrom
bbinet:polycv-0.2.0

Conversation

@bbinet

@bbinet bbinet commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

I am submitting

  • a new package
  • an update for a package

Description: polycv 0.2.0 - a data-driven two-column CV package for Typst.

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
  • 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.

@bbinet
bbinet deployed to Package Check September 11, 2026 13:49 — with GitHub Actions Active
@typst-package-check typst-package-check Bot added the update A package update. label Sep 11, 2026
@elegaanz elegaanz self-assigned this Sep 16, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

It looks like I didn't really made the remark during the previous review, but I'm a bit uncomfortable shipping a Makefile as part of the template: for web app users and more generally users who are not familiar with Make, this file will be just be confusing. I still understand that it can be useful for people who know how to use it. I think it would make sense to move it out of the template directory, and link to it from your README: this way people who need it can easily download it and add it to their project, but by default you don't get a file that you don't know how to use or can't run.

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