But that would explain the “what” of the workspace, not the “why”, which I think is way more important.
But that would explain the “what” of the workspace, not the “why”, which I think is way more important.
Yeah, I was more thinking about a how-to (parameters and descriptions) and a what. Then you have a nice skeleton where you can add the why and limitations etc etc.
Having to write out a lot of the stuff already in a workspace does take up a lot of time. Also formatting the markdown.
But that would explain the “what” of the workspace, not the “why”, which I think is way more important.
Agreed, I (try to) put lots of ‘why’ in bookmarks explaining why I’m doing something a certain way. If bookmarks could be taken into account when summarising the workspace that would be helpful