Publish to WordPress Without the Block Editor

Gutenberg divides people. Some find the drag-and-drop block editor intuitive. Plenty of developers, technical writers, and content teams find it gets in the way — whether that's because it mangles markdown, doesn't work well with code-heavy posts, or simply doesn't fit into an existing review workflow. The good news is that WordPress has a REST API, and there are several legitimate ways to publish content without ever opening the block editor.

This guide covers each option in detail: what it does, where it falls short, and what kind of publisher it works best for.

Why People Skip Gutenberg

The block editor isn't bad for everyone. If you're building landing pages with custom layouts, or you enjoy clicking through block settings, it works well enough. But for writers and developers who live in other tools, it creates real friction:

• Markdown gets mangled
• You can't write in your own editor
• Code-heavy posts are painful
• No SEO automation from external tools
• Slow for teams with external review workflows

None of these are reasons to abandon WordPress entirely. The platform has too much going for it — SEO plugins, hosting options, media management, plugin ecosystem. The fix is publishing through a different interface, not switching platforms.

Option 1 — Classic Editor Plugin

The simplest escape hatch: install the Classic Editor plugin from the WordPress repository. This replaces Gutenberg with the old TinyMCE-based editor that WordPress used before version 5.0. It's free, officially supported by the WordPress team, and takes about 30 seconds to set up.

Once active, you get a plain rich-text editing area and a sidebar with post settings. You can also switch individual posts between classic and block editor if you want to keep Gutenberg for some content.

Pros: Free, one-click install, officially supported, well understood.

Cons: You're still inside WordPress. Writing still happens in a browser textarea, not your preferred editor. No image automation, no SEO metadata from external sources, no code highlighting.

Option 2 — WordPress REST API

WordPress ships with a REST API at /wp-json/wp/v2/. You can create, update, and publish posts via standard HTTP requests — no browser required. This opens the door to automation: CI/CD pipelines, scripts triggered on Git push, scheduled publishing jobs, or any tool that can make HTTP calls.

Here's a minimal example using curl to create a draft post with Application Passwords authentication:

curl -X POST https://yourblog.com/wp-json/wp/v2/posts   -H "Content-Type: application/json"   -u "your-username:xxxx xxxx xxxx xxxx xxxx xxxx"   -d '{
    "title": "My Blog Post",
    "content": "<p>Post content as HTML.</p>",
    "status": "draft",
    "categories": [5],
    "tags": [12, 18]
  }'

Publishing a real post via the REST API isn't just one call. It's several: image uploads, featured image assignment, SEO metadata, and code highlighting.

Pros: Platform-agnostic, automatable, works in any language, free.

Cons: You're building and maintaining a publishing tool.

Option 3 — Desktop Markdown Editors

Several native Mac apps let you write in markdown and publish to WordPress directly. Ulysses and iA Writer are writing-focused apps with WordPress publishing built in. MarsEdit is a dedicated blog editor for macOS.

Pros: Native app performance, beautiful writing environments, no browser required, direct publish to WordPress.

Cons: Mostly Apple-only, limited automation, weak SEO support, weak code-block handling.

Option 4 — Static Site Generators with WordPress Headless

A more architectural approach: decouple the WordPress backend from the frontend entirely. Use WordPress purely as a headless CMS while building the public-facing site in Next.js, Astro, Hugo, or another static site generator.

Pros: Developers work entirely in their existing tools. Full control over rendering, performance, and code highlighting.

Cons: Significant upfront engineering investment.

Option 5 — Notipo (Write Markdown, Publish Everything)

Notipo is a markdown editor built specifically for WordPress publishing. You write in the built-in editor — or sync content from Notion — and Notipo handles the entire publishing pipeline via the WordPress REST API. You never open Gutenberg.

What gets handled automatically on each publish:

• Markdown to HTML
• Image uploads
• Featured image handling or generation
• SEO metadata for Rank Math or Yoast
• Code highlighting
• Categories and tags

The key difference from the REST API approach: Notipo is a complete tool, not a starting point. You don't build the image upload logic, the SEO connector, or the featured image pipeline yourself. It's already there.

Which One Should You Pick?

The right choice depends on what you're optimizing for:

• Want a simpler editor inside WordPress? Use the Classic Editor plugin.
• Want to automate publishing from scripts or CI? Use the REST API directly.
• Want a beautiful Mac writing app? Use iA Writer or Ulysses.
• Want a developer-focused headless setup? Use a static site generator.
• Want the full pipeline automated without building anything? Use Notipo.

The Bottom Line

Gutenberg is optional. WordPress's REST API has been stable for years, and there are mature tools at every level of the stack — from a simple plugin swap to a fully automated publishing pipeline.

If you want to skip Gutenberg entirely and publish from a markdown editor with images, SEO, and featured images handled automatically, try Notipo free.