Where Does Middleman Store Config and Build Output?
Middleman reads config.rb at each site root for helpers and extensions, building static output into build/ with .gitignore usually excluding it.
Last updated
Middleman centers each site on config.rb with helpers, extensions, and asset settings in Ruby. Source pages live beside it while the build command renders everything into build/. That output never needs versioning.
Deployment reads from build only, so source stays private naturally. Helpers defined in config.rb shape every page consistently. Copying a site means source plus config, with gems reinstalling from the bundle.
Where Middleman stores this, by platform
config.rb + build/
Helpers plus extensions config versioned per site. Build output beside it deploys directly. Ignore build in git.
config.rb + build/
Same repo relative layout on Mac installs. Bundle install restores gems on new machines. Output regenerates cleanly.
config.rb + build\
Windows projects share the identical structure. Ruby setup varies but site files match. Delete build to force rebuilds.
Frequently asked questions
Where is Middleman configured?
Edit config.rb for helpers, extensions, and build settings since it controls generation. Version it with the site for reproducible builds. Environment blocks separate dev from build behavior.
How do I clean Middleman output?
Delete the build folder and rerun the build command to regenerate from source. Stale outputs cause confusing deploys. Most repos gitignore build entirely.
Notice an outdated path? Let us know.