Architecture
Jasefly is structured as a platform stack, not a single monolith admin panel. Packages talk to the host through the Platform SDK. Content editing is a surface; the framework is the product.
Two repos: Core holds ~15 host modules + SDK; Jasefly-Modules holds the 15 domain packages. Cloning only Core is intentional — domains are external.
- Install — Drop the install ZIP (or clone Core + build), configure .env / DB, run migrations.
- Compose — Use Builder widgets and host modules; register capabilities via Platform SDK.
- Extend — Ship domain packages from Jasefly-Modules (or your own ZIP) — bootPlatform + Hub install.
- Operate — Update via SiteUpdater, MCP for content/release, quarantine protects a bad package.
Need domain package source?
15 first-party modules live in Jasefly-Modules — not inside Core.