htmlparser VS maddy

There are many html parsers, but I have not yet found a suitable one in c++, so I made my own. It is based on the whatwg specification, added several ways to search for nodes, support for callbacks called during the parsing process, many selectors, search for unclosed tags, html formatter. I hope it will be useful to someone else. Link: https://github.com/mylogin/htmlparser

Since I offloaded my markdown parsing to maddy, I did not test for it because it was not my own code. As a result, it was difficult to find parts that I could test. I mostly created my test cases for end to end testing. Since the number of things to test for is always numerous, I ended up finding a few things I could test for. But, I definitely am not satisfied with the number of tests I currently have and will be adding more in the future.

Across all the JavaScript-based SSGs, palpatine is developed from the ground up using C++ and CMake as the build system. As the developer and maintainer of palpatine my main concern is to make it lightning fast compared to others. Currently, palpatine1.5 can generate a static site in less than 1 second. I've also made sure that it is easy to use, with a simple command line interface. The documentation is also precise and easy to follow. However, it is lacking one of the core features, supporting markdown files fully. I've been working on this feature for the past few days and I found a header-only Markdown parser library maddy. But it seems that it has been more than a year since the last commit was made to the library. I'm not sure if it is still being maintained. CMake was quite upset about how outdated it was.

Taking inspiration from Docusaurus, I added full markdown parsing support to my SSG. I chose to add this because it was a core component of my SSG that remained incomplete. Instead of adding a nice-to-have feature, I figured it would be best to complete the core functionality of my SSG first. Instead of coding my own markdown parsing, it was much easier to simply use a markdown parsing library which already existed. I did this by using a maddy, a C++ markdown parsing library. The process of using the library was very straightforward, although calling its methods did noticeably slow down the html generation. After verifying that it worked with my SSG, I removed my initial implementation of markdown parsing.