Flashcard decks

Decks are the main unit of organization in the flashcard system. Each deck groups related cards and has its own study queue and progress state.

​

Pre-seeded decks

Starter decks are loaded from repo-managed seed files in backend/app/db/learning_content/. The deck set can evolve over time. Because of that, this docs site avoids locking itself to exact counts or names unless the product repo treats them as stable contract. The application UI is the source of truth for the current seeded deck list.

​

Creating a deck

Create a deck from the flashcards view. A deck generally includes:

• Title
• Optional description
• Track tag

​

Renaming a deck

Rename a deck from its deck settings UI. The new title is persisted through the backend.

​

Deleting a deck

Deleting a deck removes:

• The deck record
• Its cards
• Associated progress history for those cards

​

Track tags

Decks can also carry a track tag. In the current codebase, track values are used for filtering and grouping, but the docs should treat them as organizational metadata, not as proof that an entire product area is publicly supported. Examples include:

• kubernetes
• docker
• pulumi
• azure

​

Filtering by track

Track-based filtering narrows the deck list without changing the underlying study model.

​

Per-deck stats

Decks expose queue-oriented counts: