23 posts tagged with "markdown"

Markdown is the lingua franca of everything Confluence isn't: LLM context windows, RAG pipelines, Git-based docs, static site generators. So the request shows up wherever those worlds meet — "can you get our Confluence into Markdown?" — and the honest answer starts with a gap: Confluence Cloud has no native Markdown export. Built-in export gives you PDF, Word, HTML and XML; Markdown isn't on the list. Here's how to get there anyway, and how to make the output something a pipeline can actually consume.

Inline code — monospace text on a subtle background — is how you mark up variable names, file paths, key names, and short commands inside a sentence: set MAX_RETRIES = 3, edit ~/.zshrc, or run kubectl get pods. Confluence Cloud has three ways to produce it, and each fits a different moment: formatting as you go, typing Markdown, or bringing Markdown in from your repo.

The diagrams live in the repository. They were written in Mermaid, they are reviewed in pull requests next to the code they describe, and they are correct as of the last commit. The documentation, however, lives in Confluence — because that is where the rest of the team reads it. So somebody copies a Markdown file across, pastes it into a Confluence page, and the flowcharts, sequence diagrams and ER models arrive as grey boxes of unrendered code.

Everyone has hit this. It is one of the most common Confluence complaints, and the usual workarounds are worse than the problem: export every diagram to PNG and re-upload them (now they rot), keep the diagrams in an external tool and paste links (readers need a second account, and the links break), or build a browser extension to force rendering on paste.

There is a better answer, and Mermaid 12 makes it better still.

Every team has Markdown lying around that Confluence needs: the README that became the service doc, the design doc drafted as a pull-request description, the runbook that lives in the repo. And every attempt to move it hits the same wall — Confluence's default editor does not parse Markdown. Paste a .md document and you get a wall of pipes, backticks, and asterisks that looks exactly like what it is: text nobody formatted.

The macro route dissolves the wall. Paste the document into a Markdown macro that actually parses it, watch it render in the preview pane, publish. This page is the workflow, end to end.

Every engineering page in Confluence eventually holds code — a curl from the runbook, the config that fixed the incident, the query the dashboard runs. And every one of those snippets has three natural enemies: the language dropdown in the macro dialog, the paste that loses its indentation, and the reader who cannot copy the thing without dragging across line numbers.

Markdown fences solve all three, because they make the code block text you type instead of an object you configure. ```bash, paste, ``` — done, highlighted, copyable. This guide shows the syntax, the theming behavior, and when fences beat the native macro.

Ask an engineer to document an algorithm in Confluence and watch what happens to the math: O(n log n) typed as plain text, x² pasted from a character map, and — for anything real — a screenshot from an online equation editor, blurry and already out of date. Confluence has no native LaTeX support, so every formula becomes either a compromise or an image.

It does not have to. With a Markdown macro on the page, Confluence renders real LaTeX — inline $...$, display $$...$$, fenced blocks with full align environments — and the equation stays text: searchable, theme-consistent, editable in seconds. This guide gives you the syntax and copy-paste examples for all three routes.

Meeting notes fail in one of two directions: they are so informal that nobody can find the decision a month later, or so formal that nobody takes them at all. The Confluence editor quietly encourages the second — formatting dialogs are the enemy of live note-taking.

Markdown flips it. In a split-pane editor, notes are keystrokes: two characters for a heading, pipes for a table row, backticks for a snippet — and the rendered page assembles itself in the right pane while you type. This guide ships the template and the habits that make notes pages worth opening later.

The use case diagram is the scope picture: actors on the outside, what the system does for them on the inside, and — the reason product and engineering fight — the line between them. In Confluence that picture usually comes from a diagramming tool export that goes stale the moment scope moves.

Mermaid 12 added the syntax to render UML use case diagrams from text — usecase-beta — and Enhanced Markdown for Confluence renders it in the same macro as everything else on the page. This guide gives you the syntax and two copy-paste diagrams.

Sequence diagrams die in Confluence in one of two ways: someone draws one in a diagramming tool, exports a PNG, pastes it into a page — and three sprints later the flow has changed but the image has not. Or someone writes the flow as prose ("the client calls the order service, and if payment is approved…"), which is accurate but impossible to read under time pressure.

ZenUML splits the difference: the diagram is code, so it edits like code and renders like a diagram — branches, error paths, and parallel work included. This guide shows the syntax with copy-paste examples you can drop into Confluence today.

Meeting notes, project briefs, planning docs — most Confluence pages already start life as a Markdown-ish outline: a title, some headings, bullets underneath. A mind map is just that outline seen from above. This guide shows how to get from the outline you already have to an interactive mind map on the page, without drawing anything and without learning diagram syntax.

In 2004, John Gruber released Markdown with a modest pitch: a text format that is easy to read, easy to write, and converts cleanly to HTML. Twenty years later his side project became the default language of technical documentation — GitHub renders it natively, Stack Overflow is built on it, Obsidian and Notion popularized it, and every major LLM speaks it fluently. The Verge called it "the default language of the AI era."

That last part is the interesting one. Markdown didn't just survive the AI transition — it locked in because of it. This article walks through why, and what it means for how your team should write documentation inside Confluence.

Bold text is one of the most common formatting actions in Confluence — for headings, callouts, and emphasis inside paragraphs. There are two ways to do it: the toolbar button / keyboard shortcut in the standard editor, and Markdown syntax inside Enhanced Markdown for Confluence. This guide covers both, plus the common "why isn't it working" cases.

A block quote sets a passage apart from the surrounding text — usually indented with a left border — to indicate that the words are quoted from another source. Confluence does not have a dedicated "quote block" button, but there are three reliable ways to create one. This guide walks through each and helps you pick the right one.

Developers, technical writers, and data scientists think in Markdown. READMEs, API docs, pull request descriptions, and design specs are all written in it. But Confluence — where most of that knowledge ends up living — has no native Markdown support. Pasting Markdown into the WYSIWYG editor produces broken tables, literal asterisks, and lost formatting. This guide walks through the options so you can pick the right Markdown approach for your team without trial and error.

The scenario every technical team hits: your engineering docs live in Markdown — READMEs, API references, design docs — and they contain diagrams (Mermaid), equations (LaTeX), and code samples. You paste that Markdown into Confluence, and it falls apart. The Mermaid code blocks render as plain text. The LaTeX equations show as raw $...$ syntax. The code blocks lose their syntax highlighting. Confluence's native editor is WYSIWYG, not Markdown, and the import tools treat Markdown as a one-time conversion rather than something you edit live.

Enhanced Markdown for Confluence solves this with a Markdown editor that renders everything inline — Mermaid diagrams, KaTeX and LaTeX math, syntax-highlighted code, and GitHub-flavored tables — with a live split preview. It runs on the Quikdown engine, so all rendering libraries are bundled locally (no external CDN dependencies, which matters for "Runs on Atlassian" compliance). This guide walks through writing Markdown in Confluence with diagrams, math, and code all rendering live.

Developer teams use Confluence differently than marketing or HR. You document APIs, share architecture diagrams, write runbooks, and collaborate on code reviews. The default Confluence editor works, but it wasn't built for technical documentation.

This guide covers the best Confluence apps for developers in 2026, organized by use case. We built several of these apps at NGPILOT, so we'll be transparent about where our apps fit and where competitors offer better solutions.

Many teams have documentation in Markdown format (GitHub READMEs, API docs, developer guides) and need to bring it into Confluence. Confluence doesn't have a native Markdown import feature, but there are three ways to get Markdown content into Confluence pages.

Confluence has a visual table editor, but it's slow for creating structured tables — you need to click to add rows and columns one at a time. If you write documentation in Markdown, you can create tables much faster with Markdown syntax.

This guide shows how to create, format, and edit tables in Confluence using Markdown.

Confluence Markdown support lets developers write documentation in their preferred format. This guide covers how to add Enhanced Markdown to Confluence for raw Markdown editing, WYSIWYG preview, tables, code blocks, and more.

Confluence's built-in editor is strictly WYSIWYG — there is no native Markdown editor. For teams who already write in Markdown (README files, docs repos, pull request descriptions), that means manually reformatting every doc through toolbar buttons, losing time and introducing inconsistencies. Enhanced Markdown for Confluence solves this by embedding a full Markdown editor with live split preview directly inside Confluence — and it renders Mermaid diagrams, KaTeX/LaTeX math, and 190+ code-highlighted languages, all in one macro.

This FAQ answers the questions teams ask most often about writing Markdown in Confluence.

Confluence has been the go-to knowledge base and documentation platform for thousands of organizations. At its core, Confluence uses a WYSIWYG (What You See Is What You Get) editor that lets users format content visually -- clicking toolbar buttons for headings, bold text, tables, and macros without writing a single line of markup.

But an increasing number of teams are asking a different question: can we write Confluence content in Markdown instead?

Markdown is a lightweight plain-text formatting syntax originally created by John Gruber in 2004. It has become the default writing format for developers, technical writers, and content teams who work with Git repositories, static site generators, and API documentation. Its appeal is simple: you focus on structure and meaning rather than visual styling, and the formatted output is generated automatically.

Teams choose Markdown over WYSIWYG for several compelling reasons. Developer-heavy teams often already write in Markdown daily -- in README files, pull request descriptions, and documentation repos. Switching to a WYSIWYG editor for Confluence pages feels like a step backward. Markdown content is also plain text, which means it works seamlessly with version control systems like Git, diff tools, and automated pipelines. Finally, Markdown files are portable; the same .md file can be published to GitHub, a static site, or a Confluence page without reformatting.

On the other hand, WYSIWYG editing remains the better choice for non-technical users who prefer visual feedback, drag-and-drop file attachments, and toolbar-driven formatting. Many business teams have no interest in learning syntax rules, no matter how lightweight.

This FAQ addresses the most common questions teams have when evaluating Markdown versus WYSIWYG editing in Confluence, and explains how Enhanced Markdown for Confluence by NGPILOT bridges the gap between both worlds.

Teams move content in and out of Confluence every day — migrating between instances, backing up documentation, importing from other tools, exporting for offline review. Confluence has basic PDF and HTML export built in, but it's limited. No bulk operations, no multi-format support, no structured import workflow.

Over a dozen marketplace apps try to fill this gap, but most solve one narrow problem: PDF export, Word import, or Markdown conversion. We built Modern Importer & Exporter for Confluence to handle both directions — import and export — across multiple formats. In this post we compare it against every alternative on the Atlassian Marketplace.

Developers write in Markdown. Confluence doesn't. Every engineering team that moves from GitHub wikis, README files, or Hugo docs to Confluence hits the same wall — the rich text editor feels slow, and there's no way to write in the format they already know.

Several marketplace apps bring Markdown to Confluence, but they take different approaches. Some embed Markdown as macros. Others import Markdown files. A few offer live editing. We built Enhanced Markdown for Confluence to give teams a full WYSIWYG Markdown editor with code highlighting, charts, UML diagrams, and table merging — all inside the Confluence page editor. In this post we compare it against every alternative.