Is the document still being written, or is it ready for publication review?
Use list and table formatting while the document is still taking shape, then move to link extraction, preview, and export checks once the structure is stable.
Elysia Tools
Navigation
Workflow Playbook
Clean Markdown structure, review links, merge files, preview the result, translate articles, and export publishable HTML, PDF, slide, text, or JSON deliverables.
Hubs
Markdown publishing works best when the source is readable before any export step begins. Use markdown-list-formatter to normalize rough notes, task lists, and numbered sequences, then use markdown-table-generator when data needs to become reviewable Markdown tables instead of pasted spreadsheet fragments.
Once the structure is stable, run markdown-link-extractor to inspect inline links, reference definitions, image links, bare URLs, duplicates, and anchors. This catches the small publishing failures that are easy to miss in a rendered preview.
For multi-section work, use markdown-merger to combine related files and keep heading levels under control. Then use markdown-preview to check how the merged or edited document renders, including code fences, blockquotes, links, and tables.
If the content is going to another language, use ai-markdown-article-translator after cleanup rather than translating a rough draft. If another system needs the content without markup, use markdown-to-plain-text; if the downstream target needs structure, use markdown-to-json.
The final output should match the publishing destination. Use markdown-to-html for web handoff, markdown-to-pdf-theme-pack for styled PDF output, markdown-report-bundler for multi-file reports with sections and a cover, and md-slide-deck-to-pdf when the Markdown source is a slide deck. A good handoff records the source files, checked links, chosen export path, and any known limitations.
Workflow playbook
Turn rough notes into consistent lists and tables before deeper review, so the rest of the workflow starts from readable source content.
Extract inline links, reference links, image links, bare URLs, and anchors to catch broken references and duplicated destinations before publishing.
Merge related Markdown files when the content spans sections, then preview the rendered HTML to inspect headings, code blocks, tables, and layout.
Translate full Markdown articles when the audience changes, or convert a finished draft to plain text or JSON when another system needs a cleaner payload.
Choose the final output format: HTML for web publishing, themed PDF for styled documents, report bundling for multi-file handoff, or slide PDF for decks.
Use list and table formatting while the document is still taking shape, then move to link extraction, preview, and export checks once the structure is stable.
Single documents usually need preview and HTML or PDF export. Multi-file docs need merging or report bundling. Localized articles need translation before final preview.