|
|
||
|---|---|---|
| .. | ||
| ascii-names | ||
| development | ||
| exporter | ||
| interfaces | ||
| media-player-classic | ||
| midra-layout | ||
| planning | ||
| pptx-reporter | ||
| releases | ||
| rundown-converter | ||
| templates/midra-layout | ||
| README.md | ||
| changelogs.md | ||
README.md
Documentation
Project portal · Changelogs · Development
Tools
| Tool | Start here | Reference and background |
|---|---|---|
| PPTX Reporter | Guide · Visual walkthrough | Report formats · Windows quick start · Portable quick start |
| Rundown Converter | Guide · Portable quick start | Corpus findings · Plan |
| Midra Layout | Guide | Resolutions and cropping · Device checks · Plan |
| ASCII Names | Guide | Changelog |
| Document Exporter | Guide | Changelog |
| MPC-HC Companion | Setup and development | Changelog |
Shared resources
- Development: setup and checks, CI and coverage, builds and portable releases, application artwork.
- File and device contracts: interface index, including versioned examples and compatibility rules.
- Starter files: Midra Layout templates in templates/midra-layout.
- Release history: v0.3.0 notes and per-tool changelogs.
- Future work: ideas, program task list, Flipper Link feasibility.
Where documentation belongs
Keep each tool's guide, plans, screenshots and changelog in its named folder.
Shared contributor instructions live in development/, historical release notes
in releases/, and cross-tool research in planning/. The Companion setup guide
stays beside its module source.
Keep save/export contracts and their versioned examples in interfaces/, and
reusable starter documents in templates/. These files are also used by tests;
update incoming links and code or packaging references whenever a document moves.