Stefan Witschel

I think what is needed are clear types of documentation like Quick Start Guides, Concepts/References/Informations, Tutorials & How to Guides. We should have more top level categories like Quick Start,...

Not sure where to document so I do it here. My proposed documentation structure: 1. We need a comprehensive **Getting Started Guide** : https://thin-edge.io/#!get-started is not enough and the How-Tos...

Difference between Develop vs Extend like you assumed: Develop/Contribute to thin-edge (core) project. Extend => Use APIs to develop Plugins, unofficial Extensions (not part of the thin-edge.io core project).

@didier-wenzek What is your proposal? How should set up the new documentation without interfering the old one? should we create a new branch? PR?

Ok, I think we did it right so far. I forked the thin-edge repo and made make changes to my forked repo in a new folder called "new_docs" so we...

To clear some confusion about this PR. This is a proposal how to structure the new documentation - a working document. It is not yet a summary nor a TOC....

Hi @hansb001 , Your points are good and valid I guess but actually matching all concepts guide. This issue is for the concepts **overview** part of the documentation so my...

If you are an expert in thin-edge you don't need to read the concept **overview** about thin-edge I guess because you already have that knowledge. For other concepts the level...

@didier-wenzek I could live with that but at least edge computing must be roughly explained and be part of the overview.

From my side everything is provided! Is there anything missing so this issue can be worked on?