[Feature] More control over the URL routes the module handles

[bartaz]

Currently discourse module is configured by passing a urlPrefix to it and ALL URLs under this prefix are served from discourse.

For Vanilla docs where we have part of docs served from discourse and part from Flask webapp, we'd like to have more control on what URLs are handled by discourse.

In our case we'd like to keep current URL structure of /docs/patterns/notification being served by Flask, and only a design guidelines subpage /docs/patterns/notification/design to be fetched from discourse.

Our current workaround is to have a /design prefix for discourse, so having URLs of /design/patterns/notification alongside /docs/patterns/notification, but this is not ideal.

Would it be possible to have more control over which routes are handled by discourse module and not assign whole URL prefix to it?

It would be nice if we can make it in a way that just works with Flask routes. Something like:

@app.route("/docs/<path:pattern_path>/design")
def get_design_guidelines(pattern_path):
    # get content from discourse based on the path

[sowasred2012]

To be discussed in the infra guild meeting on the 28th of March.