Meetball Handbook

Quick Start

Everything you need to start contributing to Meetball - from this handbook to our other projects.

Last Updated: May 25, 2026

Our Development Philosophy

We're building in the open, taking inspiration from organizations like FUTO, Basecamp, and Gumroad - focusing on user control, simplicity, and independence over traditional growth-at-all-costs models.

We Build with AI

Meetball is an AI-native startup. That doesn't just mean we build AI features. We use AI throughout everything we do: to move faster, improve the quality of our work, and stay in alignment. But we're human-centered at the core. AI is an enabler and a convenience multiplier, not a replacement. Until we're confident about something, there's always a human in the loop. Being AI-native is a journey.

Prerequisites

  • Git
  • Zola ≥ 0.15.0
  • A text editor (VS Code, Helix, Vim, whatever you love)
  • Nix (optional, but makes setup easier)

Get This Handbook Running Locally

Open Claude Code in the handbook directory, describe what you want to change, and Claude handles the edits, checks, and pushes directly to GitHub. It automatically picks up our project guidelines covering tone, design conventions, and how we write, so changes stay consistent with everything we've already built. Same goes for our other projects.

With Nix

git clone https://github.com/himeetball/handbook.git
cd handbook
nix-shell  # This installs Zola automatically
zola serve

Manual Zola install

First, install Zola on your system, then:

git clone https://github.com/himeetball/handbook.git
cd handbook
zola serve

Visit http://127.0.0.1:1111/ and Bob's your uncle - you're looking at the handbook!

Our Projects

[This section will be expanded with specific project information]

All our projects are currently hosted on GitHub. Each repository has its own contribution guidelines and setup instructions.

Making Your First Contribution

Step 1: Create a new branch

git checkout -b my-awesome-contribution

Step 2: Add or edit content

The handbook structure:

  • content/docs/ - Documentation pages
  • content/blog/ - Blog posts and updates
  • static/ - Images and other assets

Step 3: Write in Markdown

All content is written in Markdown. Create a new file:

# For docs
touch content/docs/my-new-guide.md

# For blog posts
touch content/blog/2025-07-my-post.md

Step 4: Preview your changes

zola serve

The site auto-reloads when you save files. Pretty neat, right?

Step 5: Submit your contribution

git add .
git commit -m "Add guide for [whatever you added]"
git push origin my-awesome-contribution

Then open a pull request on GitHub and we'll review it!

Writing Tips

  • Use clear, friendly language
  • Add code examples where helpful
  • Include Mermaid diagrams for flows and architecture
  • Insert and/or screenshots for UI-related content
  • Check out existing pages for style reference
Edit this page Report an issue
Manifesto →