Sure, keep it simple: a stateless REST API with a Postgres or SQLite backend, containerized in Docker, behind a load balancer. Use a message queue like RabbitMQ for heavy write traffic, so the API can stay fast. Keep the code in a single repo, split into clear layers: controller, service, repository. Add health checks, rate limiting, and basic auth for admin endpoints. That way, if everyone hits it, the queue buffers the load and you can scale the API replicas horizontally. If you want to keep the codebase pure, stick to Go or Rust—both compile to static binaries and run well in containers.

Add a lightweight SPA—React or Vue if you must, but keep the bundle <50 KB. Use WebSocket or long‑polling to stream the queue state from the backend. Show a simple table of pending suggestions with approve/reject buttons. For fun, sprinkle a tiny SVG badge that flips when an approval is made. Just make sure the WebSocket endpoint is behind the same load balancer you already have. That keeps the “community‑driven” vibe without overcomplicating the architecture.