New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add science-posters 0.3.0 template #627
base: main
Are you sure you want to change the base?
Conversation
Hi, and thanks for opening a new PR. There were a few points that were discussed in the previous one that would still need to be resolved:
|
Thanks for the immediate feedback. I am not quite sure how to handle this situation. On the one hand, my package allows for deep customization of boxes which are used to build up the poster. On the other hand, I can see that the overall contributed functionality is not as big as that of other packages which would more point towards a template rather than a plain package. Please let me know your feedback. I can also come up with some mock-examples to show what I am getting at if desired. |
92aab43
to
d06d87c
Compare
Hey Jonas, The naming rule is less about avoiding collisions with the standard library (and thus anticipating it, we would not want to ask that of our package authors 😅) but about no package advertising itself as THE package for something (like scientific posters) with its name. For example, we asked the packages You can totally publish template packages that depend on this package and you are free to submit them in one or multiple PRs, as convenient. So if this is the tools package it could have a name like By the way, I enjoyed your blog post about creating posters with Typst! Can we quote it on our site? |
Hi, |
I am submitting
Description:
This package/template allows users to create scientific posters with minimal additional syntax.
It also comes with extensive documentation.
This PR was previously closed due to inactivity: #379
I have read and followed the submission guidelines and, in particular, I
typst.toml
file with all required keysREADME.md
with documentation for my packageLICENSE
file or linked one in myREADME.md
exclude
d PDFs or README images, if any, but not the LICENSE