If I have a file named foo.org, then http://mysite/foo would render foo.org if there's not a file named exactly 'foo', and if no other files match foo.*.
This would obviate the need to specifically define an engine for files that don't use the default rendering engine.
As a bonus, perhaps there could be a configuration setting in the .yml file to tell olelo what priority
the extensions are. For example, if I have foo.org, and foo.md then I could define an order ".org .md" and olelo would by default render foo.org when a user goes to http://mysite/foo
This issue is related to a comment on http://github.com/minad/olelo/issues#issue/29/comment/401218
If I have a file named foo.org, then http://mysite/foo would render foo.org if there's not a file named exactly 'foo', and if no other files match foo.*.
This would obviate the need to specifically define an engine for files that don't use the default rendering engine.
As a bonus, perhaps there could be a configuration setting in the .yml file to tell olelo what priority the extensions are. For example, if I have foo.org, and foo.md then I could define an order ".org .md" and olelo would by default render foo.org when a user goes to http://mysite/foo
--Nate