Modules & packages
Jasefly splits the platform into two GitHub repositories — clone both if you want the full stack:
- Core — github.com/iia3uk/jasefly: host, Platform SDK, Builder, MCP, and ~15 core/host modules (System, Users, Media, SEO, Scheduler, Module Manager, Access, …). Cloning
mainalone is enough to run the platform. - Domain packages — github.com/iia3uk/Jasefly-Modules: 15 first-party modules (blog, projects, orders, payments, forms, analytics, support, translate, …). They are not inside Core by design.
Packages boot through bootPlatform(PlatformContext) and ship as ZIP via Module Hub. There is a Package Manager — not a public Module Marketplace store.
What a module can do
Real registration surfaces — no invented APIs.
- Core repo — ~15 host modules + SDK. Clone https://github.com/iia3uk/jasefly
- Jasefly-Modules — 15 domain packages. Clone https://github.com/iia3uk/Jasefly-Modules
- bootPlatform — Preferred package entry on AbstractPackageModule — routes, capabilities, providers.
- Access providers — Register AccessProvider implementations; content gates stay fail-closed.
- Builder blocks — builder()->registerBlockMeta(...) and FE builder.registerWidget.
- Quarantine — Failed ZIP install/update can isolate the package instead of crashing the host.
Clone the right repository
Core = host. Modules = 15 domain packages. Absence of blog/orders in Core is intentional.