What should I use for golden path templates and service scaffolding?

For golden path templates and service scaffolding, the best choice depends on whether you want a developer portal experience or a repo-first template system.

Good options

1. Backstage Scaffolder

Best if you want a full internal developer portal.

• What it does: Creates software templates, service skeletons, and standardized onboarding flows.
• Strengths:
  • Strong “golden path” workflow support
  • Integrates with GitHub/GitLab, CI/CD, Kubernetes, cloud, docs
  • Great for self-service platform teams
• Use it when: You want a centralized catalog + templates + governance.

Best for: Medium to large orgs building a platform engineering experience.

---

2. Cookiecutter / Copier

Best if you want lightweight repo templates.

• Cookiecutter: Simple project template generator.
• Copier: More modern, supports updating templates over time.
• Strengths:
  • Easy to adopt
  • Works well for service scaffolding
  • Can be used from CLI or automation
• Use it when: You want template-based repo generation without a full portal.

Best for: Teams that want quick, low-friction scaffolding.

---

3. Nx Generators / Plop / Yeoman

Best if your services live in a monorepo or JavaScript/TypeScript ecosystem.

• Nx generators: Great for enterprise monorepos and enforcing patterns.
• Plop: Simple generator for files/snippets.
• Yeoman: Older but flexible.
• Use it when: You want codegen close to the repo/tooling.

Best for: Monorepos, frontend/backend codebases, JS/TS-heavy stacks.

---

4. Custom scaffolding in CI + templates

Best if you need a highly tailored workflow.

• Build your own template repo + automation around it.
• Can be driven via GitHub Actions, GitLab CI, or internal CLI.
• Use it when: You have unique compliance, metadata, or approval flows.

Best for: Highly regulated or bespoke environments.

---

My recommendation

• If you want a true golden path platform: Backstage Scaffolder
• If you want simple service templates fast: Copier
• If you’re in a monorepo / JS ecosystem: Nx generators
• If you want maximum control: custom CLI + templates + CI

Practical default

A common pattern is:

• Backstage for discovery and self-service
• Copier or Cookiecutter for the actual template generation
• GitHub Actions/GitLab CI for validation and post-creation setup

If you want, I can also give you:

1. a decision matrix for these tools, or
2. a recommended golden path architecture for a platform team.