Skip to content

docs(readme): overhaul README with visual assets, Docker quick-start, and storytelling#5

Merged
electricalgorithm merged 3 commits intomainfrom
docs/readme-overhaul
Feb 24, 2026
Merged

docs(readme): overhaul README with visual assets, Docker quick-start, and storytelling#5
electricalgorithm merged 3 commits intomainfrom
docs/readme-overhaul

Conversation

@electricalgorithm
Copy link
Owner

What this PR does

Rewrites the README to address feedback about the project being too technically descriptive without explaining why ProtoMQ matters. The new README tells a story aimed at developers evaluating the project for the first time.

Changes

New README structure:

  • Hero section with a clearer tagline: "MQTT's simplicity. Protobuf's efficiency. Zig's bare-metal performance."
  • "Why ProtoMQ" section explaining the bandwidth problem and how ProtoMQ solves it
  • Inline SVG payload comparison chart (JSON vs Protobuf for 3 message sizes: 4, 8, and 12 fields)
  • Mermaid architecture diagram showing the broker internals
  • Docker quick-start (docker compose up — one command to try it)
  • Reframed performance table with context
  • Navigation links and FAQ reference

New files:

  • Dockerfile — multi-stage Alpine build with Zig 0.15.2
  • docker-compose.yml — single-service compose for one-command demo
  • assets/payload_comparison.svg — bar chart comparing JSON vs Protobuf payload sizes
  • assets/terminal_demo.svg — terminal mock showing the publish/subscribe workflow
  • .gitignore — added .blog/ for draft social media posts (not in this PR)

Why

The original README listed features but did not explain the problem ProtoMQ solves or why someone should choose it over plain MQTT + JSON. The feedback was that developers on HackerNews/Reddit would scroll past "fast MQ" but stop for "74% bandwidth reduction on IoT sensor data."

Screenshots

The SVG assets render directly on GitHub. Preview by viewing the README on the branch.

Testing

  • Verify SVGs render correctly on GitHub
  • Docker build: docker build -t protomq-test .
  • Mermaid diagram renders in GitHub markdown preview

…lling

Rewrite the README to tell a compelling story about why ProtoMQ exists
and what makes it useful for IoT/edge deployments:

- New tagline emphasizing MQTT + Protobuf + Zig synergy
- Added SVG payload comparison chart (JSON vs Protobuf, 3 scenarios)
- Added SVG terminal demo showing the publish/subscribe workflow
- Mermaid architecture diagram of the broker internals
- Reframed performance benchmarks with context
- Docker quick-start with Dockerfile and docker-compose.yml
- Condensed Service Discovery and Admin Server sections
- Navigation links and FAQ reference
- Added .blog/ to .gitignore for draft social media posts

Signed-off-by: Gyokhan Kochmarla <gokhan.kocmarli@gmail.com>
- Replace Mermaid architecture diagram with 'Under the Hood' section
  highlighting epoll/kqueue, zero deps, runtime schema registry,
  single allocator, comptime tables, and cross-compilation
- Use h3 headers instead of h2 to reduce visual noise
- Remove Resources, License, and standalone Service Discovery sections
- Condense Admin Server to a one-line mention with link to FEATURES.md
- Rewrite 'Why ProtoMQ' in a more conversational tone
- Move detailed Service Discovery and Admin Server docs to FEATURES.md

Signed-off-by: Gyokhan Kochmarla <gokhan.kocmarli@gmail.com>
…-to-Protobuf

The broker only accepts Protobuf payloads on the wire. The CLI has a
--json convenience flag that encodes to Protobuf client-side before
publishing, but the protocol itself is Protobuf-only. The previous
wording incorrectly implied the broker does JSON-to-Protobuf conversion.

Signed-off-by: Gyokhan Kochmarla <gokhan.kocmarli@gmail.com>
@electricalgorithm electricalgorithm merged commit 6967597 into main Feb 24, 2026
1 check passed
@electricalgorithm electricalgorithm deleted the docs/readme-overhaul branch February 24, 2026 08:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant