I believe static sites really are the best option for the majority of content-driven websites out there, and this is a great overview of the common ways SSGs are used. Once you really get working with SSGs, you'll find them to be so much more powerful and helpful compared to full-stack CMSs, and really allow you to free yourself from the constraints of databases and request performance, and just focus on the content and creativity around website creation.
I've also been making my own SSG, Orchid for about a year and a half now. I can confidently say that there is a big difference between a tool to "convert markdown from here to HTML there". Building a SSG that is both flexible, extensible, easy-to-use, and performant has been a huge task, but one I am committed to continuing long into future. I really like that this article focused on the benefits and power of SSGs in general, rather than comparing features among individual tools, and showing that SSGs do much more than just convert Markdown to HTML.
While these tools are all great for blogging and simpler sites or blogs, I am creating Orchid specifically for documenting code projects and managing the entire website for entire projects. I've always hated how Java projects will have a great-looking landing page site, but then link off to a separate site with terrible-looking Javadocs, and then to yet another site for the wiki or their blog. Orchid aims to bring all this together into a single site, with a single tool to intelligently assemble all of it together.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I believe static sites really are the best option for the majority of content-driven websites out there, and this is a great overview of the common ways SSGs are used. Once you really get working with SSGs, you'll find them to be so much more powerful and helpful compared to full-stack CMSs, and really allow you to free yourself from the constraints of databases and request performance, and just focus on the content and creativity around website creation.
I've also been making my own SSG, Orchid for about a year and a half now. I can confidently say that there is a big difference between a tool to "convert markdown from here to HTML there". Building a SSG that is both flexible, extensible, easy-to-use, and performant has been a huge task, but one I am committed to continuing long into future. I really like that this article focused on the benefits and power of SSGs in general, rather than comparing features among individual tools, and showing that SSGs do much more than just convert Markdown to HTML.
While these tools are all great for blogging and simpler sites or blogs, I am creating Orchid specifically for documenting code projects and managing the entire website for entire projects. I've always hated how Java projects will have a great-looking landing page site, but then link off to a separate site with terrible-looking Javadocs, and then to yet another site for the wiki or their blog. Orchid aims to bring all this together into a single site, with a single tool to intelligently assemble all of it together.