https://hackingandslacking.com/serving-frontend-templates-and-assets-in-flask-5e2844345ff4

If you’re familiar with Django (or Python to any extent), you’ve probably accepted the concept of what Python guys refer to as “static assets” without much consideration. At some point in Django’s conception, a design decision was made: any code, styles, or assets were tucked away into their own respective uninteresting corners of the framework. Thus it was known: anything that isn’t Python is simply a “static” asset to be dealt with either locally or via a CDN somewhere. Basically, we as Python nonchalantly accept that all the things which make an app an app, such as anything visible to a user, is simply something to be dealt with. Ya know, like, over there or something. Screw it, just make a folder for all of it. Or two.

While something as simple as terminology reveals a lot about how we think about our codebase, apparently nobody thinks this is amusing except me. Fine, whatever. Let’s just get to making an app that has some pages and styles and stuff.