Centralized vs Individual CI/CD for 100 Projects: What’s Better?

I'm working at a company with around 100 projects and we're lacking proper CI/CD practices. I'm proposing that we set up a centralized CI/CD process using GitLab CI, where developers can just 'include' a shared pipeline to access all CI/CD features at once. This would allow us to manage the entire company's CI/CD from a single repository, streamline processes, and ultimately provide better and more frequent updates. However, this means we'll have to standardize our development practices. For instance, if we have a Go project, it should adhere to the go-project-layout for the CI/CD to work right. I'm aware that this may not fit well with mono-repositories (where one repo could contain multiple services). On the flip side, my CTO believes each project should have its own CI/CD pipeline, allowing various deployment methods like tag-based or branch-based deployments, plus the flexibility to disregard the go-project-layout and skip unit tests for some projects. I think his approach could hinder our progress toward continuous development, but he doesn't seem convinced. I'm looking for authoritative articles or videos that support my viewpoint. I also understand that I might not be entirely right; perhaps individual CI/CD pipelines for each project could be the better route after all.