Another +1 here for textbundle support. Bundling immutable assets (such as images) inside a simple markdown-based folder format would be desirable and solve a number of problems. The suggested workflow of creating a custom folder/group structure every time is a PITA, even if it’s automated with a template.
For example:
- start writing in a markdown document, then realize you want to add images
- look up how to do this on the forum (either because it’s the first time or you haven’t done it in awhile)
- run script or manually create folders/groups
- import the image to the correct folder/group
- create image link in markdown file
- test to make sure you did all the manual steps correctly
—this is a lot of administrative overhead with room for error when the purpose is managing knowledge.
TextBundle would also be a useful format for importing, for example as an alternative to .webarchive. I prefer to use markdown much of the time for importing articles, but that means images have to be manually downloaded and inserted into a folder/group structure.
Then there’s the need to keep everything properly organized in the folder/group. Want to run classify? Nope… need to move everything manually.
Etc. etc. TextBundle seems like a good solution to a series of problems if the desire is to not work in RTF. It abstracts away the management of the tool so that energy is spent on management of knowledge.
(see also: Markdown as first-class citizen & networked knowledge )