I noticed a theme across some of this week's posts: there are a lot of complex decisions that go into planning a Jamstack site. There are hundreds of options to choose from - SSG, deployment, headless CMS & more. The flexibility and options can be both a benefit and a burden. As Sean Davis and Jon Yablonski point out, picking a Jamstack "stack" can simplify the decision-making process, which you can then work to further automate. However, as Colby Fayock explains, don't let that deter you from using projects like your blog for experimentation.