teesloane
commented
3 years ago I think I see what you mean. #+FIRN_UNDER is intended for flat-file structures and thus arbitrary decisions of what "goes under" what. This will continue to be Firn's method for organizing information. However, I think a file-system index/site-map makes sense. However, unfortunately, as this is not my use case for Firn, I have no intention to build this functionality. I would however accept a PR on this. In case anyone is interested in submitting a PR the following would need to be done:
In firn/build.clj
- create a function called "make-site-map-from-fs".
- this will do what
make-site-mapdoes, except it builds a tree structure from a file's path, rather thanfirn-undervalues. - store this value in the config map in the function
process-allunder a key such as:site-map-fs.
In firn/markup.clj
- Create a new function called
render-site-map-from-fs, which will render html from thesite-map-fsvalues. - Rename
render-sitemaptorender-sitemap-from-firn-under - (re)create a new function called "render-sitemap"
- this function will, depending on incoming options, render either the site map from fs, or from
firn-under - ex
(render :sitemap {:filesystem true})
- this function will, depending on incoming options, render either the site map from fs, or from
And of course, write tests.
Thanks for the suggestion!
NightMachinery
I organize my notes using the filesystem directory (which makes it really easy to integrate with a lot of unspecialized tools). I wonder if it's possible to use this hierarchy instead of
#+FIRN_UNDER?E.g., I have:
I like to see these as a tree-like sitemap on my index page. Ideally, each file also contains a tree-like sitemap of its parent directory.