building-emdash-site

Add the emdash integration to astro.config.mjs with a database and storage adapter, create src/live.config.ts registering the emdashLoader, and write a seed/seed.json defining collections and content. Pages are server-rendered and query content via getEmDashCollection and getEmDashEntry.

Use getEmDashCollection for lists with options like status, limit, cursor, orderBy, and where filters, and getEmDashEntry for a single entry by slug. Always pass the returned cacheHint to Astro.cache.set so published changes invalidate the cache.

Yes, use the @astrojs/cloudflare adapter with d1 and r2 adapters from @emdash-cms/cloudflare, plus a wrangler.jsonc declaring D1 and R2 bindings. Sandboxed plugins require Dynamic Workers, available on paid Cloudflare plans.

Image fields are objects with id, src, and alt properties, not plain URL strings. Pass the whole object to the Image component from emdash/ui, or access featured_image.src explicitly in an img tag.

getEntryTerms requires the database ULID from entry.data.id, not the slug in entry.id, and the taxonomy name must exactly match the seed definition such as "category" rather than "categories". Mismatches fail silently with empty results.

Create a plugin when you need content lifecycle hooks, custom admin pages, API routes, custom Portable Text block types, or reusable services like analytics. Plugins are registered in astro.config.mjs and run in sandboxed Worker isolates.