SiteKit
SiteKit
Section titled “SiteKit”Elevator Pitch
Section titled “Elevator Pitch”Astro developers use this framework to build static sites and basic content management around explicit content and hosting contracts.
Why & Value Proposition
Section titled “Why & Value Proposition”Configure an independent site using explicit content sources and standard hosting contracts. Build from one pinned publication so content, media and generated pages share a revision. Add public editing and storage adapters where needed; domain templates and advanced Studio integrations remain separate extensions.
Key Highlights
Section titled “Key Highlights”- Validated site configuration with inline, file or HTTP content sources.
- Revision and image integrity checks before static rendering.
- Basic Markdown management with list/search, draft saving and publishing.
- Optional Cloudflare projection, analytics, commerce and editing adapters.
Quickstart
Section titled “Quickstart”Use Node.js 24+. Bun 1.4.0 is used for repository development and the commands below; installed consumers may use npm, pnpm or Yarn. Initial npm publication of this framework is pending; start with the locally packed public core artifact from a verified source candidate. Appkit 0.2.0 is available from npmjs when using the optional React screen.
bun add ./alneas-sitekit-0.1.0.tgz astro@^7.3.3Save as example.ts, then run bun example.ts:
import { defineSite } from '@alneas/sitekit/config';
const site = defineSite({ id: 'example', revision: 1, content: { snapshot: { siteId: 'example', revision: 1, posts: [], assets: [] } },});console.log(site.id, site.revision); // example 1Next Steps
Section titled “Next Steps”-
Contributing and local checks and maintainer release procedure
-
Error codes and corrective actions and configuration JSON Schema
-
Consumer AI guidance;
llms-full.txtcontains the generated full public guide compilation.
SiteKit is the new product name. These guides describe the unpublished 0.1.0 source candidates. Portal links are navigation targets and do not establish that the portal serves this candidate revision. Keep candidate APIs out of the default released portal until each corresponding package is confirmed published; see the documentation handoff.