Figured something like that. And also for the md files. Just straight up content in there and no frontmatter or anything right? (May not even be a thing for md files, not sure)
Essentially what's happening is it takes your markdown content then converts it to HTML, then it puts the header above and the footer below. Those are held in `./templates` if you want to modify them. You don't have to include anything in your markdown other than the content, if I'm understanding your question correctly.
Also, one thing I'd like to sort out is making the page titles on the pages.html page that it generates not be based on the filename, but on the title of the article so-you-dont-see-stuff-like-this on pages.html.
As of yesterday since I added config variables, I'd like to relocate those to an external file to avoid recompile, and then use those to populate the header so that people don't take time to fill in the config and then still get "Bearclaw Blog" when they fire it up.
I really appreciate the time you're taking to talk this out with me, it's very inspiring and I'm getting lots of ideas. I can't wait to get done with Job 2 today so I can hammer out some of these things :) Thank you
Thanks! I ask myself often when I have ideas if it will maintain the simplicity or make it less out of reach for regular people. Please do let me know if you end up making a blog with it. It'd be cool if I could put a list of examples in the readme so that people can see what others have done with their bearclaw blogs
