What it does for you
Run new-site.sh: it asks (native Windows dialogs under Git Bash, terminal dialogs elsewhere) for the store name, what it sells, a palette, the features, and demo size, then zips a complete store. Extract the zip anywhere, run start.sh, answer port / admin / URL, and it boots the containers, installs WordPress and WooCommerce, activates everything, and seeds the demo.
Every feature
- Wizard questionsName, tagline, address, phone, vertical, palette (dark or light), features, product count.
- ScriptableFSB_* environment variables answer every question for unattended builds; ST_* for start.sh.
- Self-contained zipdocker-compose.yml with a bind mount per bundled plugin, the theme, the seed, README-SETUP.md.
- start.shPort, admin credentials, site URL, auction length; then WordPress + WooCommerce (+ auction engine) install, activation, seed.
Setup
- bash factorize-site-builder/new-site.sh (needs Python; Docker only where you run start.sh). Each site becomes its own folder next to the suite (the default output is the repo root).
- Extract <slug>-site.zip, ./start.sh (default port 8650).
Configuration
| key | default | effect |
|---|---|---|
FSB_NAME / FSB_VERTICAL / FSB_PALETTE / FSB_FEATURES / FSB_PRODUCTS | asked | pre-answer the wizard |
ST_PORT / ST_ADMIN_USER / ST_ADMIN_PASS / ST_URL | asked | pre-answer the installer |
The Setup plugin does the same job inside wp-admin for an existing WordPress; the builder is for a brand-new stack.
Tutorial
- Build a clothing storeFSB_NAME=clothing FSB_VERTICAL=clothing FSB_PALETTE=linen FSB_FEATURES=”essentials catalog analytics storefront perks portal watch vision” bash new-site.sh — the verified run produced the light boutique that became InstaAttire (its own folder, port 8610).
Questions
Docker on Windows?
Docker Desktop; the zip runs from any shared drive.
Roadmap
- Ship the Setup plugin inside the zip and let it drive the seed