What:
Generating a blog post generally involves taking a content file, which may be a markdown, rst, or a simple text file and transforms it into some final format like html for final viewing and archiving.
Since most of the time final content in in form of html/jss/css, This process collectively can be referred to as static site generation.
The amount of controllability in the final generated content in form of UX, interactivity, themes, deployment etc. makes the core of a so-called static site generator.
Some generators also include functionality to push generated content to hosts like netlify, github/gitlab, fastly etc. hence making possible use of corresponding CDNs for faster content delivery.
Nevertheless, an user would have to choose and set up the pipeline at-least once to make the future blog generation process as seamless as possible.
Sometimes the thought of setting such a pipeline may seem daunting, and discourage people into delaying having a personal blog/website.
Medium , Substack, WordPress etc. are also popular choices promising to make it easier to publish blog posts, and have a following as well.
In my opinion it is better to de-couple blog-generation from deployment to make it easy to switch platforms if needed, in case you are setting your own pipeline.
Why:
Let internet preserve the content for you, as you definitely would be one of people searching that content later on.
Writing makes concepts much clearer, and also can be a way to organise your feelings and thoughts on a matter. It doesn’t need to be final, as we are always learning and editing is easier than creation.
Having your own content in single format, makes it easier to search, manipulate and serve even on a
