{"slug":"data-formats-etl","sectionId":"data-foundations","title":"Data formats, ETL, and pipelines","summary":"CSV, JSONL, Parquet, schema evolution, idempotent pipelines, lineage, backfills, and data quality.","focus":["format tradeoffs","ETL vs ELT","schema drift","late-arriving data"],"featureIdea":"Pipeline simulator showing schema drift, backfills, idempotency, and late data.","status":"shell","requiresBackend":true,"tags":["etl","data-quality","parquet"],"locale":"en","sectionTitle":"Data Foundations","statusLabel":"shell","backendLabel":"backend needed later","pagePath":"/learn/data-formats-etl","apiPath":"/api/learning/data-formats-etl","selfCheck":["What is the core job of \"Data formats, ETL, and pipelines\"?","Which common mistake would break a production implementation of this topic?","Which inputs or limits must be validated before the interactive feature ships?","What is the smallest test that proves the future implementation behaves correctly?","When does this module really need backend compute, and when is a UI simulation enough?"],"implementationNotes":["Start with one focused feature, not a full course inside one page.","All public inputs must be typed, bounded, and covered by reject-case tests.","If a model, dataset, or job is added, document source, license, limits, and fallback.","The interaction must explain the topic rather than serve as decoration."]}