Skip to content

The layered model ​

How Webhaki code is split across three layered core repos and one repo per website:

  • what goes where
  • how themes are organized
  • how a core change reaches every site
  • the rules that keep merges clean

Related: the System Updater covers how deployed customer sites receive updates.

Core repos and website repos ​

Three core repos in two layers, then one repo per website.

webhaki-cms-core            platform/core, packages, plugins usable by BOTH kinds of site, no front-end theme
   │
   ├──► webhaki-site-core       + site-only plugins + theme "site-base" + starter "site-default"
   │       │                      (business websites, blogs, portfolios, …)
   │       ├──► webhaki-site-companyA     + theme companyA
   │       └──► webhaki-site-…
   │
   └──► webhaki-store-core      + ecommerce plugins + theme "store-base" + starter "default"
           │                      (online stores)
           ├──► webhaki-store-mila        + theme mila
           └──► webhaki-store-…
RepoRoleUpstream (merges from)
webhaki-cms-coreShared CMS for every website—
webhaki-site-coreProduct for business websites, blogs, portfolioswebhaki-cms-core
webhaki-store-coreProduct for online storeswebhaki-cms-core
webhaki-site-<name>One business websitewebhaki-site-core
webhaki-store-<name>One online storewebhaki-store-core

Site-core and store-core are siblings. Neither sits on top of the other, because each has plugins and a base theme the other must not include.

Local folder layout ​

On a developer machine, each layer has its own parent folder under E:\Workspaces. A core sits next to the websites built from it.

E:\Workspaces
├── webhaki-cms\
│   └── webhaki-cms-core\
├── webhaki-site\
│   ├── webhaki-site-core\
│   ├── webhaki-site-companyA\        (one folder per business website)
│   └── webhaki-site-…\
└── webhaki-store\
    ├── webhaki-store-core\
    ├── webhaki-store-mila\
    ├── webhaki-store-…\              (one folder per store)
    └── sync-core.sh
FolderHolds
webhaki-cms\webhaki-cms-core only
webhaki-site\webhaki-site-core and every webhaki-site-<name>
webhaki-store\webhaki-store-core, every webhaki-store-<name>, and the sync script

Keep this layout. sync-core.sh finds websites by scanning the folders next to it, so a website cloned anywhere else is not synced.

Current state (2026-11-08)

  • webhaki-cms-core and webhaki-site-core exist as empty folders: no code, no git, no remotes yet.
  • webhaki-store\ still holds webhaki-store-all and webhaki-store-mila_old. They are cleaned up in the migration plan.

Why not one repo per plugin or theme? ​

Splitting core, packages and each plugin into separate repos (Composer packages or git submodules) means dozens of repos to version, tag and keep compatible, with no benefit while every site runs the same core.

Split a plugin into its own repo only when:

  • outside customers install it one by one, or
  • different sites need different versions of it.

Why not one core with ecommerce turned off? ​

That is simpler, but business websites would still carry ecommerce code, and stores would carry site-only plugins and the site base theme. The layered model keeps each product clean.

Next ​