Multi-Site Deployment

Agencies and teams use BF Blocks' export/import system to maintain a standard block library and deploy it consistently across client sites.

Recommended Agency Workflow

1. Maintain a master library site. A private WordPress staging install where your agency's block library lives. All new blocks are built here first.
2. Export the full library. Run wp bf-blocks export --all --output=./blocks/ from the master site.
3. Commit block JSON to Git. The ./blocks/ directory lives in your agency's starter theme or project scaffold.
4. Deploy to client site. On a new client site, run wp bf-blocks import ./blocks/ --force during the site setup script.
5. Customise per client. Modify, rename, or extend individual blocks on the client site without affecting the master library.

Deployment Script Example

#!/usr/bin/env bash
# deploy-blocks.sh — run after WP install

WP_PATH="/var/www/client-site"
BLOCKS_PATH="./blocks"

echo "Installing BF Blocks plugin..."
wp plugin install bf-blocks.zip --activate --path="$WP_PATH"

echo "Activating licence..."
wp bf-blocks licence activate "$BF_BLOCKS_LICENCE_KEY" --path="$WP_PATH"

echo "Importing block library..."
wp bf-blocks import "$BLOCKS_PATH" --force --path="$WP_PATH"

echo "Done. Blocks imported:"
wp bf-blocks list --path="$WP_PATH"

Licence Requirements

Each client site requires its own active BF Blocks licence. If you're managing 5+ client sites, the Agency plan (up to 25 sites) is the most cost-effective option.

Local environments (localhost, *.local, *.test) do not consume a licence slot — safe to use during development without counting against your limit.