Suggestion: make docfx to support to be included as a part in a site generated by other tools

Make docfx to play well with other tools. I already have a static site generated by my toolset. And I want to include several areas with api doc generated by docfx. For example for TS and .NET APIs. Currently I have to customize docfx template heavily. I have to change templates, css, js. As docfx assets aren't at the site root, they are inside a area (like /client-api and /server-api). And I don't want docfx asset to be loaded twice from that subfolders. So have a folder with all docfx assets at the same level as api areas. It's just an example why I need to customize js (all such things are hard-coded inside js).

So in general I'd suggest to think about supporting such scenarios when docfx generates one or several subarea of some big static site that generated by other tool (or not generated, it can be some sort of CMS) .