I've consolidated the features from a previous pull request with a bug fix I made to my previous code as well as adding a way to import css and js files from the local media on page rendering. An explanation of all the features added along with the documentation for each feature can be found here:
As far as additional features which I have thought about but haven't been able to get to yet, here are some ideas:
A template/blueprint/widget system which allows data to be mapped to a markdown/html format. For extensive wikis with many pages with common formats, it is often difficult to read html elements which need to be conjoined in markdown rendering. So, it would be nice to be able to use other formats like yaml, json or csv and then map them to markdown, html or tables.
A way to load files into the media sub-directory directly from the wiki. Currently, my code only supports files which are already on the server.
Similarly, a way to create alias for pages directly in the wiki interface. Once again, my code only supports aliases which have been added to the config.yaml file, which requires a reboot of jingo to update and would be difficult to maintain if jingo was being edited live by many online users.
I've consolidated the features from a previous pull request with a bug fix I made to my previous code as well as adding a way to import css and js files from the local media on page rendering. An explanation of all the features added along with the documentation for each feature can be found here:
https://github.com/rj919/jingo/blob/master/README_FORK.md
Look forward to seeing jingo v2...
As far as additional features which I have thought about but haven't been able to get to yet, here are some ideas: