Skip to content

Latest commit

 

History

History
69 lines (50 loc) · 3.64 KB

File metadata and controls

69 lines (50 loc) · 3.64 KB

Documentation

Prototype — educational use only. These docs describe a reference implementation. Code patterns and APIs may not reflect production best practices in all cases.

Process documentation for building Angular 21 + PrimeNG atomic design systems, paired with findings from a working prototype simulation.

Start Here

Read 00-quickstart — it takes 2 minutes and routes you by role.

Process Guides

Foundations (read first, in order)

# Doc What it answers Read time
00 Quickstart Where do I start? 2 min
01 Atomic Hierarchy What are atoms, molecules, organisms? 10 min
02 Maturity Stages What quality level should I target now? 10 min
03 Project Structure Where do files go? How are they named? 8 min

Building (read based on your current work)

# Doc What it answers Read time
04 Parallel Development How do design and dev work together? 8 min
05 Token Pipeline How do design tokens flow from Figma to code? 10 min
06 Tooling Landscape Which tools should we adopt and when? 8 min
07 QA Per Atomic Level How do I test and certify a component? 12 min
08 PBI and BA Guide How do I write PBIs? Where does the BA add value? 12 min

Reference (read when a specific question arises)

# Doc What it answers Read time
09 Angular Direction What Angular 21 features affect my architecture? 10 min
10 De-risking What risks will I hit and how do I handle them? 8 min
11 Implementation Tips What are the practical gotchas and solutions? varies
12 Decision Guides How do I make key architectural and process decisions? 15 min
13 Designers Guide How does a designer work in this process? 15 min
14 Replication Guide How do I replicate this approach on a new project? 12 min

Prototype Findings

Results from a simulated prototype build using this process.

Visual Reference

Specification

  • design-spec.md — Simulated Figma design handoff values (includes prototype extensions for loading/error/empty states)

Results

Next Steps

Reading Path by Role

  • Developer (new): 00 → 01 → 02 → 03 → 11 → explore src/
  • Developer (prototype): above + 05 → 07 → 10
  • BA / Product Owner: 00 → 01 → 02 → 08 → 10 → 12 → acceptance-criteria
  • Designer: 00 → 13 → 01 → 05 (tokens section) → 04 → component-catalogue
  • Evaluator (deciding whether to adopt): 00 → simulation-report → 02 → 10 → 12
  • Tech Lead: 00 → 01 → 02 → 06 → simulation-report