Skip to content

bypst:0.2.0#4529

Merged
elegaanz merged 6 commits intotypst:mainfrom
jemus42:bypst-0.2.0
Apr 13, 2026
Merged

bypst:0.2.0#4529
elegaanz merged 6 commits intotypst:mainfrom
jemus42:bypst-0.2.0

Conversation

@jemus42
Copy link
Copy Markdown
Contributor

@jemus42 jemus42 commented Apr 7, 2026

I am submitting

  • a new package
  • an update for a package

Description: This is a template for an institutional presentation style built on top of touying. In principle it's only useful for members of the institute, but having it publicly available should help others looking for inspiration when porting their own institutional themes.

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.

@jemus42 jemus42 temporarily deployed to Package Check April 7, 2026 15:07 — with GitHub Actions Inactive
@typst-package-check typst-package-check bot added the new A new package submission. label Apr 7, 2026
@jemus42 jemus42 temporarily deployed to Package Check April 7, 2026 15:16 — with GitHub Actions Inactive
@jemus42 jemus42 temporarily deployed to Package Check April 7, 2026 15:19 — with GitHub Actions Inactive
@elegaanz elegaanz self-assigned this Apr 8, 2026
@jemus42 jemus42 temporarily deployed to Package Check April 8, 2026 18:01 — with GitHub Actions Inactive
@jemus42 jemus42 temporarily deployed to Package Check April 9, 2026 09:35 — with GitHub Actions Inactive
Copy link
Copy Markdown
Member

@elegaanz elegaanz left a comment

Choose a reason for hiding this comment

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

Thank you for this package. I have left some small remarks, but overall it looks good :)

Comment thread packages/preview/bypst/0.2.0/README.md Outdated
## Quick Start

```typst
#import "@local/bypst:0.2.0": *
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Can you show how to use the @preview import here? It should be the default way to import packages.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Done!

)
```

## Installation
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Similar remark regarding this section: it should be made clear that this is an alternative installation method, and that the preferred way is to just use a @preview/ import.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I clarified this now and differentiate between using the package and local development/installation.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do you have the rights to distribute this logo? If so, can you please specify that it is not under the same license as the rest of the package and under which terms it can be used, for example at the end of your README?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Hmm i am not sure about the licensing, I think the easiest approach might be a "bring your own logo" setup with a global theme parameter and users point it to a file path, with the package itself just shipping a placeholder image? I assume then I'd have to update the thumbnail as well 😅

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I tried it like this, not optimal but I guess it.. works?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

A lot of other packages are doing that, it's a bit more effort for the user but it works fine in practice. If in the future you learn that you can actually distribute it, you can always publish a new version of the template :)

@jemus42 jemus42 temporarily deployed to Package Check April 9, 2026 17:34 — with GitHub Actions Inactive
@elegaanz
Copy link
Copy Markdown
Member

Thank you!

@elegaanz elegaanz merged commit e92617b into typst:main Apr 13, 2026
3 checks passed
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