I’ve been experimenting with different presentation of the files and folders myself. One idea that I tested is having a very simple file/folder structure in the side menu and using transclusions do the rest of the work.
So, instead of this in the side menu …
Blog
2022-08-28 ABC
2022-08-29 DEF
… readers would only see this:
-Blog
-Blog
is one Markdown file that uses transclusions, so the Markdown would be this:
![[2022-08-28 ABC]]
![[2022-08-29 DEF]]
If you want to test this approach, then you need to take these steps:
(1) create the Markdown file (-Blog
) in the root folder for your blog. (For me, I created -Blog
in the wte
folder.)
(2) Hide the Blog
folder and all of the blog posts in the side menu by add some CSS in publish.css
. This worked for me:
.tree-item-self[data-path^='wte/Blog'] {
display: none;
}
I liked my transclusions experiment so much … I think I went a little overboard, and now I’m mixing some visible folders in the side menu with things like -Blog
.
Bonus tip! If you’re going to go nuts with transclusions, as I did, then you will probably want to remove the scroll bar in the inserted file, which can make it hard to scroll the entire page.
/* Remove scroll bar from transclusions */
.markdown-preview-view .markdown-embed-content {
max-height: unset;
}
.markdown-preview-view .markdown-embed-content > .markdown-preview-view {
max-height: unset;
background-color: var(--theme-transclude-background);
}
And here is another bonus tip!!! Play around with format of the title of the inserted file by modifying the CSS. I like the titles, but I wanted them to wrap correctly (not go on forever and ever) and I wanted them aligned to the left. So, this is what I added:
.markdown-embed-title {
/* display: none; */
line-height: normal;
text-align: left;
word-wrap: break-word;
white-space: normal;
}
Let me know what you think of this workaround and what you come up with!