There are a handful of things that Feather Wiki either simply cannot do or struggles with:
- Certain quality of life features, optimizations, and data validations are excluded where possible to save on space.
- Feather Wiki is a deliberately barebones tool built for the novelty of being as tiny as possible, so you may run into occasional issues or annoyances.
- That being said, please create a bug report in the Feather Wiki code repository whenever you run into a problem! Feather Wiki is a living project, and I need your help to find all the edge cases that I don't know need to be tested.
- Feather Wiki is a deliberately barebones tool built for the novelty of being as tiny as possible, so you may run into occasional issues or annoyances.
- Feather Wiki will not notify you of new versions as they are released.
- You can either subscribe to the source code (either create an account and watch the repository or subscribe to the RSS feed) or the official Feather Wiki account on the Fediverse for updates.
- While absolutely not necessary for normal use, a modest knowledge of HTML, CSS, and JavaScript will help you get a lot more out of Feather Wiki.
- Extensions that change the way Feather Wiki renders (i.e. adding/changing things on the screen, changing the Markdown parser, etc.) will typically cause the screen to flicker.
- This is because the replacement causes a re-render of the page, and unfortunately cannot be avoided.
- Nested lists in Markdown struggle with alternating types (i.e. switching from ordered to unordered lists and back within nested lists)
- Try to stick with either ordered or unordered lists in a single list when nesting them (as seen on this page).
- Search is not (and will never be) built in to Feather Wiki to save on file size (but ask yourself, do you really need it?)
- If you do really need it and don't mind the extra bandwidth + file size, check out the Search extension.
- The way Feather Wiki stores data in its file means that writing
</script>
anywhere in your pages may cause loading problems after it is saved and re-loaded.- To get around this problem, you can either use the escaped </script> or put a backslash before the slash whenever you type it (
<\/script>
) so the browser doesn't identify it as a real HTML tag.
- To get around this problem, you can either use the escaped </script> or put a backslash before the slash whenever you type it (