LaTeX

sublimated compiles .tex files to PDF + HTML on every push.

how it works

• push a .tex file via git or the API
• sublimated runs latexmk (PDF) and LaTeXML (HTML) on Modal
• PDF stored as render_pdf, HTML as render_html, SVG pages as render_svg
• HTML is the primary web view: text selection, per-block comments, search
• PDF always available for download
• if LaTeXML fails (exotic packages), falls back to SVG page view

features

• dual output: PDF for print/submission, HTML for web review
• structured error log: parsed from .log file, not raw 500-line noise
• multi-file projects: \input, \include, \bibliography resolve via sbl clone
• cascade recompilation: edit refs.bib and all .tex files that depend on it recompile
• TOC sidebar extracted from HTML headings
• per-block comments on HTML elements (sections, paragraphs, theorems, figures)

demo files

• basics.tex — headings, lists, emphasis, quotes
• math.tex — equations, aligned math, matrices, theorems
• code.tex — code listings with syntax highlighting
• tables.tex — tables with formatting and multicolumn
• figures.tex — figures, subfigures, cross-references
• bibliography.tex — citations and bibliography styles
• layout.tex — page setup, columns, spacing
• styling.tex — fonts, colors, custom environments
• article.tex — complete article using all features
• refs.bib — shared bibliography database

multi-file projects

LaTeX projects typically have multiple files. sublimated handles this:

• \input{chapter1} and \include{chapter1} resolve relative to the .tex file
• \bibliography{refs} finds .bib files in the same folder
• \usepackage{custom} resolves local .sty files
• \documentclass{mythesis} resolves local .cls files
• dependencies tracked automatically, cascade recompilation on any change

engines

pdflatex is used by default. sublimated detects when other engines are needed:

• \usepackage{fontspec} → xelatex or lualatex
• \usepackage{luacode} → lualatex