Noteplan zettelkasten5/1/2023 ![]() Organize any way you want to: from simple folders over P.A.R.A.Create tasks and notes quickly with Markdown.Plan your day by seeing your calendar, notes, and tasks in a single view.Perfect for project managers, designers, researchers, writers, students, or anyone who wants to be organized and efficient. NotePlan lets you manage everything in one place: your tasks, notes, and calendar. Having trouble planning your day, managing your to-do list, and organizing your notes? Always jumping between apps and losing track of what to do and where you put things? to make the experience feel more like their prior app.Having trouble planning your day, managing your to-do list, and organizing your notes? Always jumping between apps and losing track of what to do and where you put things? Say hello to NotePlan! NotePlan lets you manage everything in one place: your. And perhaps some guidance on common settings / plugins / themes to use for users who are switching from Noteplan, Bear, Roam, etc. This could be an interesting feature for certain personas as long as it doesn’t unduly disrupt workflows for the others.īut I do think it could be worthwhile for Obsidian to provide some guidance up front on the overall strategies that each option supports or inhibits. I may be misunderstanding the persona here, and I’m sure there’s other personas as well. (I’m in the latter, but do also store some reference/cheatsheet type info in the same vault, but would not want the described function to become a global default for all of my notes) I think this is showing a difference in the overarching strategy behind how different user personas use You may already have these personas developed but if not there seem to be at least two user personas at play here: one that wants a more hierarchical approach for knowledge/reference management, and one that wants a more fluid note-focused approach for Zettelkasten-style knowledge development with attachments relatively decoupled from notes. I suspect adding something like this opens the door to a lot of edge case complexity and it is probably preferable to keep Obsidian simple, especially since there’s currently a straightforward (but admittedly mildly frustrating for the individual who wants this) manual workaround. So adding this would require either (a) adding a configuration item that increases complexity or (b) changing existing behavior which breaks my own workflow. Then there’s the issue of how are existing user workflows handled? For example, my workflow doesn’t need this capability at all, because I either add images to a global folder or to a source-specific folder, so the images will always be attached to their source which is itself in the enclosing folder. Do you leave the image in the local attachments folder and update Note A point to the image in the “old” location? Or do you move the image and then update Note B to point to the image in the “new” location? Or do you copy the image to both locations? ![]() The problem I see with this is what happens if you have Note A and Note B both referencing an image in the local attachments folder, and you move Note A but leave Note B in place. OP’s question seems (to me at least) to be more about moving some but not all notes from a folder and taking their attachments with them.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |