News, guides, and deep dives on technology, AI, web development, CMS, and SEO — practical, no-fluff reads for people who build and grow things on the web.
EmDash separates who can log in and edit (a user, with one of five roles) from who gets public credit on a piece of content (a byline) — two different systems that only overlap when you want them to. Here's how both actually work.
There's no Settings → Webhooks panel in EmDash — outbound webhooks are something you build as a small sandboxed plugin using a content hook and ctx.http. Here's the real, working pattern, including the specific capability EmDash's own docs name for exactly this use case.
Content, media, schema, revisions, search, and plugin endpoints, all under one consistent response envelope and Bearer-token auth. This is the practical map of EmDash's REST API for scripts, CI pipelines, and admin tooling.
EmDash generates your sitemap, robots.txt, and JSON-LD structured data automatically — but only correctly if one config value is set. Here's the full SEO surface: site-wide defaults, per-page metadata via plugin hooks, and the one setting that silently breaks all of it if skipped.
A working blog — index page, post pages, and a way for editors to publish without touching code — in about the time it takes to define one collection and write two Astro templates.
Adding a field to an existing collection is a database column change, applied live — three ways to do it (admin UI, CLI, REST API), plus the reserved names that will get rejected if you try to use them.
A two-hour maintenance window stretching to eight hours isn't a fluke — it's the predictable result of specific, well-documented mistakes. This covers what actually goes wrong in CMS migrations, beyond just the SEO risks.
Rankings aren't lost because you changed CMS platforms — they're lost because search engines temporarily can't tell your new URLs are the same content as your old, already-trusted ones. Understanding that mechanism is what actually prevents the drop.
301 redirects need to stay live for a minimum of 12 months, not until launch day passes. This is the scannable, platform-agnostic checklist for before, during, and after a CMS migration — the specific items that actually determine whether you keep your rankings.
JSON-LD is the format Google recommends, and it's trivial to generate from a CMS's own content fields — no separate plugin required if your platform lets templates emit it directly. Here's what to actually implement, and how the mechanics differ from a plugin-based approach.
Redirects in EmDash are defined declaratively in the seed file — source, destination, status code, and an optional group label for admin filtering. Here's the actual schema, plus what to do for redirects on a site that's already live.
Scheduling is an opt-in collection feature, not something every content type gets by default — and on Cloudflare Workers specifically, scheduled posts silently won't publish without one extra config step. Here's the complete, accurate picture.