FSNotes manual
xxxAleksandrxxx opened this issue · comments
Description
Hi!
Thank you for the app!
I am a new user and now trying to switch from Obsidian to FSNotes. I've read your wiki page https://github.com/glushchenko/fsnotes/wiki/Backup-&-Versioning-of-Notes
but still don't understand what are
- inbox
- notes
- todo
How do I control them (rename, delete, create new one)? How to create folder-in-folder structure and so on?
Could you share more detailed user manual for those who just started to use this application and don't understand probably well-known intuitive things.
Best regards
FSNotes version
6.2.2 build 277
macOS/iOS version
iOS
These are standard filters and should be discoverable through small amount of use:
Inbox = unsorted notes that are not in any folders
Notes = all notes across all folders
Todo = notes containing todo items (Format > Toggle Todo)
You cannot create or rename the built-in filters, but you can avoid using them by hiding them (View > Show in Sidebar) personally I hide all except Inbox and Trash.
To create new filters use folders (Library > Create Folder) or tags (type # followed by tag name)
Folder-in-folder structure is supported on macOS, but not currently supported on iOS.
Tags may be an alternative.
Thank you!
Hi!
Am I correct that MacOS version of FSNotes supports nested folders while iOS version doesn't?
I used the same folder with folder-in-folder structure and on MacOS it shows the same way as in Finder app but on iOS it shows mess of folders.
Do you plan to implement the same behaviour for iOS and MacOS soon?
If not, I would probably need to change the way how I store the notes...
@xxxAleksandrxxx yes, macOS version gained this in the most recent version. iOS version needs to catch up soon.
I updated the 4. Sidebar note in the Welcome folder, which hopefully can help someone else figure out how this all works, it's available here: https://p.fsnot.es/7wr7wlnmpu/
It probably could use some cleanup before it's ready for integration directly, but hopefully it helps whoever is doing the documentation make it a bit more user-friendly.