Replies: 1 comment 3 replies
|
Hey @Almeus, thank you for sharing your thoughts. Every point you listed is a valid request! Some background info: Currently we are moving with the engine towards plugins, so that features can be added that are not (yet) in the core of the wiki. This enables users to add the features they want without overloading the core functionality. Back to your suggestions: (1) visually differentiate [..] nonexistent pages: This is already available via docs/plugin_examples/plugin_redlinks (2) Call it "tags" or "categories": I can see that this is useful and a valid way for organizing the content of a wiki. Will think about it. (3) In (4) "backlinks" are available via docs/plugin_examples/plugin_referencingpages |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Like this project. Wish I could help but I'm not a developer. I've been trying a bunch of wikis lately and this one seems like it has potential. Mediawiki is too complex. Gollum isn't complex enough. Dokuwiki is ugly and requires a bunch of plugins to be useful. Bookstack almost isn't a wiki (you can't create new pages by linking from other pages). Wiki.js and Pepperminty wiki are abandoned. Tiddlywiki has a weird workflow thanks to it being a single HTML file.
Here are some ideas that I think might improve things.
Some of this may be scope creep, but I think number 1 (along with the ability to follow the link to create the page which Otter already does) is the feature that differentiates a wiki from a documentation system or CMS.
All reactions