guided-resume-starter-cgc:2.0.0

[Spelkington]

I am submitting

• a new package
• an update for a package

---

Description: Explain what the package does and why it's useful.

After porting a previous template over to Typst, I was sent the recommendation to add it to Typst Universe. The original has now been proofread and typos appropriately swept away — after an additional proofread and local test on my end, this appears to be ready to go!

This is a port of a previous LaTeX package used by undergraduates for creating new resumes. On top of a standard styling, it also includes a set of best practices on how to write good content for a resume, such as:

• Structuring concise bullet points
• Formatting non-standard experience as an addition to work experience
• Methods for tuning resumes to particular job entries

Please let me know if there are any necessary additions needed. Thanks!

---

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.

[elegaanz]

Typst packages generally use kebab-case for naming functions and their arguments. But this is not a hard requirement, and you can decide to leave this as is if you prefer.

Suggested change

	#let hide(shouldHide, content) = {
	#let hide(should-hide, content) = {

[Spelkington]

This should be fixed in 49d62cd!

[elegaanz]

Unless you expect people to edit the contents of these functions, I think this file should be outside of the template/ folder (either directly in the root of the package, or in a dedicated sub-folder). As it is done now, this template file would be duplicated in every new project initialized from this template.

[Spelkington]

This project is a bit more "to each their own" than something like IEEE-compliant formatting, so the hope was to include the template file directly to more easily allow users to tweak it to their comfort. However, I'd imagine that Typst is looking to encourage adoption for the packaging system.

As a comfortable compromise, I've:

• kept the local copy of the template in the repository,
• switched the #import to the package system copy by default, and
• provided a brief instruction for users to use the local copy to tweak the editing if they'd like.

I've also added additional comments to the template file itself to make it a bit friendlier to power users who do want to tinker around with the template directly.

Hopefully this is a comfortable in-between!

[elegaanz]

It is, thank you :)