Typst for scientific journals: a no-code alternative

Typst can be an interesting alternative to LaTeX for authors who want to write and typeset scientific documents using a more modern and accessible markup language.
However, preparing a manuscript is not the same as producing a scientific journal.
A journal needs to work with the files it receives from authors, review metadata, apply its editorial design, manage proofs and generate different publication formats. To cover this process, the team needs more than a tool capable of creating a good PDF.
Index Production (Auto Markup Styler) is an alternative to Typst designed specifically for editorial teams. It turns Word manuscripts into PDF, HTML and JATS XML from a visual environment, without forcing editors to learn a markup language or work with code.
Typst is simpler than LaTeX, but it is still a markup language
Typst describes itself as a markup-based typesetting system and an alternative to word processors and LaTeX. Content is written using its own syntax, which is then processed to generate the document.
Its language may be easier to learn than LaTeX, but users still need to:
- know Typst syntax;
- use functions and commands;
- configure or adapt templates;
- check for possible compilation errors;
- convert the manuscripts received into its working structure.
For an author familiar with this kind of tool, this system can be convenient. For an editor who receives articles in Word and has to prepare many documents each year, it means adding a new language and an extra step to the process.
A scientific journal needs much more than a PDF
Editorial production begins once the article has been accepted.
From that point on, the journal must:
- check titles, authors and affiliations;
- verify abstracts, keywords, DOIs and ORCID iDs;
- structure tables, figures and references;
- apply its visual identity;
- prepare and correct proofs;
- generate the publication formats;
- organise articles, issues and volumes;
- prepare the content for the web and for indexing.
Typst is mainly geared towards typesetting documents. Although it can generate PDF and is developing HTML export, its current official documentation still considers the latter incomplete and advises against using it in production.
In addition, JATS XML generation, editorial metadata review, proofs and volume management are not part of an integrated editorial workflow equivalent to that of Index Production.

Index Production: an alternative to Typst designed for editors
Index Production starts from a common reality: most journals receive manuscripts in Microsoft Word.
Instead of forcing the team to rebuild the article in a new language, Index Production lets them work directly from the file received.
The process is visual and simple:
- The editor uploads the Word manuscript.
- Index Production extracts and organises the content.
- The team reviews and validates the metadata.
- The journal template is selected.
- The PDF, HTML and JATS XML are generated.
- Proofs and corrections are managed from the same environment.
There is no need to write code, memorise commands or understand the technical structure of an XML file.
The technology works in the background so the editor can focus on reviewing the content and controlling publication. Index Production also lets you save templates, centralise proofs, manage volumes and generate the final PDF of each issue.
Typst vs Index Production for scientific journals
| Editorial need | Typst | Index Production |
|---|---|---|
| Main user | Author or technical profile | Editorial team |
| Way of working | Markup language | Visual interface |
| Learn a new syntax | Yes | No |
| Work directly from Word | Requires adaptation | Yes |
| Generate PDF | Yes | Yes |
| Generate HTML for publication | Still in development | Yes |
| Generate JATS XML | Requires an additional step | Yes |
| Review scientific metadata | Needs to be configured | Integrated |
| Apply editorial templates | Through functions and configuration | Visual template selection |
| Manage galley proofs | Not its main function | Yes |
| Manage articles and volumes | No | Yes |
| Recurring editorial production | Requires building the workflow | Integrated |
The difference is not only which tool produces the best document. It is how much work the team has to do before and after generating it.
Typst helps you write and typeset documents. Index Production helps you turn manuscripts into scientific publications.
From Word to PDF, HTML and JATS XML without code
PDF is still important, but it is no longer enough for many journals.
The same article may need:
- a typeset PDF for reading, downloading or printing;
- HTML adapted for web publication;
- JATS XML for structuring, interoperability, preservation and indexing.
With Index Production, these formats are generated from the same editorial workflow. The team does not have to prepare each version separately or replicate corrections manually.
This reduces duplication and prevents the PDF, HTML and XML from containing different versions of the article.
It also lets the journal maintain a consistent identity through its own templates with its typefaces, colours, headers, tables, figures, licences, DOIs and citation data.
When should you choose Index Production?
Index Production is particularly suitable for journals that:
- receive most of their manuscripts in Word;
- do not want their editors to learn Typst, LaTeX or XML;
- need a visual, intuitive tool;
- publish several articles per issue;
- require PDF, HTML and JATS XML;
- want to automate typesetting in OJS;
- need to review metadata and proofs;
- want to maintain their own visual identity;
- want to reduce manual processes and duplicate files.
Typst can still be a good option for authors who write from scratch and are comfortable using a markup language.
When the need is editorial, recurring and multi-format,
Index Production is particularly suitable for journals that:
- receive most of their manuscripts in Word;
- do not want their editors to learn Typst, LaTeX or XML;
- need a visual, intuitive tool;
- publish several articles per issue;
- require PDF, HTML and JATS XML;
- want to automate typesetting in OJS;
- need to review metadata and proofs;
- want to maintain their own visual identity;
- want to reduce manual processes and duplicate files.
Typst can still be a good option for authors who write from scratch and are comfortable using a markup language.
When the need is editorial, recurring and multi-format, Index Production offers a simpler and more complete workflow.
Index Production is particularly suitable for journals that:
- receive most of their manuscripts in Word;
- do not want their editors to learn Typst, LaTeX or XML;
- need a visual, intuitive tool;
- publish several articles per issue;
- require PDF, HTML and JATS XML;
- want to automate typesetting in OJS;
- need to review metadata and proofs;
- want to maintain their own visual identity;
- want to reduce manual processes and duplicate files.
Typst can still be a good option for authors who write from scratch and are comfortable using a markup language.
When the need is editorial, recurring and multi-format, Index Production offers a simpler and more complete workflow.
FAQ
Can Typst be used to typeset scientific journals?
Typst can be used to typeset articles and other scientific documents. However, a journal working with Word manuscripts, metadata, proofs, JATS XML and volumes will need additional processes or tools.
Can Typst work directly with Word documents?
Typst does not use Word as its main working format. Content must be adapted or converted to its language before being typeset.
Can Typst generate JATS XML?
JATS XML is not part of a native Typst editorial workflow. Obtaining it requires adding a conversion or additional development. Index Production integrates JATS XML generation into editorial production.
Is Index Production easier to use than Typst?
For a non-technical editorial team, yes. Index Production uses a visual environment and does not require writing commands, editing code or rebuilding each manuscript in a different syntax.
Can Index Production be used with OJS?
Yes. Index Production can complement OJS and handle post-acceptance production: structuring, metadata, typesetting, proofs and generation of PDF, HTML and JATS XML.
Produce your journal without learning a new language
Editors should not have to become programmers to publish a scientific journal.
Index Production lets you work directly from Word, review the content visually, apply the journal’s template and generate all the formats you need from a single environment.
No code. No duplicate processes. No new language to learn.
Discover how Index Production can simplify your journal’s editorial production and request a demo.
