Minisleep – A Tiny Wiki Engine

• zim-desktop-wiki

  32 1,784 0.0 Python

  Main repository of the zim desktop wiki project

  

  I use zim wiki for desktop wiki / knowledge base for my personal stuff. The biggest hurdle I have had with any wiki or knowledge base stuff is to actively using it and improving it. I find myself adding stuff in bursts and then not using it for weeks.

  https://zim-wiki.org/

• TiddlyWiki

  69 7,550 9.5 JavaScript

  A self-contained JavaScript wiki for the browser, Node.js, AWS Lambda etc.

  Tiddlywiki seems (from a technical perspective) a little bit closer to what you're imagining:

  https://tiddlywiki.com/

  Sadly it doesn't let you edit WYSIWYG, ie when you click "Edit" it still transforms the page back into monospaced markup script.

  Theoretically it should be possible to change that, but I have not looked at the codebase.

  If you were to do this from the ground up you would probably:

  * Enable .contentEditable on the whole page (or at least sections like )

  * Add a floating toolbar for formatting controls (and a save button)

  * Do the submit in javascript, so the page doesn't have to fully reload.

  * Possibly add a toggle edit button? Or would people be comfy being able to accidentally edit pages whilst reading (as long as they realise they have to hit "save" to make a change). This might ruin some people's navigation key shortcuts in their browser (eg users of Vimium).

  For personal or small-team use I could see this being good. For larger teams it would be a nightmare, as accidental edits would be common. The formal 3/4 step editing process has its problems, but it's a useful barrier against the tides.

• Appwrite

  appwrite.io

  sponsored

  Appwrite - The open-source backend cloud platform. Add Auth, Databases, Functions, and Storage to your product and build any application at any scale while using your preferred coding languages and tools.

  

• wiki

  0 319 0.0 CoffeeScript

  Federated Wiki - node server as npm package (by fedwiki)

  

  http://fed.wiki.org/view/how-to-wiki

  2. Once you're there, click the "wiki" word down in the grey footer. A checkmark will appear next to the word "wiki."

  3. Double-click a paragraph and edit. Ctrl-s saves. The page you edited will gain a yellow halo. The yellow indicates that your changes are only being saved in your browser's local storage for now. (If you have your own site and are logged in, changes will be saved on the server.)

  I run my own Federated Wiki (fedwiki) server. You can also just run it locally (which I do sometimes). It requires nodejs. I was a bit fussy with my server setup and have lighttpd as reverse proxy (I think that's the correct terminology) and 'supervisor' as nodejs babysitter, but most (all?) of that is not strictly necessary. fedwiki can just run on its own and serve its own pages.

  [0] https://github.com/fedwiki/wiki

• Trilium Notes

  77 23,626 9.3 JavaScript

  Build your personal knowledge base with Trilium Notes

  Trilium Notes might be what you are looking for. Very very pleasant

  https://github.com/zadam/trilium

• zim-wiki

  0 646 10.0

  This repository is a placeholder so we can use the asociated wiki for community documentation.

  Ahah, I found the tables! You have to go into Zim's settings and enable them as an addon in there. Ty, I thought there was no support whatsoever (other than putting pictures of tables in https://github.com/jaap-karssenberg/zim-wiki/wiki/Create-a-t... ).

  Indeed it still seems a bit limited. Nothing like Firefox's in-built table editor used to be (this is the one in Thunderbird, which is quite nice). I wish they hadn't removed that feature :|

  Treesheets is a beautiful program, but I'm too much of a pen-and-paper + plaintext notes person to appreciate it properly.

• Shaarli

  1 670 0.0 PHP

  The personal, minimalist, super-fast, no-database delicious clone. (by sebsauvage)

  I think about rate-limiting from an unprivileged user perspective and saw it first at https://github.com/sebsauvage/Shaarli/blob/master/index.php#.... So e.g. fail2ban is not an option. And the application has to deal with it.

  I care more about load/DOS than actual crack success. What means the firewall is the sensible place. Not the application.

  Or just take the risk, make backup/restore simple and do intrusion detection by monitoring a dedicated endpoint with e.g. https://updown.io/44q5 and let things happen for the sake of simplicity.

  Hm. (I'm doing a federated, single-user microblog engine targeting laypersons. A proof of concept is at https://codeberg.org/mro/ShaarliGo)

Suggest a related project