I'm getting close to finishing the extension/plugin functionality for Feather Wiki, and I was able to successfully write a search extension using Fuse.js! The plugin will be included on the website when the new version with the extension support is ready :)
The Choo framework is set up to replace the <body> with its render, but any <script> on the page when it's loaded should run—it just won't appear in the inspector after Choo renders.
EDIT: Unless you're talking about it surviving after saving the wiki, in which case it won't remain. I'm actively working on support for extending Feather Wiki that allows whatever custom JavaScript you want, in a very similar way to how the custom CSS is preserved. But it's not ready yet. Keep an eye out for version 1.3.0 in the near future!
I'm currently working on a way to extend the code by revealing the underlying [Choo](https://choo.io) framework to enable easier hacking! Search is one feature that theoretically won't be too hard to add, but I excluded it from the core because it would have made it too big.
Note: I have no solid reference point for what "too big" actually means for this project—my only guideline so far has been "as small as possible"
Exactly this. I wanted to see how small I could get it (Hummingbird) and then got obsessed with the idea of bird names for the build versions and just had fun with it :)
It's inspired by TiddlyWiki, but it's not nearly as feature-packed by design. Literally the only reason I even started this project was because I noticed how big an empty TiddlyWiki 5 file was and thought I could make one that was smaller. :)
I'm actively working on a way to extend individual wikis, which will hopefully pave the way for more features through hacking it.
This is very true. I added a warning when switching pages within the app itself when the editor is open, but it would definitely be worth the extra bytes to add a warning when closing the tab!
Seems like an excellent way to lose data and the best kind, thoughts typed.
Tiddlywiki will prevent a page close, this does not and will lose the entire wiki. Feather warns on not saving individual pages, but saving in this context means so little, this should just be part of the ephemeral internal state. No saving required. Save to disk is the only permanent storage and Feather doesn't have any guardrails here.
I don't do browsers, but can locally loaded file set cookies and/or use browser storage? I shouldn't ever have to consciously think about saving a file, let alone an entire wiki in 2022.
