First off, I shot myself in the foot by putting thousands of nodes under my IMMUTABLE NAME, which is the initial top-level node, instead of starting another MUTABLE top-level node.
Why is a mutable top-level node important, you ask?
For this simple reason: leftside panel navigation and hashtag shortcuts. I love hashtags in WorkFlowy and use them constantly. They link important, temporary datapoints together which need to be addressed, and then I erase them as they resolve (these data points have to do with people rather than topics, so it helps to use hashtags that link anywhere in WorkFlowy regardless of headings and subheadings). BUT, it would save a lot of time to find my hashtags in a convenient location to easily click them! (As again, their function for me is very "high-traffic.") All of this to say that I wish I could alter my silly name at the top and use it to list certain important hashtags to easily search ALL of WF for them from the leftside panel which only works if the heading you click includes all the relevant nodes within it, since clicking a heading and then a hashtag will only search the nodes within that heading if you don't zoom out all the way first.
So, with a mutable name/top-level node I could put my hashtags there and access them with two clicks: Leftside panel + hashtag itself. That would be amazing, and moving all my current bullets to a new, mutable top-level node is NOT feasible because 1) alt-shift won't move them out of my immutable node, and 2) exporting (or copy/paste) won't work given the significant amount of shift+enter notes I have taken, which turn into bullets when pasted. 🤦♂️
However, even if I could edit my top node and update the hashtags there, all of that would be unnecessary if the hashtags were automatically stored in an accessible list somewhere by default!
That would be awesome.
I also support this user's idea which could potentially fix my dilemma as well! https://workflowy.zendesk.com/hc/en-us/community/posts/360062294951-immutable-nodes
Temporary but still less-than-ideal fix for the immediate problem (original request stands 🙂): inserted an otherwise-meaningless node echelon between my immutable name and the rest of my WorkFlowy. The node is labeled as "#: #hashtag #shortcuts #here #etc." This is my inelegant work-around for the fact that my main top-level node is locked, SHFT+ENTR notes don't export well, and hashtags only search within the current zoom level and can't be accessed conveniently anywhere besides some dedicated "#:" bullet . . . . 😝
Please sign in to leave a comment.