Marmite now supports workspaces - a way to manage multiple independent sites from a single project directory and build them all with one command.
\nA workspace is a directory containing multiple marmite sites, identified by a marmite-workspace.yaml file at the root:
myproject/\n blog/\n content/\n marmite.yaml\n photos/\n content/\n marmite.yaml\n marmite-workspace.yaml\nEach subfolder (blog/, photos/) is a regular marmite site that can also be built independently with marmite myproject/blog output.
Create a marmite-workspace.yaml at the project root:
# List of sites in build order (required) \nsites : \n - name : blog \n - name : photos \n\n# Which site serves at "/" (default: first in list) \ndefault_site : blog \n\n# If true, root "/" gets a redirect instead of the default site content \nredirect : false \n\n# Shared configuration defaults inherited by all sites \ndefaults : \n language : en \n pagination : 10 \n enable_search : true \n\n# Separator for cross-site references (default: "::") \nseparator : "::" Each entry in sites accepts:
name (required) - the directory nameoutput_path (optional) - custom output subdirectory name, defaults to the directory namesites : \n - name : blog \n output_path : b # renders to output/b/ instead of output/blog/ \n - name : photos $ marmite myproject output -v\nWorkspace mode: 2 site(s) detected\nBuilding site 'blog' -> output\nBuilding site 'photos' -> output/photos\nWorkspace generated at: output/\nThe default site renders directly at the output root. Other sites render to subdirectories.
\nBy default, the first site (or the one specified by default_site) renders at the root of the output directory. Other sites render as subdirectories.
With redirect: true, all sites render to their own subdirectories and the root index.html is a meta-refresh redirect to the default site:
default_site : blog \nredirect : true This generates output/blog/, output/photos/, and an output/index.html that redirects to /blog/.
The defaults section in marmite-workspace.yaml provides base configuration values for all sites. Each site's own marmite.yaml overrides these defaults. Fields not specified in the site config inherit from the workspace defaults.
# marmite-workspace.yaml \ndefaults : \n language : en \n pagination : 10 \n enable_search : true \n\n# blog/marmite.yaml - overrides name but inherits everything else \nname : My Blog \ntagline : A personal blog CLI-passed configuration flags (like --pagination 5) apply only to the workspace-level defaults, not to values explicitly set in individual site configs.
Sites in a workspace can link to each other using the :: separator (configurable via separator in the workspace config):
Check out the [photo gallery](photos::gallery.html).This renders as a link to /photos/gallery.html.
This renders as an image source pointing to /photos/media/sunset.jpg.
Content-gathering shortcodes accept a site parameter to pull content from other sites in the workspace:
<!-- .posts site="photos" --> \n<!-- .tags site="blog,photos" --> \n<!-- .authors site="all" --> \n<!-- .pages site="photos" --> \n<!-- .streams site="photos" --> \n<!-- .series site="blog" --> The site parameter accepts:
site="photos" - content from that site onlysite="blog,photos" - merged content from listed sitesall: site="all" - content from every site in the workspacePosts and pages returned from other sites have their slugs prefixed with the site's output path, so links generated by url_for point to the correct location (e.g., /photos/first-photo.html).
The card shortcode also supports cross-site slugs using the :: separator or the site parameter:
<!-- .card slug="photos::first-photo" --> \n<!-- .card slug="first-photo" site="photos" --> When no site parameter is provided, shortcodes behave exactly as in single-site mode - showing only the current site's content.
Most commands work with workspaces:
\nUse --site to specify which site to create content in:
$ marmite myproject --new "My Post" --site blog\nWithout --site, workspace mode will prompt you to specify the target site.
Aggregates URLs from all sites:
\n$ marmite myproject --show-urls\nOutput is grouped by site name with prefixed paths.
\nLists shortcodes from all sites:
\n$ marmite myproject --shortcodes\nTheme commands (--init-templates, --start-theme, --set-theme) and --init-site are not supported in workspace mode. Run them on individual sites instead:
$ marmite myproject/blog --set-theme my-theme\nWorkspace watch mode monitors all site directories and the workspace config file. Any change triggers a full workspace rebuild with live reload:
\n$ marmite myproject output --serve --watch\nThe built-in server serves the combined output directory, so localhost:8000/ shows the default site and localhost:8000/photos/ shows the photos site.
A sites.json file is generated at the output root listing all sites:
[\n {"name" : "blog" , "path" : "/blog/" },\n {"name" : "photos" , "path" : "/photos/" }\n]Each site gets its own complete output with static assets, media, feeds, sitemap, and search index.
\nEach subfolder remains a fully independent marmite site. You can always build a single site directly:
\n$ marmite myproject/blog output/blog\nThe workspace feature is purely additive - existing single-site functionality is completely unaffected.
\n\n\n\n\n", "summary": "\"Build and manage multiple marmite sites from a single workspace with cross-site references, shared configuration, and unified builds.\"", "date_published": "2026-07-03T15:00:00-00:00", "image": "media/workspace-multi-site-support.banner.jpg", "authors": [ { "name": "Bruno Rocha", "url": "https://go.rocha.social/@bruno", "avatar": "https://github.com/rochacbruno.png" } ], "tags": [ "docs", "workspace", "multi-site", "features" ], "language": "en" } ] }Please consider giving a ☆ on Marmite Github repository, that helps a lot!
\n