I'm not sure how this should be implemented in Flask, perhaps we could create the entire application as a blueprint use internal nested blueprints for the _
, and use .
(Though at the thought of it, a blueprint (non-nested) for each /site/_
should be enough because the static files aren't going to be served by Flask anyways. Then it might be a bit hard to teach url_for
about routes in /site/
.)
This isn't entirely necessary, as the overhead of running a lightweight WSGI server like Gunicorn doesn't seem like much. But it's probably good to have to be a bit more manageable.