Lately, I've been hearing more and more people advocating for using Markdown and other digital formats to publish TTRPGs instead of/or in addition to PDFs. One conversation that stuck with me was from the Sly Flourish podcast, where they discussed the simplicity and accessibility of these formats and how some designers have been embracing markdon.
This got me thinking about an idea I've been tinkering with for a year or two: combining the functionality HTML pages provide with strong graphic design principles to create a single-file TTRPG. No external assets, no JPGs, PNGs, JS, or CSS files. Everything self-contained. My first attempt was for a Fallout TTRPG I was designing just for fun. It mimicked the green-screen look of the in-game terminals, complete with flickering effects and all: [ Ссылка ]

This is my proof of concept:

Features:
A dynamically generated menu bar and table of contents for each "section" of the book.
A simple but functional search feature to help navigate the content.
The ability to bookmark specific headers for easy reference later.

Pros:
Accessibility: A single HTML file works on nearly any device with a web browser, no installation or specific software required.
Offline Functionality: Players and GMs can download the file and use it entirely offline.
Interactive Features: Search, bookmarks, and dynamic menus make navigating the content much easier than flipping through pages.
Customizability: It’s easy to include thematic fonts, colors, and styles without relying on external files.
Portability: One file is simple to share and store compared to folders with multiple assets.
Cost-Effective: No need to print or rely on expensive PDF formatting tools AND you can add your own content using just basic knowledge of html.
Responsive Design: Can be designed to work on both desktop and mobile devices seamlessly.

Cons:
Learning Curve: Designing a functional and visually appealing HTML TTRPG requires some coding knowledge.
Graphic Limitations: Inline images and styles can bloat the file or limit its visual fidelity compared to professional PDFs or printed books.
Compatibility Issues: While most modern browsers handle single-file HTML well, older or less common ones might struggle.
File Size: Embedding all assets (images, fonts, etc.) directly into the HTML can result in a large file size.
Perceived Simplicity: Some might view it as 'less professional' compared to traditional publishing formats like printed books or polished PDFs.
Limited Security: HTML is inherently editable, which might make creators hesitant to distribute without risk of unauthorized modifications.


What do you think of this approach? Could this be a viable format for TTRPGs in the future, or are traditional methods still the way to go? I'd love to hear your thoughts, suggestions, or critiques!

свернуть