Welcome#
What is Flask-Commands Unwatched
What Flask-Commands is built to do, which parts of a Flask app it accelerates, and why the project leans so hard into local-first scaffolding.
If the embed does not load, watch on YouTube: What is Flask-Commands.
Flask-Commands is a local-first CLI plugin for Flask that adds a small amount of opinionated but transparent structure for building Flask applications quickly. The goal is not to make a pretty website. The goal is to help you scaffold views, controllers, routes, and models so you can spend less time wiring and more time building.
It focuses on removing repetitive setup work, from project scaffolding to wiring views, controllers, routes, and front-end tooling, while keeping everything local, readable, and easy to customize.
All generated code is plain Flask code on disk. No hidden runtime layers. No framework lock-in. No mystery sauce. Just files you can open, read, edit, and actually own.
What Flask-Commands Is Not#
What Flask-Commands is not Unwatched
What the tool is intentionally not trying to solve so you can keep your expectations aimed at structure, wiring, and repeatable setup instead of design polish.
If the embed does not load, watch on YouTube: What Flask-Commands is not.
Flask-Commands is not a design system, CSS framework, or website beautifier. The examples in this documentation keep the templates intentionally plain so the focus stays on structure.
If you want to make something beautiful later, I will have a solution to that soon (Flask-Flare). Flask-Commands, however, is a different layer of work. It is here to help you build the app shape, not win a beauty pageant 💃.
The Plain Recipe App We Are Building#
The plain recipe app we are building Unwatched
Why the docs use a plain recipe app as the teaching example and how that example gives us believable nested relationships to work with.
If the embed does not load, watch on YouTube: The plain recipe app we are building.
Throughout this documentation we are going to build a small recipe app. It is not because recipes are magical. It is because recipes give us very believable relationships:
recipes
comments
images
ingredients
That makes the app a great teaching tool for:
views
routes
controllers
models
nested resources
We are also going to keep the templates intentionally plain. The point is to show how the data structure fits together, not to distract ourselves with CSS when the real lesson is how the pieces connect.
How to Use This Documentation#
How to Use This Documentation Unwatched
How the written chapters and video callouts fit together so you can follow the course in order or jump to the command family you need.
If the embed does not load, watch on YouTube: How to Use This Documentation.
If you like learning as you build, good news, that is exactly how the rest of this documentation works. This documentation is written like a small class. You can read from top to bottom, or you can jump around to the command family you care about.
Each teachable section starts with a video card that shows the video title, and a checkbox to indicate if you you have watched it so you can mark your progress through the series. If the video is already linked, you can expand the card and play it directly on the page. If the video is still planned, the card keeps its place in the course so you can see what is coming.
The written docs are still the source of truth while the video cards are meant to act like a little guide walking you through that exact section.