At the moment most CSS is under app/static/style.css, but in #38 was introduced app/templates/errors/style.css. It would be nice to have CSS close to the related HTML in the file tree, but performance-wise I think it shouldn't be a dynamic render but a static serve.
In other words, both of the current approaches have upsides and downsides. Maybe there is a third way that is even better. In any case we should use one approach across the repo.
At the moment most CSS is under
app/static/style.css
, but in #38 was introducedapp/templates/errors/style.css
. It would be nice to have CSS close to the related HTML in the file tree, but performance-wise I think it shouldn't be a dynamic render but a static serve.In other words, both of the current approaches have upsides and downsides. Maybe there is a third way that is even better. In any case we should use one approach across the repo.