Where were we... Ah yes. So I got a pretty sensible mechanism in place for scanning the content from the filesystem with node, in this git repo. I have a high level structure that looks like this:
pages: [
{ isFile: false, path: 'blog/blog-engine' },
{ isFile: false, path: 'blog/test' },
{ isFile: true, path: 'blog/code-as-graphs.md' },
{ isFile: true, path: 'blog/sagas-rant.md' },
{
isFile: true,
path: 'blog/test-ubo-tut/a.md',
saga: 'blog/test-ubo-tut'
}
]
If I have a folder with just one blog markdown file inside (here a.md
is this test case), I don't qualify that containing folder as a saga yet, even though this file has been identified as belonging to one, since it only has one post inside. This way I don't have to manually do anything to change a series of posts from being standalone into being part of a saga. It's really not a big deal, but this is an example of why it can be really nice to roll your own system so it can work in a way that truly makes sense to you.
It is also finally time to render plain markdown with Marked and Markdeep documents with the convert.ts
markdeep
script I already got working earlier this week.