Hi, for a scenario when multiple blog posts are added often, work with the static approach (building all the time) might be the best idea? or maybe having in mind the SSR apply for this?
It really depends on the frequency. If you are okay with deploying a build once every 3 days (assuming that's the frequency), I would say static rendering would be enough.
This is mainly because you do not need to set up a data storage source from which the blogs will be pulled. The data storage can range from a simple folder with markdown files to a full-on Headless CMS
Conclusion - Go for static rendering, unless there is a store from which blogs can be pulled easily. SSR is basically automating your build task.
Hi, for a scenario when multiple blog posts are added often, work with the static approach (building all the time) might be the best idea? or maybe having in mind the SSR apply for this?
It really depends on the frequency. If you are okay with deploying a build once every 3 days (assuming that's the frequency), I would say static rendering would be enough.
This is mainly because you do not need to set up a data storage source from which the blogs will be pulled. The data storage can range from a simple folder with markdown files to a full-on Headless CMS
Conclusion - Go for static rendering, unless there is a store from which blogs can be pulled easily. SSR is basically automating your build task.
And automation best described by XKCD is
Got it! Thanks so much for your advice @poovamraj