Elysia Tools
Navigation
Workflow Playbook
Convert HTML, Markdown, README, or plain text into polished PDFs with page templates, typography, headers, footers, numbering, TOC, columns, and direction checks.
Hubs
A reliable print PDF workflow begins by identifying the document source. If the source is HTML, use html-to-pdf-precise or html-to-pdf-renderer depending on whether strict layout control or browser rendering fidelity matters more. If the source is documentation, markdown-to-pdf-converter, markdown-to-pdf-theme-pack, and github-readme-to-pdf keep the authoring format close to the final export. For simple printable notes or transcripts, text-to-pdf-converter may be enough.
After the first PDF exists, review the page system before decorating it. pdf-basic-text-doc establishes a simple document baseline, pdf-page-master-template defines repeated page rules, pdf-multi-column-layout checks reading flow, and pdf-typography-playground helps tune spacing, line length, and visual density. This order prevents final headers or numbers from masking basic layout problems.
The last pass turns a rendered document into a deliverable PDF. Use pdf-section-toc-generator for navigation, pdf-header-footer-snippets for repeated context, and pdf-page-numbering-styles for front matter, body, and appendix numbering. If the document contains Arabic, Hebrew, mixed-code examples, or translated labels, add pdf-rtl-ltr-support before approval. A good final review names the source, paper settings, template rules, typography decisions, navigation elements, and language-direction checks.
Workflow playbook
Start from the real source of truth: render HTML with precise or browser-oriented conversion, transform Markdown with a converter or theme pack, capture a GitHub README, or create a basic PDF from plain text.
Create the basic document, apply reusable page masters, test multi-column regions, and tune typography before adding production furniture that would hide layout problems.
Finish with section tables of contents, headers and footers, numbering styles, and RTL/LTR checks so the PDF is navigable, printable, and safe for multilingual readers.
Use the HTML tools when browser layout fidelity matters, the Markdown and README tools when documentation source is canonical, and the text tool when the job is a simple printable transcript or plain report.
A one-off can stop after conversion and light typography review; recurring reports, manuals, or packets should add page masters, numbering rules, TOC structure, and header-footer snippets.