Tooling & Stack

This page defines the core stack for the challenge. It is the baseline system used to build products, document decisions, analyze usage, and publish the process.

The stack will evolve, but this is the current foundation.

Product stack

Frontend

• Nuxt for the application framework
• Nuxt UI for interface primitives and faster internal product development

Nuxt gives you a strong full-stack default with routing, rendering, server capabilities, and a structure that is fast to repeat across multiple products.

Nuxt UI helps keep the front-end implementation efficient so the focus stays on shipping.

Backend

• Supabase for database, auth, storage, and backend services

Supabase is the main backend platform for the challenge. It covers the core infrastructure needed to launch quickly without rebuilding common backend concerns from scratch.

Analytics

• Metabase for analytics, reporting, and visibility into product data

Metabase will be used to inspect product usage, surface trends, and make decisions based on real activity instead of guesswork.

Content and production stack

Video production

• DaVinci Resolve for editing the daily YouTube videos

The challenge is both a build system and a content system. Video production is part of the workflow, not an afterthought.

Recording

• OBS for capturing focused build segments during the day

OBS is used to record short, intentional clips that can later be organized and assembled inside DaVinci Resolve.

Documentation

• Nuxt Content for this documentation site and knowledge base

This docs project is where the initiative gets documented in a structured way so the process can be reviewed, improved, and reused.

Why this stack fits the challenge

The stack is intentionally practical:

• fast to set up
• flexible enough for different startup ideas
• good for iteration
• strong enough to support both shipping and documentation

The point is to reduce friction. Every tool here should help move from idea to product to reflection as quickly as possible.

Operating principle

If a tool slows down execution, adds unnecessary complexity, or does not help the daily workflow, it should be questioned.

This challenge is ultimately about building a repeatable system for rapid product creation. The stack exists to support that system.

Next step

Move to YouTube Episode Workflow for the production format, recording structure, and editing system behind the daily episodes.