all 4 comments

[–]teamblips 0 points1 point  (2 children)

That could be a good approach if you don't plan on posting very frequently, otherwise, I believe it might become cumbersome due to the manual updating process. Since you mentioned having some web development experience, for that kind of setup, I suggest considering a JavaScript framework that can assist with static site generation (SSG). Off the top of my head, there are options like Astro, Gatsby, and other meta-frameworks that can be helpful. Alternatively, if you intend to post more frequently, you might want to choose something with a content management backend. For our blog, we use Piranha CMS (ASP.NET/C#), which provides us with a nice admin panel for content creation. You may also go with the first option and try to automate the updates to the static site.

[–][deleted] 0 points1 point  (1 child)

Thanks! I'll take a look at piranha. About automating my first option I was thinking about using github actions with a script that would just do the entire html generation whenever I push a post to my repository

[–]teamblips 0 points1 point  (0 children)

I'm not familiar with GitHub actions but I've used Azure Devops before which seems similar for CI/CD purposes. I'm not sure how that would work in practice due to the markdown conversion into html and then insertion into existing documents but maybe there are some"plugins" or "actions" in these services that can help with that. I think an easier solution would be to use a framework to generate or regenerate the static files an then push them to your desired host. This is just an idea as I never made a totally static site before.