The-DevOps-Daily / The-DevOps-Daily/devops-daily

Learning paths: curated multi-week journeys

Open
#1,164 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
1.1k
Forks
392
Avg merge
5h 8m
Merged PRs (30d)
121

Description

Summary

Bundle the existing 600+ pieces of content into curated sequenced journeys. Each path is a JSON config pointing at existing content in a specific order. localStorage tracks per-user progress, no backend required.

Paths to launch with

  • DevOps in 30 days — fundamentals to basic deployment
  • Kubernetes in 14 days — from pods to production
  • SRE fundamentals — SLOs, error budgets, on-call, postmortems
  • Platform engineer track — IDPs, Backstage, golden paths
  • GitOps crash course — Argo CD, Flux, repo structure

UX

  • /paths — index of all paths with difficulty + duration
  • /paths/{slug} — path detail with ordered content list, progress bar, "continue" CTA
  • Each content page in a path shows "Step X of Y in {Path Name}" breadcrumb at top
  • localStorage tracks completed items
  • "Completed" badges + shareable social card when you finish a path

Data shape

content/paths/{slug}.json:

{
  "title": "DevOps in 30 Days",
  "description": "...",
  "difficulty": "beginner",
  "estimatedDuration": "30 days",
  "items": [
    { "type": "guide", "slug": "introduction-to-linux" },
    { "type": "exercise", "slug": "cloud-server-setup" },
    { "type": "simulator", "slug": "dns-simulator" }
  ]
}

Why

  • Solves the "where do I start?" problem new visitors have
  • Massive retention lift (users come back to continue)
  • Gamification with path completion badges
  • Zero new content needed, just config + UI

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the proposed content/paths/{slug}.json data shape and the /paths and /paths/{slug} entry points. Done means the listed learning paths can be browsed in order, progress is retained with localStorage, and completion is visibly reflected through the specified progress, badges, breadcrumb, and sharing experiences.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
content, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.