Q: Your organization has 40 disparate starter repositories. How do you design and standardize enterprise 'Golden Paths' so developers can scaffold microservices with built-in CI/CD, telemetry, and security, while maintaining template updateability over time?

Adopt Copier for template source definitions. Unlike Cookiecutter, Copier maintains a `.copier-answers.yml` file in the generated repository, enabling `copier update` via GitHub Actions to backport security updates and Dockerfile patches without overwriting custom business logic.

# Re-apply upstream template changes to existing microservice
copier update --answers-file .copier-answers.yml

Expose the Copier template through Backstage's Scaffolder UI via custom actions (`scaffolder-backend-module-copier`). Developers fill in a 3-field form in the browser, triggering repo creation, branch protection rules, and SonarQube registration automatically.

# template.yaml
spec:
  steps:
    - id: template
      name: Scaffolding Service
      action: copier:copy
      input:
        targetPath: ./output
        values:
          serviceName: ${{ parameters.name }}

Run a central GitHub Actions scheduled workflow across all organization repositories. When a Golden Path template releases a new semantic version (e.g. v2.1.0 updating Node.js LTS), the workflow executes `copier update` and submits an automated PR to each microservice.