Docs

Rikiki documentation

A tiny Lit Web Components framework for technical presentations. Write a deck as plain HTML, open index.html, give the talk · five years from now too.

Where to start

Pick the entry point that matches what you came for.

New to Rikiki?

Install in a minute, write your first slide, learn the navigation keys.

→ Getting started

Looking up a component?

Every <deck-*> in one page · attributes, slots, tokens, parts.

→ Component library

Want to rebrand?

~100 CSS custom properties · two themes ship, write a third by copy-paste.

→ Theming guide

Need a specific layout?

Patterns for code-on-left, side-by-side, three-column, big-number slides.

→ Recipes

Design principles

Rikiki is opinionated about three things. The rest is up to you.

  1. Zero build for deck authors. A deck is a folder · drop it on any static host, it runs. No Node, no bundler, no node_modules to resurrect.
  2. Web standards over framework lore. Custom Elements, Shadow DOM, ES Modules and CSS Custom Properties have been stable W3C specs since 2018. They will outlive Vite.
  3. Light by default, extensible on demand. The bundle is ~11 KB gzip. The overview mode and the help overlay lazy-load on first use. Anything bigger ships as an opt-in module.

Not the right tool when…

  • You want a builder UI · Rikiki is "write HTML, open in a browser".
  • You need fancy transitions · the framework toggles display, no GPU animation between slides.
  • You want a hosted SaaS · there is none. You host the static files yourself.
  • You want PowerPoint compatibility · Rikiki produces HTML, not .pptx.

For everything else · keep reading.