itemplate:0.1.0

[hexiongwu1995]

I am submitting

• a new package
• an update for a package

This package restructures the default exported HTML file to provide a more complex structure for subsequent CSS styling and JS manipulation. CSS and JS resources are provided default from an npm package "@hexiongwu1995/itemplate" but can also be downloaded form this package's sub directory to ensure reliability and stability.

Unfortunatly, the iconfont files can only be accessed from the npm package mentioned above because typst does not support uploading to their repository.

I have read and followed the submission guidelines and, in particular, I

• selected itemplate that isn't the most obvious or canonical name for what the package does

  • Explanation: the name contains the word "template" which explains itself as a html template. The prefix "i" makes the name very short, easy to remember and sounds unique.

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

[hexiongwu1995]

I delibrately put all source files associated with this project, except for the iconfont files, in the assets directory to ensure this package always maintains a consistent appearance and functionality. And I think they are necessary and not redundant.

[elegaanz]

Thank you for this template :)

[elegaanz]

There is an extra space before the version number here.

[hexiongwu1995]

The extra space has been deleted.

[elegaanz]

Can you remove that file please? It is a compilation artifact and is not referenced anywhere.

[elegaanz]

This file too doesn't really belong here, it is more useful for you or other maintainers, so it should only live in your own repository. Can you remove it too, please?

[elegaanz]

Regarding assets management, you should either:

• Use unpkg all the time and remove the local copies of the files
• Use bundle export to re-export them along the HTML document, and stop relying on unpkg. You can keep using for font files, load them from another third-party, or add a parameter that lets users provide the font files themselves.

[hexiongwu1995]

I choose to use the unpkg method. All css and js files has been removed.

[hexiongwu1995]

@elegaanz I have made some changes, please check this package again.