[contrib] tabi

I tried Jekyll with al-folio. Tried Material for MkDocs.

Both claimed “ease of use.” but both didn’t deliver.

Setup fought me. Maintenance fought me. Codebases sprawled everywhere. I’d spend hours tinkering with configs when I should’ve been writing.

Personal website should be place to share. Not place to waste time.

What Changed

Found tabi. Zola-based. Static site generator in Rust.

Simple architecture. Packed with what I needed. Nothing I didn’t.

Respects readers by default. Fast loads. Accessible navigation. Zero tracking. No bloat.

You’re looking at it now.

Someone else opened the issue. I picked it up.

Why was it easy?

Oscar documents everything. Builds respectful environment for contributors. Codebase makes sense. You know where things are.

Not intimidating like other static site generators. Simple. Works. Embraces community.

This also leads to me opening a discussion to initiate a community around tabi ecosystem.

Fast site that loads in milliseconds. Accessible by default. Privacy-respecting. One config file controls everything.

Write. Publish. Done.

No fighting dependency hell. No debugging mysterious build failures. No maintenance overhead.

Start your repository by using tabi-start template.

Only need on command to see it running:

zola serve

Check my implementation: github.com/leekaize/www

Your move: Clone it. Run it. See if it fits.

Tools should get out of your way. Tabi does.