CBC GitHub Super-Template — Delivery Package

Everything you need to standardise every repo in github.com/careerbytecode.
Template · Playbook · Filled example · Migration checklist. All in one zip.

cbc-github-super-template/
├── README.md                    ← You are here (delivery notes)
├── MIGRATION-CHECKLIST.md       ← One-pager for bringing existing repos in line
│
├── cbc-repo-template/           ← THE UNIVERSAL TEMPLATE
│   ├── README.md                 → With {{ PLACEHOLDERS }} to find/replace
│   ├── CBC-REPO-PLAYBOOK.md      → 15-part brand & structure playbook
│   ├── TEMPLATE-USAGE.md         → 9-step guide for new repos
│   ├── LICENSE                   → MIT
│   ├── CONTRIBUTING.md
│   ├── CODE_OF_CONDUCT.md
│   ├── SECURITY.md
│   ├── .gitignore
│   ├── .markdownlint.jsonc
│   ├── .github/                  → Issue templates, PR template, workflows, FUNDING
│   ├── docs/
│   │   ├── ABOUT-CBC.md          → Deep About CareerByteCode
│   │   ├── CBC-COMMUNITY.md      → Community, events, WhatsApp, benefits
│   │   └── CBC-BRAND.md          → Colours, logo, usage rules
│   └── assets/
│       ├── favicon.png
│       └── logo/                 → Full logo, lockups, icons, socials
│
└── cbc-cloud-aws-eks-lab/       ← THE FILLED EXAMPLE (a real repo built from the template)
    ├── README.md                 → Fully populated — no placeholders left
    ├── LICENSE, CONTRIBUTING, ... → Same brand chrome as template
    ├── docs/                     → Same doc set
    ├── assets/                   → Same logo assets
    ├── terraform/                → Real Terraform code (VPC + EKS modules + dev env)
    │   ├── modules/{vpc,eks}/
    │   └── environments/dev/
    └── scripts/                  → bootstrap.sh, cleanup.sh

• Create a new repo in your careerbytecode GitHub org: cbc-repo-template
• Push everything from cbc-repo-template/ into it
• Go to Settings → General → Template repository and tick the box
• Pin it on the org profile

From now on, every new repo starts with "Use this template" on cbc-repo-template.

• Create cbc-cloud-aws-eks-lab in the org
• Push everything from cbc-cloud-aws-eks-lab/ into it
• This is the canonical "this is what a fully populated CBC repo looks like" example

• Use MIGRATION-CHECKLIST.md and Part 14 of the playbook
• Prioritise per the P0–P4 matrix in the checklist
• Announce each migration on WhatsApp + LinkedIn

• Click "Use this template" on cbc-repo-template
• Follow TEMPLATE-USAGE.md — takes 5 minutes
• Reference CBC-REPO-PLAYBOOK.md for anything unclear

Every choice in this package traces back to three principles:

1. Every repo sells all three CBC arms — Learning Platform · Large Tech Community · Freelancing & Earning Platform. No repo is a dead end for the other two.
2. Zero friction for the team — the template ships every boilerplate file, so publishing a new repo is 5 minutes of find/replace, not 5 hours of decisions.
3. Brand consistency by construction — the mandatory 6 sections and the copy-paste blocks in Part 8 of the playbook are guardrails, not suggestions. Ship them verbatim, and every repo feels like it belongs to one platform.

• 📧 Email: [email protected]
• 📱 WhatsApp: +32 471 40 89 08
• 🤝 Escalation: Sangeetha B, Director – Partnerships

CareerByteCode — Learning Made simple
🌐 www.careerbytecode.in · 📧 [email protected] · 📱 +32 471 40 89 08

© 2015–2026 CareerByteCode · a platform by Cloudnloud Technologies SRL, Belgium.