Skip to content

docs: add per-folder README guides - #2153

Closed
shrey160 wants to merge 1 commit into
cjpais:mainfrom
shrey160:docs/folder-guides
Closed

shrey160 wants to merge 1 commit into
cjpais:mainfrom
shrey160:docs/folder-guides

Conversation

@shrey160

Copy link
Copy Markdown

New contributors and agents had to read source to learn what each directory does. Several upstream docs are also stale, so folder-level guides provide a verifiable entry point next to the code they describe.

Add a README to each significant directory covering its purpose, the conventions to follow and the traps to avoid, plus docs/ as the committed home for fork-local documentation.

Highlights:

  • src/ and src-tauri/src/: the dictation spine, and the settingUpdaters trap where a missing entry silently desyncs UI state from Rust
  • src-tauri/: Cargo patch rationale and the packaging-identity checklist
  • tests/: states that Playwright runs without Tauri IPC and cannot verify app behaviour
  • scripts/: documents the maintainer-only catalog tooling

transcribe-libs/ is described as the generated, gitignored build output it is rather than as checked-in binaries.

Generated and vendored directories are deliberately left undocumented.

Before Submitting This PR

Please submit only one fix or feature per pull request. Pull requests containing multiple fixes or features will likely be closed.

Please confirm you have done the following:

If this is a feature or change that was previously closed/rejected:

  • I have explained in the description below why this should be reconsidered
  • I have gathered community feedback (link to discussion below)

Human Written Description

Related Issues/Discussions

Fixes #
Discussion:

Community Feedback

Testing

Screenshots/Videos (if applicable)

AI Assistance

  • No AI was used in this PR
  • AI was used (please describe below)

If AI was used:

  • Tools used:
  • How extensively:

New contributors and agents had to read source to learn what each directory
does. Several upstream docs are also stale, so folder-level guides provide a
verifiable entry point next to the code they describe.

Add a README to each significant directory covering its purpose, the
conventions to follow and the traps to avoid, plus docs/ as the committed home
for fork-local documentation.

Highlights:
- src/ and src-tauri/src/: the dictation spine, and the settingUpdaters trap
  where a missing entry silently desyncs UI state from Rust
- src-tauri/: Cargo patch rationale and the packaging-identity checklist
- tests/: states that Playwright runs without Tauri IPC and cannot verify
  app behaviour
- scripts/: documents the maintainer-only catalog tooling

transcribe-libs/ is described as the generated, gitignored build output it is
rather than as checked-in binaries.

Generated and vendored directories are deliberately left undocumented.
@shrey160 shrey160 closed this Sep 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant