A Typst Workbench

A few months ago, I had an idea of how I could integrate Typst into some of the work I do. I started toying around with integrating some useful tools, adding photos, handling variable data, serving documents. As I continued on, I realized that I was creating something others might find useful.

Introducing AMjuno - a Typst workbench

Key Features

  • Visual Typst Editor: Real-time preview with Monaco-based code editing.
  • Asset Management: Image upload and management. (disabled in demo :crying_cat_face:)
  • Function Toolkit: One-click snippet insertion for common layouts (Tables, Grids, Headers).
  • Package Manager: Browse and import packages from the Typst Universe (@preview/).
  • Variable Binding: Define variables (JSON) for dynamic template generation.
  • REST API: Full programmatic access for template management and document generation.
  • PDF/UA Support: Built-in support for accessible PDF generation.
  • Self-Contained: Backend compiles Typst in-memory (no external CLI required).

Right now, it is set up in a beta-demo mode, with some limitations. Once there are a few more refinements, the plans are to release - online accounts, and a standalone app and open source version, which can be used as a private server or enhanced by you.

Please feel free to offer feedback, here or on website. I’m looking forward to meeting you and being a part of this amazing, growing community!

7 Likes

Will this be a self-hostable competitor to the official Typst webapp?

This is a great question I have been thinking a ton about. The more I’ve thought about online accounts - a) it’s duplicative b) it’s a headache I don’t want to deal with.

A big part of the reason I shared it here is to garner feedback & integrate ideas, and head in the right direction. My philosophy is to be additive, rather than competitive - both can drive innovation and adoption (but one doesn’t encourage people to become a**holes).

For example, I’ve been tinkering with honing in on education. The way I’ve set up the soft-ware on the backend is very similar to the way a Professor could publish curriculum/tools/cool snippets to a set of students. This could be a money-maker, and in some ways compete - so at least 1/3 of any proceeds, at least, go back into feeding the beast. As would any profit making endeavor.

How does this fit in? How can it benefit the ecosystem? What can I do to be of benefit? - I should have asked initially

1 Like