dropbits Documentation

Packs & capabilities

Optional features ship as packs on disk. Brochure boots do not autoload pack PHP — you install then enable a capability when you need it.

From Admin (site owners)

  1. Open Admin → Site.
  2. Scroll to Packs & capabilities.
  3. For a pack on disk but not installed: Install & enable.
  4. For an installed capability that is off: Enable (or disable when you want it off).

Quiet chips in the edit session can point at the same “available” list. Dismiss per capability+version; they reappear when the version changes. Rediscover anytime under Site.

What enable does

Activation runs the pack recipe (entities, admin pages, grants, defaults) with collision detection — nothing silently overwrites. Recipe work goes through Toolbox tools (install_pack, enable_capability, disable_capability).

Operators (CLI)

Site builders can also use:

./bin/site pack-install <name>
./bin/site enable <capability>
./bin/site disable <capability>

Full install/deploy detail: Packs (CLI + Admin).

Not in v8 Admin

There is no catalog-packages browse hub and no AdminHub “install from card grid.” Discover packs from Site (and edit-session hints), not a separate package store UI.

See also