เทมเพลตและไฟล์สแตติกที่อยู่ในขอบเขต Blueprint

A truly modular blueprint carries its own templates and static files. This keeps a feature self-contained and easy to move around.

When you create the blueprint, set template_folder so Flask also searches that folder when rendering this blueprint pages.

That template path is relative to the blueprint module thanks to __name__. Flask resolves it from where the blueprint file lives.

Flask merges every template folder into one search path. The blueprint folder is added to the global app templates, not fully walled off.

Because folders merge, two blueprints with the same filename can collide. Namespace templates by nesting them in a per-blueprint subfolder.

A blueprint can ship its own CSS and images too. Set static_folder at creation to hold this feature private assets.

Reference those assets with url_for and the namespaced static endpoint, so each blueprint serves its own files cleanly.

Give the assets a public route with static_url_path. This controls the URL browsers use to fetch the blueprint files.

The main app keeps its own /static for shared assets. Blueprint statics live alongside it, each reached by its own endpoint.

The payoff is a clean package: routes, templates, and static files in one place. That folder is the whole feature, ready to reuse. 📦

Since assets travel with the code, you can copy a blueprint into another project and it still works with little extra setup. 🚀

How do you link a blueprint static file?

Set template_folder and static_folder on a blueprint so it owns its assets, namespace templates, and link statics via blog.static. 🎉