Consumer documentation for @elek-io/core. These docs ship inside the published package, so a developer or AI coding agent always has version-matched references for the exact Core version in use, with no network lookup.
They cover how to use Core: the data model, the public API, the local REST API, the CLI and the Astro integration. They do not cover how to develop Core itself, that lives in the repository’s contributing/ folder and is not published.
New to elek.io Core? Read concepts.md for the data model, then usage.md for a runnable walkthrough. Reach for the reference docs below as needed.
Start here
features.md- capability overview for evaluating Core, including current limitationsconcepts.md- the data model: Projects, Collections, Components, Entries, Values, Assets and Releasesusage.md- programmatic usage, the local API, the CLI and the Astro integration
Content modeling
fields.md- the field type reference and how Entry Values are storedschema-changes.md- what happens to existing content when you edit field definitionsreferences.md- typed pointers between content and how Core keeps them intactmarkdown-content.md- storing and rendering richmarkdowncontent as an mdast treeasset-management.md- the two-file Asset model, creating, reading and deleting Assets
Reading and shipping content
local-api.md- the read-only REST API: endpoints, pagination and the OpenAPI docsapi-clients.md- generating typed JS/TS clients and standalone TypeScript typesexport.md- exporting Projects to plain JSONreleases.md- tagged, versioned snapshots and promotingdraftintomainprovisioning.md- provisioning Projects into build environments (CI/CD and local builds), whatever runs next
Platform
git-and-sync.md- the branch model, commits and synchronizing with a remotestorage-layout.md- where Projects and their files live on diskerror-handling.md-CoreErrorand how to catch failures