Skip to content

Repository Audit

Current Snapshot

  • Total files in uploaded archive: 367
  • Markdown files: 175
  • C source files: 76
  • Shell scripts: 20
  • Header files: 16
  • Device tree source files: 11
  • Python scripts: 5

Existing Strengths

  • Labs already keep code close to the related learning topic.
  • Daily logs preserve the original learning timeline.
  • Notes already contain many reusable concept explanations.
  • The repo is already mostly Markdown-based, so MkDocs migration is low-risk.

Do not move everything at once.

  1. Add MkDocs site scaffold first.
  2. Keep docs/notes/ and docs/labs/ intact.
  3. Copy learning-log/ into docs/logs/ for MkDocs navigation.
  4. Add topic index pages that link existing notes and logs.
  5. Normalize lab folder layouts gradually.

Items to Review Later

These are not blocking Phase 1, but should be cleaned up later:

  • Missing or skipped Day logs in the uploaded archive, such as Day 29 and Day 46.
  • Some filenames appear to have typos or unusual extensions:
  • docs/labs/day28/driver-ci,yml
  • docs/labs/day35/myadc-iio-dts
  • docs/labs/day36/test_iio_buffer,sh
  • docs/notes/dual-bus-integrarion.md
  • Some older labs are single Markdown files, while newer labs are directories.
  • README is very long and should eventually become a concise repo landing page, with detailed content moved into the MkDocs site.