Platform features
Jasefly is an AI-first dual-runtime platform. The admin CMS is one product surface on top of PHP/Node core, React frontend, Platform SDK, Access, Builder, MCP, and ZIP module runtime. Below are shipped capabilities — not a wishlist.
Repos: Core (~15 host modules) + domain packages (15 modules on Jasefly-Modules).
What ships today
Honest inventory of the platform stack.
- Visual Builder — Compose public pages from widgets; layouts stored as layout_json and rendered by LayoutRenderer.
- ZIP Module Runtime — Upload → inspect → install/update packages with rollback metadata and quarantine on hard failure.
- Two GitHub repos — Core host + Jasefly-Modules (15 domain packages). Clone both for full sources.
- Platform SDK — bootPlatform(PlatformContext) — access, events, HTTP, builder, capabilities, content, and more.
- Universal Access Layer — One access service for content rules and admin capabilities — fail-closed providers.
- Capabilities & ACL — registerCapability / canCapability for admin UI and /admin APIs — deny wins on overrides.
- MCP Server — cms_* tools for site map, content, modules, diagnostics, and managed releases from the agent.
- Safe Updates — SiteUpdater applies update ZIPs and cleans stale frontend assets on shared hosting.
- Quarantine — Broken ZIP modules isolate so a bad package does not take down the whole API.
- Shared Hosting Install — Prebuilt frontend + PHP API on ordinary Apache/MySQL hosting — install ZIP on GitHub releases.
- Self-contained Packages — Domain packages carry PHP + FE assets; sources live in Jasefly-Modules, not Core.
- AI-ready Workflow — MCP + local clone lets agents work on code and content with controlled tools — not shell root.
Not claimed as shipped: a public Module Marketplace storefront. ZIP Package Manager exists; a marketplace is exploratory roadmap only.
Start building on the framework
Read the docs, clone Core, and open the 15 domain packages when you need them.