Skip to content

ieee-vgtc:0.0.1#3726

Merged
elegaanz merged 17 commits intotypst:mainfrom
domoritz:ieee-vgtc-0.0.1
Jan 13, 2026
Merged

ieee-vgtc:0.0.1#3726
elegaanz merged 17 commits intotypst:mainfrom
domoritz:ieee-vgtc-0.0.1

Conversation

@domoritz
Copy link
Contributor

This is a new version of #3534 with a single package for both the journal and conference templates an a more generic name.

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.

@domoritz domoritz mentioned this pull request Dec 23, 2025
9 tasks
@typst-package-check typst-package-check bot added the new A new package submission. label Dec 23, 2025
Removed exclusion of conference template from typst.toml.
@elegaanz elegaanz self-assigned this Jan 5, 2026

<p align="center"><img src="thumbnail.png" width="500"/></p>

Live [preview of the PDF template](preview.pdf).
Copy link
Member

Choose a reason for hiding this comment

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

The linked PDF file doesn't exist. It's fine to commit it to this repository as you are referencing it in your README. You can also link to your own repository directly if the file is available there, but if you decide to do so, make sure to use a "pinned" URL (i.e one that includes a commit hash or git tag name in the URL, not a branch name).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sounds good. I wasn't sure what is okay to submit here vs what I should keep in my source repo. I suppose I should then add preview.pdf to exclude, right?

Copy link
Member

Choose a reason for hiding this comment

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

Yes, it's better to exclude the PDF. In case you haven't already read it, this section of our docs may help you to understand what files should be submitted here and what should be excluded.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for the pointer. I think I followed those rules.

Removed the section detailing the templates provided by the package.
@domoritz
Copy link
Contributor Author

Btw, did you see the email to [email protected] about the name for this package?

@elegaanz
Copy link
Member

Yes, I got the email, even if it was mentioning the previous PR and not this one. So keeping this name is fine.

I think you actually forgot to exclude the preview.pdf file, could you do that? After that, it should be good to merge.

@domoritz
Copy link
Contributor Author

I think you actually forgot to exclude the preview.pdf file, could you do that? After that, it should be good to merge.

Done in ieeevgtc/ieee-vgtc-typst@861a82a and synced here in 50abe88 (#3726).

@elegaanz
Copy link
Member

Thank you!

@elegaanz elegaanz merged commit 7cab697 into typst:main Jan 13, 2026
3 checks passed
@domoritz
Copy link
Contributor Author

Thank you for shepherding the pull request!

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