Important steps
Background:
Important steps: build, CI, code quality, review app , production, docker image, cache, variables, issue board, runner, (artifacts), parallelization , junit, coverage, Prometheus, kubernetes service (part of deploy, runner), slack integration
What questions are you trying to answer?
Which parts (of CI/CD) are important? How can we help people to know about these parts and help them learn and use them?
Are you looking to verify an existing hypothesis or uncover new issues you should be exploring?
I don't really want to gamify it, but thinking about someone getting started with GitLab CI/CD, they might add a config that does some tests. But we could detect that they don't have Code Quality in there, and suggest they add it, link to docs, tell them right here how to add it, or even just add it for them. Going further, tell them about review apps, etc. Also, detect they can improve things by adding cache, parallelization, etc. Is this a good approach? What is holding people back from using these things? Are they fully aware of them but just don't care? Or do they want it, but don't know how to start? Or are they completely unaware they exist at all?
What is the backstory of this project and how does it impact the approach?
Random thought came to me that we could show tips or even tutorial style guidance
What do you already know about the areas you are exploring?
What does success look like at the end of the project?