Editor Experience

user: anonymous

{
  "path": "/blog/editor-experience",
  "attrs": {
    "title": "Editor Experience",
    "date": "2024-10-22",
    "layout": "BlogPostLayout",
    "splash": {
      "image": "/images/red-white-flower.jpg"
    }
  },
  "md": "# Editor Experience\n\nEditor Experience (EX) is a crucial aspect of web publishing.\n\nContent **editing** tools with reusable **themes** enable creators to publish professional-looking websites without the need for custom development. This is the long tail of web publishing dominated by [WordPress](https://wordpress.com/theme/twentytwentyfour) and platforms like [Wix](https://wordpress.com/theme/twentytwentyfour) and [Shopify](https://themes.shopify.com/).\n\nWeb frameworks like [Next.js](https://nextjs.org/) start with developers first. Even when they are integrated with a [CMS](https://www.sanity.io/) and deployed to an edge host like [Cloudflare Pages](https://pages.cloudflare.com/), the dependency on developers remains.\n\n> This puts modern web frameworks out of reach for the typical creator.\n\nAn ideal web publishing architecture incorporates three key elements:\n\n1. A responsive **theme** that ensures content looks great on all devices.\n2. A user-friendly content **editor** with built-in theme awareness.\n3. Fast, reliable web **hosting** for the rendered content.\n\nPublishers need efficient content creation, updates, and optimal presentation across the web. If you're building tools for web publishing, don't forget the editor experience.\n\n---\ncontext: https://x.com/jldec/status/1848681247154835887\n\n![Screenshot of Cody writing in VS Code](/images/writing-with-cody.webp)",
  "html": "<h1>Editor Experience</h1>\n<p>Editor Experience (EX) is a crucial aspect of web publishing.</p>\n<p>Content <strong>editing</strong> tools with reusable <strong>themes</strong> enable creators to publish professional-looking websites without the need for custom development. This is the long tail of web publishing dominated by <a href=\"https://wordpress.com/theme/twentytwentyfour\">WordPress</a> and platforms like <a href=\"https://wordpress.com/theme/twentytwentyfour\">Wix</a> and <a href=\"https://themes.shopify.com/\">Shopify</a>.</p>\n<p>Web frameworks like <a href=\"https://nextjs.org/\">Next.js</a> start with developers first. Even when they are integrated with a <a href=\"https://www.sanity.io/\">CMS</a> and deployed to an edge host like <a href=\"https://pages.cloudflare.com/\">Cloudflare Pages</a>, the dependency on developers remains.</p>\n<blockquote>\n<p>This puts modern web frameworks out of reach for the typical creator.</p>\n</blockquote>\n<p>An ideal web publishing architecture incorporates three key elements:</p>\n<ol>\n<li>A responsive <strong>theme</strong> that ensures content looks great on all devices.</li>\n<li>A user-friendly content <strong>editor</strong> with built-in theme awareness.</li>\n<li>Fast, reliable web <strong>hosting</strong> for the rendered content.</li>\n</ol>\n<p>Publishers need efficient content creation, updates, and optimal presentation across the web. If you're building tools for web publishing, don't forget the editor experience.</p>\n<hr>\n<p>context: <a href=\"https://x.com/jldec/status/1848681247154835887\">https://x.com/jldec/status/1848681247154835887</a></p>\n<p><img src=\"/images/writing-with-cody.webp\" alt=\"Screenshot of Cody writing in VS Code\"></p>\n"
}