Ah yes I didn’t notice you were the one who linked it!
No they shot it down because it was not technically the solution they wanted. And as a side remark they complained that the PR included non-open-source code extracted from the website.
4 Likes
It’s funny that Typst is yet to become important (or referenced) enough to earn its place in Wikipedia.
4 Likes
What would be the recommended typst package for slides? Kind of like beamer in LaTeX.
(For now, a simple 5 page presentation in 20 minutes with some math and code, no interaction, linear structure. Being able to customize colors and insert a logo would be nice.)
I’ve tried polylux and it was quite simple!
It’s not hard to create your own theme from scratch, but you can also start from or directly use existing ones (such as basic-polylux – Typst Universe or metropolis-polylux – Typst Universe).
2 Likes
I think touying – Typst Universe is currently the foremost slides package. It is based on polylux, but is more actively developed (though polylux also seems to be worked on.)
7 Likes
Thanks for the tips, touying worked well for my purposes.
My kvetching above about the docs may come across as negative, so here are some things I like about typst:
- very easy to just
#importextensions, even lets you specify the versions. no need to download packages - compilation is really fast
- package have no-frills defaults, mostly. eg I was pleasantly surprised that
touyingdoes not include a header, footer, nav buttons, and other items in the kitchen sink by default in the “simple” style (cfbeamer, where I have to start disabling a lot of stuff to get clean look) - defining colors with
rgb(#whatever), in contrast to thetikzmadness ofA!blend!Bwhich was always driving me crazy - it is a programming language with a thin document-friendly surface syntax and an intuitive code syntax like almost every language in the Algol 60 family.
letand parentheses and similar.
18 Likes
For these simple requirements you could as well roll your own “slide system” 
// Paper can also be presentation-16-9
#set page(paper:"presentation-4-3", numbering: "1", number-align: right)
// Base text size
#set text(24pt)
// New slide for each level 1 heading
#show heading.where(level: 1): it => pagebreak(weak: true) + it
// More space under headings
#show heading: set block(below: 1em)
// Fancy color for headings
#show heading: set text(rgb("#006699"))
= Slide title
#lorem(20)
$
a^2 + b^2 = c^2
$
#lorem(10)
= Another slide title
#lorem(20)
(For the logo it depends if you want it on a title page or on every slide.)
15 Likes
I spent the last 5–6 weeks trying to use Typst exclusively (except where I collaborate on existing documents with coauthors). I decided to go back to LaTeX for now.
Typst has a great promise and I will return to explore it in the future, but for now I am much more productive in LaTeX because I know my way around. Whenever I want to solve something in Typst, I search for a solution, about 60% of the time it is already available (and usually extremely elegant and well-designed), 40% of the time I ask on the forum, where there is this person (the same person) who shows up within 15 minutes and makes comments that are irrelevant, until someone shows up who actually understands the question which, by now, has 5 replies that are just noise. About half the time I run into an open issue which has no solution yet (if there is an open issue, it has a discussion clarifying that it will be done the Right Way 
, just be patient), half the time the problem is solved.
This is interesting and exciting, as learning new things usually is, but a huge distraction. I have a perfectly fine workflow in LaTeX, which is adequate for my needs, so the incentives to switch are not that large.
But back in LaTeX, I miss the cleanliness of the Typst source syntax. All those extra \s and line noise are grating, even though I have them supressed with gray in Emacs.
30 Likes