An ode to those who love the craft, an ode to the old internet, an ode to a time before numbers and figures dominated writing, an ode to a time where readers remembered their favourite writers, and an ode to the hope that all of it is still present, somewhere.

Ode is for writers who want to publish in an aesthetically pleasing website, who ignore the bells and whistles of the modern internet, and who want to create a better experience for their readers. It is opinionated, minimal, and easy to use, guided by its own ethos.

This project is backed by the Dimwit Pledge.

The theme/idea comes directly from journal.coffee which was my Wordpress-based website where I've written prose for years now. Its styling and design evolved with significant manual effort over the years. Wordpress was great but it became quite bloated over the years and I wanted a lightweight, faster place to write in. Plus, the reading mode and ease of markdown publishing has been on my mind for ages.

Rest assured, as of the very first release, I am using ode too!

You can find a live demo of the app here.

• README.md: Overview, features, and getting started
• CONFIGURATION.md: Full config.yaml reference
• ETHOS.md: Core principles and philosophy behind Ode
• WRITING.md: Content repository, auto-deployment, and GitHub Actions
• THEMING.md: Theme presets, customization, local fonts, and visual examples
• CHANGELOG.md: Version history and release notes
• REFERENCES.md: Credits and inspirations

This is my favourite feature, personally.

• Markdown-based content: Write your pieces and pages in simple markdown files with front matter; push to publish
• Reader mode: Beautiful paginated reading experience with keyboard navigation (arrow keys)
  • Checkpointing: URLs for the reader mode track piece and position so even if you publish more and the collection gets updated, a bookmarked link will always send the reader to the right place in the "book"
  • Gestures: The Reader supports both swipe and trackpad gestures
• Collections/Volumes: Automatically organize your pieces into themed collections for curated reading
• Dark/Light mode: Automatic theme switching with user preference persistence with a nice lamp reminiscent of olden times
• Theming: 10 built-in themes with full customization support via config.yaml
• RSS feed: Auto-generated RSS feed with full content for your readers to use
• Body of Work: Chronological archive of all your pieces, organized by month/year; order is up to you
• Random piece: Let readers discover content serendipitously and the continue reading
• Build-time generation: Static pages and indexes generated during build for optimal performance
• Fully customizable: All UI labels, site metadata, and page order configurable via config.yaml
• No tracking, no analytics, no boxes, no search, no media: Just writing and reading

If you want to self-host, use the public Docker image. Create a directory with your content:

my-site/
  public/
    config.yaml
    content/
      intro.md
      pieces/
      pages/
  docker-compose.yml

Create a docker-compose.yml:

services:
  ode:
    image: ghcr.io/dimwitlabs/ode:latest
    ports:
      - "8080:4173"
    restart: unless-stopped
    volumes:
      - /path/to/your/public:/app/public

Run:

docker compose up -d

Your site will be available at http://localhost:8080. Restart the container to rebuild after content changes:

docker compose restart

Once you have your Fork or branch ready, you can deploy the app but the reader position Permalinks as well as the Body of Work links will fail. This is due to SPA handling of paths and (from my understanding) how React works. But this can be fixed.

You can directly to Vercel below. vercel.json already has the fixes Vercel will need.

https://github.com/DeepanshKhurana/ode/blob/46873b31df3d4b02bbb375d4389173a1b6ac3f6b/vercel.json#L1-L12

If you are like me, you probably have your own server where you will need to handle SPA routing. If you are using nginx, configuration templates are provided in the nginx/ directory.

If you are coming from WordPress, you can use the awesome lonekorean/wordpress-export-to-markdown to get your content in markdown format. It will mostly be plug and play with this version of Ode.

Create markdown files in public/content/pieces/ with front matter:

---
title: "Your Piece Title"
slug: "your-piece-slug"
date: 2025-11-23
categories:
  - essays
  - fiction
---

Write to your heart's desire.

Create markdown files in public/content/pages/ with front matter:

---
title: "About"
slug: "about"
date: 2021-06-14
---

Tell everyone everything!

Ode comes with 10 built-in themes that you can use and customize. Switch between presets, override colors and fonts, or build your own theme from scratch.

Edit public/config.yaml to customize your site. You can handle quite a few things here:

• Change your site's name, author, and vibe at the top.
• Tweak button text and messages to sound how you want.
• Pick which pages show up first in the menu.
• Hide any pages or pieces you don't want public.
• Choose your not found (404) page (yes, a markdown file!).
• Set how collections are sorted—oldest first or newest first.
• Set how the Body of Work page sorts your history.
• Rename the light/dark mode switches.
• Edit the "words wasted" summary to your liking.
• Control the number of entries in the RSS feed.
• Select theme presets and control overrides.

https://github.com/DeepanshKhurana/ode/blob/fcc6d2b7b0b825e07cc07e94a43596e716dd8b79/public/config.yaml#L1-L49

npm install

npm run dev

Runs the app in development mode at http://localhost:5173

npm run build

This will:

1. Index all pieces from public/content/pieces/
2. Index all pages from public/content/pages/
3. Paginate pieces for reader mode
4. Calculate word/piece statistics
5. Generate RSS feed
6. Generate body of work archive
7. Build the production bundle

npm run preview

Run individual build scripts:

• npm run build:pieces - Index pieces
• npm run build:pages - Index pages
• npm run build:paginate - Paginate pieces
• npm run build:stats - Calculate statistics
• npm run build:rss - Generate RSS feed
• npm run build:sitemap - Generate Sitemap

• React 19 with React Router for client-side navigation
• Vite for blazing fast development and optimized builds
• SCSS for styling with a clean, minimal design
• TypeScript build scripts for content indexing and generation
• ReactMarkdown for rendering markdown content
• Front Matter for parsing markdown metadata

MIT

You are free to use this, break it, customise it. If you have any idea the community will benefit from, raise a PR or an Issue.