Skip to content

Try Basic Content Management

In about five minutes, manage a test article in an isolated local browser fixture. Use Node.js 22.12+, Bun 1.4.0, npmjs connectivity and an extracted public source candidate. Start a terminal in that candidate’s root. No private registry or CMS credentials are required.

The fixture consumes the core /studio/basic, /studio/http-provider and /studio/basic.css exports plus the Cloudflare /studio and /studio-handler exports. Package names are listed in the exports reference. This React example shows the actual browser imports used by the fixture:

import '@alneas/appkit-react/styles';
import '@alneas/sitekit/studio/basic.css';
import { BasicStudioApp } from '@alneas/sitekit/studio/basic';
import { createHttpStudioProvider } from '@alneas/sitekit/studio/http-provider';
const provider = createHttpStudioProvider();
export function Admin() {
return <BasicStudioApp provider={provider} collections={[{ id: 'posts', label: 'Posts' }]} />;
}
Terminal window
bun install --frozen-lockfile --ignore-scripts --registry=https://registry.npmjs.org

Expected result: the candidate’s locked public dependencies are installed.

Terminal window
bun scripts/public-consumer-smoke.mjs --preview

Expected result: the script packs both framework packages, installs them in an isolated consumer with npmjs Appkit, checks the actual SQLite schema and HTTP path, then prints Basic Studio preview: http://127.0.0.1:4317/.

Open the printed URL. Select 新規作成, enter a title and slug, and write Markdown in the body field. Leave summary and tags empty. Select 下書き保存.

Expected result: 下書きを保存しました appears. Return to the list and open the article using its title button. The entered values remain.

Select 公開, then reload the page.

Expected result: 公開しました appears before reloading, and the list shows the article’s 公開 state afterwards. This changes the temporary fixture record; it does not publish a website to the Internet.

Stop the terminal process with Ctrl-C. The fixture uses a temporary SQLite database and a local test session; neither is a production authentication setup. You have verified the basic public management flow. Follow the integration guide to connect your own authenticated server and D1 binding.