touying-endfield:0.1.1

[leostudiooo]

I am submitting

• a new package
• an update for a package

Changes:

• adapted custom mini-slides components for better design
• adjusted default init behavior so users can configure less

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.

[leostudiooo]

Do I need to use absolute package name for inside-package examples? My template entry uses package names, but i don't think it necessary for the examples to use package name.

[saecki]

Do I need to use absolute package name for inside-package examples? My template entry uses package names, but i don't think it necessary for the examples to use package name.

If you include examples on Typst universe they should use the package specification (@preview/...) so they work directly when copy-pasted.

This PR also seems to include the 0.1.0 version. Could you sync your fork, so it only contains the changes from 0.1.1?

[leostudiooo]

I‘m not sure if this sync operation is right (followed the doc gh repo sync --force and git pull --rebase 'd), please kindly double-check. I've modified the examples in the latest commit per the typst universe requirement.

[leostudiooo]

Sorry, I think I have just messed something up. Shall I close this pr and create a new one?

[saecki]

That might be the result of a mix of merge and rebase. You can try to update this one or create a new PR, it's up to you :)