How-to guides

Recipes for the things Baseline does not do for you, and a few guides on grafting it onto setups that already exist.

Index

• Customise the assets pipeline
• Deploy under a subpath
• Image transform
• Multilingual index
• Build scripts and cleanup
• Translate UI strings
• Deployment checks
• Persist the build cache on your host

Prefer a guided start? See the simple Baseline site tutorial.

Eleventy behaviours that catch people out

None of these is Baseline's, and all of them have been hit by somebody following Baseline's own instructions. Each is written up on the page where it applies; this is the list to scan when you have the symptom but not the page.

• A permalink function reads undefined from eleventyComputed, warns, and the template's permalink quietly wins. The warning names the wrong file. → Content organisation
• A .11tydata.js silently beats a sibling .11tydata.json. Edits to the JSON do nothing. → Project structure
• Redefining a filter or shortcode warns only under DEBUG=Eleventy:UserConfig, while redefining a collection throws. → Plugin entrypoint
• Your config finishes before any plugin body runs, so a name you register directly is in place before Baseline's, wherever in the file you wrote it. → Plugin entrypoint
• CSS and JS asset sources are not templates. Template syntax in them ships to the browser as typed. → Customise the assets pipeline
• @import-glob only resolves in the CSS entry file, and is ignored without error in anything imported from it. → Customise the assets pipeline