And a better markdown support in general was already on the roadmap, but got cancelled/removed?!
Maybe replace EditorMD as there is no development for more than 1.5 years. SimpleMDE is designed to work along with marked.js and it does look and work similar to EditorMD. Ok, development in SimpleMDE is going slow aswell but at least there is development at all. SimpleMDEmay be not as feature rich as EditorMD, but it provides a better rendering IMHO and many features are available with code snippets.
I already implemented this replacement for testing purposes once but doing this with every update is too cumbersome.
BTW TOC is already available - at least while editing. You can activate it by editing the template \seahub\seahub\templates\file_edit.html.
Don’t take it personally. In my opinion it would be bad if they create a plugin infrastructure.
All of the software on the market which implemented such an infrastructure are much more vulnerable to exploits. Just have a look at Wordpress. You can read about security issues every other week. The more complex a software is, the more vulnerabilities you have. I prefer simplicity like the KISS principle (“Keep it simple, stupid”).
I’m not a developer at all but as an end user, i think that the wiki feature is not irrelevant in the use of a cloud storage system. Many users points the lack of editing features in Seafile, that gives the felling of a “limited” software (which it is not).
I know hat Seafile Team @daniel.pan are not convinced about the wiki feature and i understand their point of view.
I’m not convinced, also, by a plugin infrastructure.
But i wonder is there would be some place for a 3rd party integration, as Django Wiki
If the Wiki is based on files, Seafile could eventually store them in libraries (as Seahub does with its own wiki)
Looking at the interface, the wiki could use seafile API to look for and attach files within its own library.
django-wiki stores the article data in the database.
I think it’s one of the strengths of the Seafile wiki that all content is stored as plain text files in a library that you can also edit by any other means. Therefore I can document our Seafile setup in it and refer to my locally synced copy even if I messed up our installation.
I did not find the information when i posted this idea, sorry.
But i checked and confirm that is uses a database to store the folder tree.
My idea was to think of a convenient way to provide wiki features as part of seahub/seafile.
Maybe the devs will find accurate to provide a richer interface while keeping the ability to store .md files in libraries, which is also very useful.
My wish is to provide users some little documentation about Seafile and our libraries and groups.
I think that building a wiki into a Organisation Library (Shared with anyone) and giving acces to it near the Personal Wiki link (in the tools section) coul easily do the job.
The wiki may be read-only but could be edited by admin or wiki owner.
It would be great to enlarge the use of wiki to the default users and give more user-friendly content to them.
I supposed that it is ot so complex and does not interfer with basic principles of the wiki in Seafile.
Thanks for the solution based on the template and your proposal for a “add link to menu” feature.
I already linked a public page, but it is not enough…
I’d like to give access (for registered users) to a complete Wiki , with the TOC on the left side and the list of pages.
Creating public shared links for all pages is not a solution for me, because they are difficult to maintain.