TL;DR Collabst is a FOSS, self-hostable, collaborative Typst editor that works in the browser. It's available here: https://github.com/collabst/collabst/ and we are looking for contributions. Help us make it perfect !

Hi everyone,
We built a new web-based self-hostable app for collaborating on Typst projects, and its called Collabst (pronounced collapsed, /kəˈlæpst/).

After 6 months of work, this project has finally reached a stable-enough state for its repository to go public. Here is a bit of background: The Collabst project was created with the objective to create the equivalent of ShareLaTeX (now going by the name of Overleaf Community Edition) but for Typst. This came out of the frustration our team had. We're working in a public research lab that stopped paying for Overleaf and now self-hosts its free instance instead. This also means the lab won't pay any time soon for similar products, like the official Typst Web-App self-host paid plan. And though the Typst Web-App is undeniably a fantastic application, we felt like there was enough room to also provide a free and open source alternative, similarly to ShareLaTeX in the LaTeX world. We think this could help with Typst adoption, especially in research labs and scientific production.
As this is not meant to compete with Typst's official web app, we chose to license Collabst under AGPL-3.0, which should discourage most people from creating a direct competitor and threatening the business model behind Typst development.

Features

Here are a few of the main features of Collabst:

• Typst project Editor, with Syntax Highilighting & Dynamic Preview
• File & Asset management
• Dashboard for managing your Projects.
• Light & Dark Theme (with optional negative preview in dark theme)
• Account + Login system
• Collaborative Features:
  • Project Sharing
  • Collaborative file editing
  • Comments
• Export to PDF or export project sources as ZIP And much more !

Current Limitations

In its current state, the app is far from perfect. It still has some bugs, and there are many features that still need to be added or ironed out.
To mention just a few, as of writting, Collabst lacks:

• Support for all export option (such as PNG, SVG or HTML)
• Typst compiler choice
• Collaborative Suggestions (= distinguishing between a Comment and a Suggestion that modifies the text file.)
• Document Outline
• Zotero Synchronization
• Proper Project Management page
• Support for using in-house Login Systems instead of the one provided by Collabst (this one certainly would help with lab deployment)
• UI Translations (it's only in English for now)
• Cannot jump between code and preview cursor location in the editor And for the repository itself, it lacks:
• A proper Testing Suite
• A proper Demo on the github.io page.

Contributing

Collabst is currently a spare-time project made by 4 people, but if you are as enthousiastic as we are about this project and its potential, you can contribute too !
If you have a feature you would like to implement, or even just want to make some feedback, make sure to check the Contribution Guidlines of the Collabst repo to see how you can help.

Collabst is available here: https://github.com/collabst/collabst/
Keep in mind, things are still prone to change !

I hope you guys will enjoy our project, take care ;)

I am trying to draw a circuit in the photo, I am using circuiteria (I tried using zap but the gates style doesn't work and I need to use IEEE style). I am stuck at drawing custom shapes, I don't know how to draw a voltmeter. If you already used this and know how to make custom shapes or if there is any better packet for this that you know I would love to try. It's my first day using this program and I couldn't find anything that would work.

In the past two years, I developed Oicana, a toolset to use Typst for document templating from your own code. I got frustrated with existing solutions for templating in software and wanted to use Typst for it. But at the time, options to integrate with Typst from software were mostly limited to one language. I needed something that could render the same template in the browser and from C# - so I built it.

Oicana consists of multiple core crates that wrap the Typst compiler crate and define a common template format including snapshot testing and input handling with fallbacks.

An Oicana template consists of "normal" Typst files that can use any packages and a manifest file. This is what a minimal template can look like:

#import "@preview/oicana:0.1.1": setup

#let read-project-file(path) = read(path, encoding: none)
#let (input, oicana-image, oicana-config) = setup(read-project-file)

#set document(date: datetime.today())

= Hello from Typst, #input.info.name

Now we can pass names into the template from any Oicana integration.

[package]
name = "example"
version = "0.1.0"
entrypoint = "main.typ"

[tool.oicana]
manifest_version = 1

[[tool.oicana.inputs]]
type = "json"
key = "info"

To compile the template from your own code, pack it using the Oicana CLI, then use one of the available integrations:

• Browser
• Node.js
• C#
• Java
• PHP
• Python
• Rust

For example, this is the relevant code to render the document from above in Python:

import json
from pathlib import Path

from oicana import CompilationMode, Template

template_bytes = Path("example.zip").read_bytes()

with Template(template_bytes) as template:
    pdf = template.compile(
        json_inputs={"info": json.dumps({"name": "Alice"})},
        mode=CompilationMode.PRODUCTION,
    )

Oicana is source available on GitHub and you can follow the getting started guide to quickly try it out. Usage is free for personal projects, research, education, and open source under the non-commercial license.

Hey r/rust,

I’ve been working on a small project called PaperJet: https://paperjet.dev

It’s an API that takes Typst source and returns a PDF. The compute part is written in Rust, and the goal is to make PDF generation less painful for product/SaaS use cases like invoices, receipts, reports, exports, etc.

It’s still early, but it’s live now and I’d love to get feedback from people who care about Rust/dev tools/docs/API design.

Things I’m especially curious about:

• does the API feel simple enough?
• is the documentation clear?
• does the Typst-based approach make sense for your use cases?
• what would stop you from using something like this in production?

You can sign up and create an API key from the Dashboard.

Docs are here: https://api.paperjet.dev/docs

Happy to hear any feedback !

Link: https://github.com/voxell-tech/velyst

Hey Reddit folks, I’ve been experimenting with real-time Typst rendering inside Bevy using Vello. The idea is to treat Typst as something more like a reactive, interactive 2d vector scene.

One interesting aspect is that Typst functions can be evaluated and rendered dynamically, which opens up possibilities for dashboards, data visualization, motion graphics (sth I’m heavily targeting, similar to manim), UIs

I’m working hard towards making the scene queryable/modifiable (esp for animations). Curious what the Typst community thinks. What use cases would you want from “live Typst”?

Any feedback is welcomed! Especially around architecture or use cases I might be missing.

Jumpstart your Typst Thesis with a GitHub repo template. I've extracted this from my Bachelor Thesis, see also my other blog post.

Blog: https://splines.me/blog/2026/typst-thesis-starter
GitHub: https://github.com/Splines/typst-thesis-starter

Hola a todos 👋

Estoy buscando un freelancer con experiencia en Typst para desarrollar un ebook técnico de gran tamaño (más de 500 páginas).

El proyecto incluye contenido académico con una gran cantidad de:

• Ecuaciones matemáticas
• Fórmulas químicas
• Expresiones de física
• Diagramas y contenido educativo técnico

Busco a alguien que:

• Ya haya trabajado con Typst o sistemas similares tipo LaTeX
• Tenga experiencia maquetando contenido académico/científico
• Sepa crear documentos limpios, modernos y bien estructurados
• Pueda optimizar estilos, índices, referencias y consistencia visual

Idealmente me gustaría ver ejemplos de trabajos previos o portfolios relacionados con documentación técnica, libros académicos o material educativo.

Si tienes experiencia o conoces a alguien que pueda ayudarme, mándame DM