CraftlyNow Docs

Overview

CraftlyNow is the startup-specific documentation space for the challenge. Instead of mixing every product note into the global docs, this section keeps the product context, decisions, and implementation notes attached to the startup itself.

The goal is to make each startup readable on its own: what it is, how it is built, how the workflow operates, and what changed over time.

Product Overview

CraftlyNow is a content-first founder workspace. It combines product building, structured knowledge capture, and educational publishing into one operating loop.

The startup should make it easier to manage course material, shape lesson content, organize production assets, and keep the documentation tied to the actual product work.

• capture course and lesson assets in one place
• turn product work into publishable educational material
• preserve the process behind every change and release

Tooling & Stack

CraftlyNow uses the same baseline stack as the challenge, but this page should track the startup-specific implementation details as they evolve.

• Nuxt for the application layer and structure
• Nuxt UI for the product interface and docs-aligned design language
• Supabase for backend data, auth, and storage
• Metabase for analytics and reporting
• DaVinci Resolve for video production in the publishing workflow

Over time this section should document the exact architectural decisions specific to CraftlyNow rather than only the shared challenge stack.

Build Notes

This section should become the running product log for CraftlyNow. Each build session should leave behind a short record of what changed, what was decided, what broke, and what comes next.

• scope of the current iteration
• UI or workflow changes shipped
• backend or data model updates
• issues discovered during implementation
• next actions for the following session

Publishing Loop

CraftlyNow is not only a product. It also supports the public side of the challenge by helping the daily build process turn into reusable content.

The docs for this startup should eventually connect product work to course assets, video scripts, lesson outlines, and the final published material so the creation loop stays visible and repeatable.