I posted earlier about some changes I made to the "public" plugin, and Jeremy suggested making it a separate plugin which uses the public plugin as a dependency, but he's looking for community feedback on if it should be part of Roda.
The use case for this is you can't serve a static site with Roda just with the public plugin. For static sites it's typical to have URLs like /path/to/page which can resolve to either path/to/page.html or path/to/page/index.html — this is commonly known as "pretty URLs". In the Bridgetown project which has adopted Roda
for both a dev server supporting the static output as well as dynamic routes in dev and production (using Roda's typical routing features), we had to patch or otherwise change public plugin's behavior to enable this.
Rather than alter public, this PR adds "pretty_public" which works just like public but adds support for pretty URLs along with a few configuration options (if you want to support .htm, .txt, whatever).