While doing a general sanity check on the build output, I noticed something that shouldn’t have been there in the first place: raw content directories ending up in dist.

Quesby already relies on computed permalinks for content and on the Eleventy Image pipeline for assets. Copying src/content/posts and src/content/media verbatim into the output was not just redundant, it was wrong. It exposed files that should never be public and went directly against the whole idea of a controlled build pipeline.

v0.2.1 — Stop copying what shouldn’t be copied

The fix was simple and long overdue:

• Removed passthroughCopy for src/content/posts
• Removed passthroughCopy for src/content/media
• Prevented Eleventy from dumping raw content folders into the output
• Enforced a single source of truth:
• permalinks decide URLs
• the image pipeline decides which assets exist and where

Result: cleaner builds, no accidental leaks, no duplicated junk in dist.

While testing that change, I stumbled into another, more subtle issue.

Social cards were broken.

v0.2.2 — Fix Open Graph & Twitter images (properly)

Quesby was generating Open Graph and Twitter Card meta tags using the original image filenames. That worked only as long as you ignored reality: those files don’t exist anymore after Eleventy Image processes them.

So social platforms were pointing to URLs that were never generated.

The fix:

• Process images with Eleventy Image before generating SEO meta tags
• Use the actual output URLs produced by the image pipeline
• Ensure Open Graph and Twitter cards reference real, existing files
• This fixes broken previews when sharing links and aligns SEO metadata with how Quesby actually builds assets.