Type something to search...

Some things are just faster in raw Markdown. Click Raw Markdown in the editor toolbar to switch.

The Raw Editor

Markdown mode is a full code editor with:

  • Markdown syntax highlighting, matching your light or dark theme
  • Word wrap
  • Line numbers and code folding on wider screens
  • Its own fullscreen toggle

Everything you type is the literal file content — frontmatter delimiters excluded, since frontmatter stays in the form on the left.

Click View in Rich Text Editor to switch back.

Cursor Sync

Your cursor position is preserved in both directions. Put the caret in the middle of a paragraph, switch to Markdown, and the caret is at the same point in the source. Switch back and you land in the same paragraph, scrolled into view.

This means you can move between the two views mid-sentence without losing your place — which is the point of having both.

Fullscreen

The Expand button removes the frontmatter pane and gives the editor the whole window. It works in both rich text and Markdown mode. Press it again to restore the split view.

Fullscreen is available on wider screens; below roughly 1536px the editor already uses tabs, so there’s nothing to expand.

When Rich Text Can’t Parse a File

Some Markdown is too unusual for a visual editor to represent safely — heavily nested HTML, unusual MDX, malformed syntax. When that happens Sitepins shows:

Rich text failed to parse your content! Try our raw editor

and switches to Markdown mode automatically. Your content is untouched — the editor is just refusing to guess. Edit it in raw mode, or fix the construct that’s causing the problem and switch back.

This is a safety measure, not data loss. Nothing is rewritten or dropped; the visual editor simply declines to render a file it can’t round-trip faithfully.

Saving

Saving works identically in both modes — same split button, same commit behavior. See Saving & Publishing.

Editing Non-Markdown Files

Markdown mode is for content files. To edit any other file in your repository — a component, a stylesheet, a build config — use the code editor instead.