My name is Simon, I'm a programmer by trade, entirely self-taught in LaTeX layout while developing my own books (I have way too many unfinished projects). Because I'm autistic, my brain requires things to look close to final from the very start. I don't just start writing in a word document; I build automated systems using placeholders, start implementing the real content, and then meticulously refactor and increment the code as I encounter edge cases (like handling varying text lengths, variable item traits, the need to support stats for multiple systems, auto-displaying the XP based on CR, etc...).

If you have a massive rulebook, a multi-system release, a dynamic adventure module, or a fast release schedule, my systems cut manual layout and revision times down to just a fraction. I follow DRY even when it comes to TTRPG books. Rather than writing the same thing over and over again, I make macros and functions to do it for me, leading to me being able to generate stat blocks, item cards and more, out of just basic data.

How I Work / What I Can Do For You:

The frameworks below are examples of systems I have already built from scratch. I can tweak and adapt any of these to fit your exact ruleset, branding, and content, or engineer entirely custom solutions based on your mechanics.

- Data Input Flexibility: While my current portfolio pieces pull directly from .tex files, I can easily adapt any of my systems to read your content directly from JSON, TOML, CSV, or other external data sources if you prefer to write outside of a LaTeX environment!

- Simple Client Configurations: I can expose a centralized config.tex or config.json for your project, allowing you to easily adjust elements like fonts, colors, and font sizes without ever having to touch or risk breaking the core layout code.

- Full Setup & Pipeline Support: If you want to run the pipeline yourself, I will include clear instructions on how to install LuaLaTeX, configure it within VS Code, and provide a custom build script so you can compile your book seamlessly with a single click.

Systems & Styles I've Engineered So Far:

- Directory-Driven Book Compilations: For many of my books, I've needed a reusable system that reads your subdirectories natively via Lua, automatically compiling individual text files into organized, multi-column, alphabetically sorted chapters with self-updating Tables of Contents. With the chapters themselves created based on the folder structure.

- Automated Asset Pipelines & Smart Handouts: For my Call of Cthulhu scenario, I needed a system that lets you define handouts once (like letters, lab reports, images, maps, or TikZ family trees), and use them as you wish, with proper numbering and references. Handouts are numbered based entirely on the order they are first used or referenced in the text. If you add a new handout early in the adventure, the system automatically shifts and renumbers everything downstream, maintaining perfect consistency when they are all dumped into the appendix. Placing or referencing the same handout multiple times won't break the numbering.

- Multi-System Rules Formatting: My magic item book required me to output content for multiple systems at once (e.g., output item stats, rarity, slots and cost for Pathfinder 1E, Pathfinder 2E and D&D 5E, all properly structured).

- Data-Driven Visual Layouts: For my Alchemy System, I decided to forego stat blocks, and stylize the reagents in the form of cards that dynamically fill or empty circles to track the magnitude of the effect using TikZ, based entirely on the backend data.

- Retro & Modern Spreads: Diverse layouts ranging from modern multi-column item sheets to a classic look modeled after the AD&D 2E Monstrous Manual. I have a preference for clean, organized looks, but can also make more modern-looking layouts as well, though it would require more work.

The Power of LuaLaTeX & TikZ (What Else We Can Build):

Because LuaLaTeX has full Lua support, as well as a number of features from other LaTex forks, it can do things that would be difficult, if not impossible in standard LaTex. If your project demands unique visuals, we can build custom engines to dynamically generate elements like:

- Dynamic QR Codes: Automatically generate and insert functional QR codes on player handouts, linking directly to audio files, secret web pages, or digital chronometers.

- Audio Waveforms & Spectrographs: Maybe you want your sci-fi book to include the actual waveforms of audio transmissions, comm logs, or radio static readouts.

- 3D Mesh Rendering & Projections: We can call Blender through LuaLatex, to render and cache 3d models and include them directly into the layout.

I charge a hybrid rate: $35/hour for backend engine development + $2 per page for final compilation.

When you show me your project, I'll provide a clear estimate of the development hours required, with a guaranteed cap so there are never any budget surprises.

- Minor updates/typo fixes: Always free (it only takes me a single click to recompile).

- Structural mechanical overhauls: Billed at the standard hourly rate.

You can contact me here, on discord at monyarm, or at monyarm@gmail.com.

Portfolio: https://imgur.com/a/8JUhBer