DEV Community: Matthias

From Markdown to print-ready PDF in the browser — here's what the output actually looks like

Matthias — Mon, 11 May 2026 15:51:16 +0000

Most Markdown editors are great for writing. Very few care about what comes out the other end.

I've been building mdedit.io, a browser-based Markdown editor focused on document production: not notes, not quick drafts, but structured long-form documents you can actually hand in, send to a client, or publish — as PDF or DOCX, directly from the browser, without an account, without Word, without LaTeX.

This post isn't about features. It's about the output. Let me show you what a real export looks like.

The document

The demo document is a 27-page academic paper: "Markdown as a Writing and Production Environment for Scientific Work — a criteria-based evaluation of mdedit.io compared to Word and LaTeX." It's written entirely in Markdown, with:

YAML frontmatter (title, author, date, language, citation config)
An embedded CSL-JSON bibliography (Pandoc/Citeproc-compatible)
In-text citations ([@gruber2004markdown], [@pandoc2025], etc.)
Heading-based structure (H1–H4), outline-navigable
Multiple scientific tables with different layout presets
KaTeX math — inline ( $E = mc^2$ ) and block (Gaussian integral)
A footnote
An embedded image with caption
A code block (YAML)
A long URL as a line-break stress test
Auto-generated table of contents, figure list, table list
Auto-generated bibliography at #refs

In other words: everything that typically breaks in a Markdown-to-PDF workflow.

What the PDF looks like

Title page — clean hierarchy: title in bold serif, subtitle in italic, author and metadata below. No manual formatting. It comes from this Markdown:

::: title-page

# Markdown als Schreib- und Produktionsumgebung ... {.no-toc}

## Eine kriteriologische Bewertung ... {.no-toc}

**Max Beispiel**  
Masterarbeit · Universität Beispiel · 2026-05-10

:::

Table of contents — auto-generated from headings, with page numbers. Figure and table lists generated from captions. One line of Markdown each:

[[toc]]

## Abbildungsverzeichnis
<!-- list-of-figures -->

## Tabellenverzeichnis
<!-- list-of-tables -->

Scientific tables — bordered, with distinct header styling. You pick the layout with a directive:

::: table{layout=scientific}
| Kriterium | Word | LaTeX | Markdown |
| --- | --- | --- | --- |
| ...
:::

Math — KaTeX renders in preview, exports cleanly to PDF:

$$
\int_0^\infty e^{-x^2} \, dx = \frac{\sqrt{\pi}}{2}
$$

Bibliography — placed at #refs, rendered automatically by Citeproc from the embedded JSON. Every citation in the text links to its entry. The bibliography is embedded directly in the document, not dependent on an external file or live Zotero connection.

Footnote — marker in text, content at page bottom. Stable across pages.

Page numbers — bottom of every page, via the layout's footer config.

The result is a document that looks like it came out of a publishing system — because under the hood, it did. mdedit.io uses Pandoc + Citeproc + a custom CSS/paged layout stack. But you never touch any of that directly.

The Markdown source

The complete source is plain .md. No LaTeX escapes, no special syntax beyond standard Markdown extensions (GFM, KaTeX, Mermaid, footnotes, custom directives). It's readable without rendering. It's diffable. It's pasteable into Claude, ChatGPT, or any other AI and stays structurally intact — headers, tables, citation markers and all.

That last point matters more than it sounds. AI models work on explicit text structure. A Markdown document lets a model replace a section, restructure an argument, or adjust a table without destroying the citation layer or the layout commands. A .docx file does not.

What mdedit.io is not

It's not Obsidian. It's not a second brain or a notes app. It's not Typora or iA Writer.

It's also not a LaTeX replacement for math-heavy papers, OSCOLA-style legal footnotes, or thesis templates where the university sends you a .cls file.

It's the gap between those two worlds: structured document production for people who want to write in Markdown and get a clean, print-ready output — without a desktop app, without a toolchain, without an account.

Try it

The beta is live at mdedit.io — open the demo document and hit "PDF download." The source is on GitHub under Apache 2.0, self-hostable with Docker.

I'd especially like to know:

Does the export quality meet your bar for real documents?
What's missing for your specific workflow (thesis, specs, reports)?
Does the no-account / browser-only approach work for your use case?

Feedback via GitHub Issues or in the comments here.

Looking for feedback: mdedit.io, a no-account Markdown editor

Matthias — Mon, 04 May 2026 12:09:49 +0000

I built mdedit.io — a no-account Markdown editor with live preview, collaboration and AI assistance

I’m looking for feedback on the public beta of mdedit.io:

https://mdedit.io

Repository:

https://github.com/MatthiasHertel21/mdedit

mdedit.io is a browser-based Markdown editor focused on writing, structuring, previewing, sharing and exporting longer Markdown documents.

It does not require an account. You can open it, start writing, preview your document, navigate it through an outline/tree view, export it as Markdown, PDF or DOCX — and optionally share or collaborate on documents by permalink.

The beta also includes an AI assistant panel that can help with writing, rewriting, summarizing and improving Markdown content.

Why another Markdown editor?

There are already many good Markdown tools.

Some are great as desktop apps.
Some are great inside an IDE.
Some are great for personal knowledge management.
Some are great for team collaboration.

But I often wanted something slightly different:

open a browser
start writing immediately
see a live preview
keep an overview of the document structure
use Markdown extensions like Mermaid and KaTeX
share a document without setting up a workspace
get lightweight AI assistance while writing
export the result cleanly as PDF or DOCX
do all of that without creating an account first

That is the use case I built mdedit.io for.

What mdedit.io currently supports

The current beta includes:

browser-based Markdown editing
no account required
live preview
split editor/preview layout
outline/tree view for document structure
GitHub-flavored Markdown features
tables
task lists
footnotes
Mermaid diagrams
KaTeX math rendering
image paste / drag-and-drop support
Markdown download
PDF export
DOCX export
ZIP export for multiple documents
optional permalink sharing
lightweight collaborative editing
participant display names for collaboration
automatic joining of shared documents, if enabled
AI assistant panel
configurable AI providers/models
keyboard shortcuts
multilingual UI
Apache-2.0 source code

Collaboration in the beta

mdedit.io is primarily designed as a fast writing and document-export tool, but the beta also includes lightweight collaboration features.

The idea is not to recreate a full enterprise workspace. Instead, I wanted collaboration to feel simple:

Share a document. Let someone open it. Work on the same Markdown content.

Current collaboration-related features include:

optional document sharing by permalink
shared document access without requiring user accounts
collaborative editing support
display names for collaborators
settings for allowing collaborative editing
settings for automatically joining shared documents

This is one of the areas where I would especially appreciate feedback.

I’m interested in questions like:

Does permalink-based sharing feel natural?
Is it clear when a document is shared?
Is the collaboration model understandable without accounts?
Would this be useful for reviewing docs, notes, specs or drafts?
What would make it feel safer or more trustworthy?

AI assistance

The beta also includes an AI assistant panel directly inside the editor.

The goal is not to make AI the main product. Markdown editing should still work perfectly without it.

Instead, AI is meant to be a writing companion for common document tasks:

rewrite a paragraph
improve wording
summarize a section
generate a draft from notes
explain or simplify text
help structure a document
suggest headings
improve technical documentation
work with Markdown content directly

The UI includes configurable AI provider/model settings, so the assistant can be adapted depending on the available provider setup.

I’m especially interested in feedback on whether AI belongs directly in this kind of Markdown editor, and where it is actually useful instead of distracting.

The main idea

The core idea is simple:

Write Markdown. See the structure. Collaborate lightly. Export clean documents.

I am not trying to replace every Markdown tool.

mdedit.io is mainly for people who write longer Markdown documents and care about structure, sharing and export quality:

technical documentation
README files
project notes
specifications
concept documents
academic-ish notes
blog drafts
meeting notes
collaborative drafts
review documents

What makes it different?

The feature combination I am aiming for is:

no-account browser workflow
live preview
outline/tree navigation
Mermaid and KaTeX support
optional permalink sharing
lightweight collaboration
built-in AI assistance
print/export-oriented layout
PDF and DOCX export
open source / self-hostable foundation

Tools like VS Code, Obsidian, Typora, StackEdit and HackMD are all useful in their own ways. mdedit.io is meant to be more focused:

Open it, write a document, inspect the structure, optionally share or collaborate, then export it cleanly.

Important beta notes

This is a public beta, so some things are still evolving.

Known limitations:

no offline-first mode yet
browser and mobile behavior still need more testing
import workflows are not fully built out yet
some advanced features are still experimental
collaboration is still a beta feature
AI integration depends on configured providers/models
the hosted version stores documents server-side to support sessions and sharing

Because of that, I would not yet recommend the hosted beta for highly sensitive documents. For more control, the project can be self-hosted.

What I would love feedback on

If you try it, I would especially appreciate feedback on:

Is the editor flow intuitive?
Does the outline/tree view help with longer documents?
Is permalink sharing understandable?
Does collaboration work the way you would expect?
Is the AI assistant useful inside a Markdown editor?
Which AI tasks would you actually use while writing?
Is the PDF export useful for real documents?
Is the DOCX export good enough for your workflow?
Do Mermaid and KaTeX rendering work as expected?
What browser/device did you use?
What is confusing?
What is missing compared to your current Markdown tool?
Would you use this again for a real document?

Feedback is welcome via GitHub issues or directly here in the comments.

Beta:

https://mdedit.io

Repository:

https://github.com/MatthiasHertel21/mdedit

Thanks for taking a look.