Being able to store the HTML, JasvaScript, CSS, or other static content in FME Flow Resources folders and serve them via Data Virtualisation Manual Endpoints directly (without a workspace that feed the Data Virtualisation Writer attributes) would be more straightforward and engine saving way to provide HTML pages, so the Workspace Endpoints could deal with the dynamic contents.

OK, it needs the ability to set the content_type header as well.