トトも

@ImpulseAdventure Please review this PR~

@nakkaya Please review this PR~

> Looks nice, but does this mean we have to create a new badge on [img.shields.io](https://shields.io/) if we want to add additional sections to the README ? ? They are...

@ocerman Please review this PR~

@hrvach Please review this PR~

@eclecticc Please review this PR~

The most easy to use variant would be markdown + github pages I'd say. Simply have all docs in `/docs/` or `/documentation/` with subfolders for the different topics. I would...

On that note, it would be beneficial to use the `project` tab to track the progress on this documention refactoring.

An additional strategy to consider is creating a separate repository for the documentation. Consider that the `avrdudes` organization is almost solely focused on, well, **AVRDUDE**, it won't have a problem...

With the separate repository way the following folder structure could be utilized: avrdudes `Organization`  ↳Documentation `Repository`   ↳Pages `Github Pages In Markdown Format`    ↳README.md `Documentation Home ( User )`   ↳Resources `Images,..`   ...