strict-modern-uestc-thesis:2.0.0

[kong13661]

I am submitting

• a new package
• an update for a package

Description: This is the uestc thesis. Compared to the modern-uestc-thesis, this template implement the whole format in the the university word template.

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

[SchrodingerBlume]

Hi, spotted this while checking on my own PR, wanted to share a couple of things!

uestc-thesis might not pass review. Bare org abbreviations like uestc are reserved for official templates per the naming rules (https://github.com/typst/packages/blob/main/docs/manifest.md#naming-rules). A prefix should do the trick, or email hello@typst.app if it's official.

Also, just a thought, the comparison with other templates in the description might not be necessary? Your template stands on its own either way! 😊

Good luck with the submission!

[kong13661]

Hi, spotted this while checking on my own PR, wanted to share a couple of things!

uestc-thesis might not pass review. Bare org abbreviations like uestc are reserved for official templates per the naming rules (https://github.com/typst/packages/blob/main/docs/manifest.md#naming-rules). A prefix should do the trick, or email hello@typst.app if it's official.

Also, just a thought, the comparison with other templates in the description might not be necessary? Your template stands on its own either way! 😊

Good luck with the submission!

Thanks for your review. I have rename the template name to strict-modern-uestc-thesis. Besides, there is no comparison content in this template, such as typst.toml and README file. The purpose for the comparision is for review.

[saecki]

Thanks for this package!

[saecki]

This import should use a package specification (@preview/...)

[saecki]

Could you either use a perma-link or a link to a specific branch/tag of a version? That way the linked resources will always match the published version of the package.

[saecki]

Same here, could you please either use a perma-link or a link to a specific branch/tag?

[saecki]

This isn't quite the way template packages are supposed to be structured.
The package entrypoint should be outside of the template directory and the template/example should use the package using an @preview import. This ensures the user can upgrade by changing the version on the import of the package. when a newer version is released. See: https://github.com/typst/packages/blob/main/docs/manifest.md#templates

We currently don't accept packages that only provide template/example code without a reusable core.

If I understand correctly though. I think you just need to move the src directory out of the example directory and update the imports :)

[saecki]

Could you either also add an english description, or replace the description with an english one?

[saecki]

It is generally appreciated to have at least an introduction sentence in English, even if the target audience for the template is not native English speakers. This allows the broader Typst community to get an idea of what the package is about and make sure that it isn't of interest to them.

[saecki]

I'm not sure how well this will work on Typst Universe because there all h1 headings are removed and the package name is added as the h1 heading of the page. I don't know how to test this, so we can just give it a try and publish a new version if this fails somehow.
Just wanted to give you a heads up :)