That is my approach (partially from many years in graphic arts and printing, where data segregation per job was a necessity, so it’s part of my mindset). But beyond my personal preference, it’s still a valid approach for anyone to use.
Here’s an example…
My Group (parent group, titled by day, subject, etc.)
- TodaysDocument.md (Markdown document)
- img directory (images pertinent to the day, subject, etc.)
- resources directory (css, js, etc.)
- docs directory (miscellaneous linked docs)
And you could also keep the non-Markdown files in the root of the parent group instead of subgroups too. Both are valid.
Note: The resources directory could be in a single location in the database and linked, but I isolate all the data for a given document. Again, part of my mindset, and also it’s due to an ongoing evolution and exploration of the styling and mechanics of Markdown/CSS/JS/etc.