If you have no blog yet and Astro is acceptable as the host framework, start here. npx create-pilcrow my-blog scaffolds a complete Astro project with the typesetting layer, image pipeline, OG cards, RSS, and sitemap pre-wired. The shape of the repository assumes you want what pilcrow.page itself ships, so the cost of getting started is roughly zero and the cost of disagreeing later is rewriting some Astro plumbing. Choose this when you are starting fresh and the editorial defaults are close enough to what you want that arguing with them is not worth your evening.
If you already run an Eleventy site, or you prefer the 11ty model of small composable transforms over a framework that owns your routing, install pilcrow-eleventy. It registers as an ordinary plugin, opens one headless Chromium for the build, and replaces the inner paragraphs of any page that wraps its content in <div class="post-body">. Pages without that wrapper pass through untouched, so you can opt content in one layout at a time. Choose this when your site already exists and you want typesetting added to it rather than around it.
If your blog lives inside a Next.js application alongside product surfaces, install pilcrow-nextjs as a rehype plugin in the @next/mdx pipeline. The work happens at next build time only; serverless and edge runtimes are not viable hosts for Playwright. The output is static HTML baked into the compiled MDX, which means nothing ships to the reader at runtime on the typesetter's account. Choose this when Next.js is already paying its way for the rest of the site and you would rather add a build step than maintain a separate publishing tool.