Emovart Docs
Working with Notion Docs

⚡ Which Notion block types are supported?

A live tour of every Notion block Emovart renders — plus what happens to the handful it doesn't.

Last updated on July 9, 2026

Hey there 👋

This article doubles as a demo. Nearly every block you see below was written in Notion with zero special setup, synced, and rendered by Emovart exactly as it appears here. Use it as a reference when planning your own articles.

The short version: everything you actually need for help documentation — text, headings, lists, callouts, toggles, media, code — works out of the box. A few workspace-oriented blocks (databases, synced blocks) are skipped gracefully, so an unsupported block never breaks a page; it simply doesn't appear.

Basic Blocks

Paragraph

Plain paragraphs carry Notion's inline formatting through untouched: bold for emphasis, italic for nuance, inline code for keys and commands, and links wherever you need them. Line breaks and paragraph spacing are preserved, so articles read the way you wrote them.

Headings

Notion's three heading levels map straight onto the article's heading hierarchy. Use Heading 1 sparingly for major parts, Heading 2 for sections, and Heading 3 for details. In the Documentation layout your headings also feed the table of contents beside the article — one more reason to use them generously.

A Heading 2 Looks Like This

And a Heading 3 Sits Beneath It

The two demo headings above do real work: they create the visual rhythm of the page and become anchor targets, so you can deep-link readers to an exact section.

Bulleted List

  • Bullets render with clean, readable spacing
  • Inline formatting works inside items — bold, italic, code
  • Long items wrap naturally on small screens

To-do blocks are supported as well: checked and unchecked states survive the sync, which is handy for pre-flight checklists.

Numbered List

  1. Numbered lists keep the numbering you set in Notion
  2. Reordering items in Notion reorders them here
  3. That makes them perfect for step-by-step instructions

Quote

Quote blocks get a distinct treatment so they stand apart from surrounding text:

Good documentation is a conversation with a reader you'll never meet — be kind to them.

Divider

A divider becomes a subtle horizontal rule, great for separating loosely related thoughts. Here's one:


Callout

Callouts are the workhorse of good docs. The emoji you pick in Notion becomes the icon, and the tinted background makes the block impossible to skim past.

💡
Use callouts for tips and gotchas that readers must not miss. Whatever emoji the block has in Notion is exactly what shows up here.
They also work nicely as confirmations — "you're done, and here's how to verify everything worked."

External Link

Links to other sites behave exactly as you'd expect — for example, Notion's guide to sharing pages. External links open in a new tab so readers never lose their place in your docs.

Internal Link

Links between your own articles are best written as relative paths, like 🔗 Linking internal Emovart articles. They open in the same tab and keep visitors on your domain.

Code Snippets

Code blocks sync together with their language setting, so syntax highlighting just works. A quick sampler across languages:

const greet = (name) => `Hello, ${name}!`;
console.log(greet("Emovart"));
type Article = { title: string; slug: string };
const doc: Article = { title: "Hello", slug: "hello" };
def greet(name: str) -> str:
    return f"Hello, {name}!"

print(greet("Emovart"))
3.times { puts "Docs that stay in sync. Imagine that." }
package main

import "fmt"

func main() {
    fmt.Println("Hello from a Go snippet")
}
fn main() {
    println!("Rust highlights nicely too");
}
<?php
echo "Even PHP gets proper highlighting";
let blocks = ["paragraph", "callout", "code"]
print(blocks.joined(separator: ", "))
curl -s https://docs.emovart.studio | head -n 5
{ "block": "code", "language": "json", "rendered": true }
.article-body code {
  font-size: 0.9em;
  border-radius: 4px;
}
SELECT title FROM articles WHERE published = true ORDER BY position;

Math Equations

Equation blocks — Notion's LaTeX support — are one of the few text blocks that currently get skipped. If a formula is essential, add it as a code block or drop in an image of it instead.

Bookmarks

Paste a URL in Notion and choose Create bookmark to get a rich preview card. Bookmarks sync and render as clickable cards with the target's title and description — a much friendlier way to reference external resources than a bare link.

Media

Images

Images sync at full quality, scale to the article's width, and captions you add in Notion come along for the ride. PNG, JPG, and GIF all work — animated GIFs are a great lightweight alternative to video for short UI walkthroughs.

Sample synced image
Sample synced image

Complex Layouts

Notion lets you arrange blocks side by side in columns. Column layouts don't carry over one-to-one: Emovart flattens them into a single column so articles stay readable on every screen size. The three photos below sit next to each other in Notion — on the published page they stack.

First column photo
First column photo
Second column photo
Second column photo
Third column photo
Third column photo

Nested content holds up fine

Blocks indented under other blocks — a paragraph under a list item, content inside a callout or toggle — keep their relationships when rendered. The exception is heavily engineered column-in-column arrangements, which are simplified rather than reproduced.

About "magic tables" built from columns

Some Notion users fake tables by lining up column blocks. Because columns flatten, that trick falls apart on the published page — the "cells" end up stacked vertically. Reach for a real simple table instead.

Simple Table

Notion's simple table block is fully supported and renders as a clean, responsive table, with header row and header column styling preserved. For feature matrices, plan comparisons, or anything data-shaped, it beats improvised layouts every time.

Toggles

Toggles become tap-to-expand sections on your site — ideal for FAQs and optional detail that would otherwise clutter the page.

What's hiding inside this toggle? In Notion, this paragraph and the image below are tucked into a toggle block; on the published page the toggle expands with a smooth animation to reveal them.

Toggle reveal image
Toggle reveal image
💡
Content inside toggles is still indexed by your site's search, so answers don't get lost just because they start out collapsed.

Videos

Third Party Videos

Embed videos from YouTube, Vimeo, Loom, and friends by pasting the link in Notion and choosing Embed. They render as a responsive player:

Generic embeds beyond video — Figma files, Google Maps, and similar — render in an embedded frame too, wherever the provider allows it.

Notion Uploaded Videos

Video files uploaded straight into Notion are served through Notion's storage behind expiring links, which makes them unreliable on a public site.

💡
Host longer videos on YouTube (an unlisted video works great) or Vimeo and embed them instead — you get faster streaming, adaptive quality, and no file-size worries.

Audio

Audio blocks are currently skipped during sync. If you need to share a clip or a podcast episode, embed it from the hosting platform or link to it directly.

Files

File attachment blocks are skipped as well — like uploaded video, they sit behind Notion's expiring links and wouldn't download reliably from your site.

💡
Put downloadable files on storage you control (or any public drive) and add a normal link or a bookmark to them. Links always render, and you can swap the file without touching the article.

Synced Blocks

Synced blocks — content mirrored across several Notion pages — are skipped during sync, so anything inside them won't show up in the published article.

💡
Quick check before publishing: synced blocks show a colored outline when you click into them in Notion. If an article looks incomplete on your site, a synced block is the first suspect.
💡
The fix takes seconds: open the synced block's menu and choose Unsync. The content turns into regular blocks and syncs normally from then on.

Unsupported Blocks

For reference, here is the full list of what Emovart skips or simplifies:

  • Databases — table, board, gallery, calendar, and list views don't render. Use a simple table, or restructure the content as articles.
  • Synced blocks — skipped; unsync them to publish their content.
  • Columns — not skipped, but flattened into a single column.
  • Equations, audio, and file attachments — skipped for now.
  • Workspace blocks — buttons, breadcrumbs, and Notion's table-of-contents block don't make sense outside Notion, so they're dropped. (The Documentation layout builds its own table of contents from your headings automatically.)

Skipped blocks never break anything — the rest of the article renders normally around them.

Conclusion

Write documentation the way you'd naturally write it in Notion — text, headings, lists, callouts, images, the occasional toggle and code block — and everything simply works. Stay inside the supported set and your articles will look sharp on any device.

Need more help, or is a block rendering oddly? Hit the Contact button on this site and send us the article link — we're happy to take a look.

Was this article helpful?