There is no one size fits all answer to this and following the GitHub you linked would be actively harmful in my opinion. The specifics of your situation matter greatly.
Any ways to standardise it are deemed to produce illiterate "CTOs" who follow the notorious saying about a man with a hammer looking at every problem as a nail. There is a fair share of people like this in IT
Would love to see real examples of this thought process... i.e. of the form "we have these requirements, so we chose this and that, etc."
From what I see nowadays, it's more like, hey we have a project... Let's do it with AWS it has a ton of cool features!
(substitute AWS with GC, Azure or anything of your choice)
So ideally there will be many many lists / recommendations / best practices (with the org's specific situation / requirements) such that I and others can formulate our specific blueprint and start building.