Flask project structure conventions - Step-by-Step Execution

Concept Flow - Flask project structure conventions

Start Project

↓

Create app.py

↓

Add folders: templates, static

↓

Add config.py (optional)

↓

Add blueprints (optional)

↓

Run Flask app

This flow shows the typical steps to organize a Flask project from start to running the app.

Execution Sample

Flask

project/
  app.py
  config.py
  /templates
    index.html
  /static
    style.css

This is a simple Flask project folder structure with main app file, config, templates, and static files.

Execution Table

Step	Action	File/Folder Created	Purpose
1	Create main app file	app.py	Contains Flask app and routes
2	Create templates folder	templates/	Stores HTML templates
3	Create static folder	static/	Stores CSS, JS, images
4	Add config file (optional)	config.py	Holds configuration settings
5	Add blueprints (optional)	blueprints/	Organizes routes in modules
6	Run app	app.py	Starts Flask development server
7	Exit	-	Project structure ready and app running

💡 All necessary files and folders created; Flask app runs successfully

Variable Tracker

Component	Before	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
app.py	None	Created	Created	Created	Created	Created	Created
templates/	None	None	Created	Created	Created	Created	Created
static/	None	None	None	Created	Created	Created	Created
config.py	None	None	None	None	Created	Created	Created
blueprints/	None	None	None	None	None	Created	Created

Key Moments - 3 Insights

Why do we need separate 'templates' and 'static' folders?

Templates hold HTML files that Flask renders dynamically, while static holds fixed files like CSS and images. This separation helps Flask serve files correctly, as shown in steps 2 and 3 of the execution_table.

Is the config.py file mandatory for a Flask project?

No, config.py is optional. It helps organize settings but the app can run without it. This is shown in step 4 where config.py is added optionally.

What is the purpose of blueprints in Flask?

Blueprints help organize routes into modules for bigger projects. They are optional and added after basic structure, as in step 5.

Visual Quiz - 3 Questions

Look at the execution_table, what is created at step 3?

A static folder

B templates folder

C config.py file

D blueprints folder

💡 Hint

Check the 'File/Folder Created' column at step 3 in execution_table

At which step is the Flask app started?

A Step 4

B Step 5

C Step 6

D Step 7

💡 Hint

Look for 'Run app' action in the execution_table

If you skip creating the 'templates' folder, what impact does it have?

A App will not start

B HTML templates cannot be rendered

C Static files won't load

D Config settings won't work

💡 Hint

Refer to key_moments about the role of 'templates' folder

Concept Snapshot

Flask project structure:
- app.py: main app and routes
- templates/: HTML files
- static/: CSS, JS, images
- config.py: optional settings
- blueprints/: optional route modules
Organize files for clarity and Flask to find resources.

Full Transcript

This visual execution shows how to set up a Flask project structure step-by-step. First, create the main app.py file where the Flask app and routes live. Then add a templates folder to hold HTML files that Flask will render dynamically. Next, add a static folder for CSS, JavaScript, and images that do not change. Optionally, add a config.py file to store configuration settings separately. For larger projects, blueprints can be added to organize routes into modules. Finally, run the app.py to start the Flask development server. This structure helps Flask find files and keeps the project organized. Key points include the separation of templates and static files and the optional nature of config and blueprints. The execution table tracks each step and what is created, while the variable tracker shows the state of each component as the project grows. The quizzes test understanding of folder roles and project setup steps.