But I think that in that case it either it would have to be served as static assets, probably with some catch all route that forwarded to a router that would sit beneath the normal routes - but here you would basically loose the ability to “seamlessly” integrate other parts of phoenix, like having assigns, small helper/partial templates and such, or it would probably be quite difficult to glue it together into an existing static file in case you wanted those? I might also be misunderstanding what you envision.
1 Like
