Hello
My first note.
Open source · Apache-2.0 · TypeScript
Build a static site from Markdown or an Obsidian vault, while keeping routes, components, and styles in an application you own.
Create a project
npx create-riebeckite
Team notes / Development
Set up a development environment for new team members.
Keep the Node.js version, required environment variables, and local startup steps in one place. Update this page when they change.
See how content is organized →A framework, not a theme
Start from Markdown, then choose the navigation, discovery tools, theme, and routes that make the site yours. These are the same surfaces available to a generated project.
Team Handbook
OnboardingDevelopmentMeeting notesDevelopment / Releases
Review the changes, test in staging, and complete the checks after publishing.
Markdown → Web
The same Riebeckite pipeline that builds a site parses frontmatter, Markdown, and Obsidian WikiLinks here.
Markdown source
---
title: Hello
---
## Hello
My **first** note.
[Getting started](/docs/getting-started)Published page
My first note.
npm packages
Install a package, register it in the configuration, and decide where its components belong in your routes.
npm install @riebeckite/plugin-search
import { search } from "@riebeckite/plugin-search";
export default defineConfig({
plugins: [search()],
});
This example adds site search. Plugins can also add transforms, renderers, standalone pages, browser behavior, endpoints, SEO, and diagnostics. Themes supply tokens and styles without deciding the application structure.
Choose by outcome
Start with a site need rather than a package name. Each guide covers setup and the pieces you add to your routes.
A project you can read
Generated projects use ordinary files, so each change has an obvious home. Writing stays separate from the interface around it, while one configuration file describes the site you are assembling.
content/ so notes can grow and move without changing the application.app/routes/ and app/components/ for the pages and UI your readers use.riebeckite.config.ts.app/
routes/
components/
content/
riebeckite.config.tsFrom draft to live site
dist/.Working references
Compare official themes, see plugins running together, or read how to customize the site around your content.
Build output is written to dist/. The deployment guide covers local Cloudflare Workers publishing, GitHub Actions, and separate content repositories.