Improve the structure of the documentation
The Problem
Currently, the sidebar looks like this:
It is just a bunch of random tutorials, that somehow relate to KDE. This makes finding the relevant information for the developer hard.
Possible Solution
I propose splitting all the tutorials to the three categories (wording and order may be different):
- Relying on KDE Technologies
- Extending KDE Technologies
- Building KDE Technologies
"Relying on" would contain all the things the developer would like to know, when developing a cross-platform or Linux app using KDE Tech:
- Kirigami
- Getting Started (btw, very weird section, it's about building a desktop app using KDE Frameworks, right?)
- Configuration (KConfig and KConfigXT)
- IPC via DBus
- Session Management
- KArchive
- Desktop file
- KAuth
- KIdle (detecting system idle state)
- Akonaldi
- Concurrency
- Spell checking
"Extending" section would contain all the things the developer would like to know, when developing an extension for the official KDE Software:
- Sensors for System Monitor
- Dolphin Plugins
- KCM subsection from the present configuration section
- Plasma plugins (KWin Scripts, Applets etc.)
"Building" section would contain all the things the developer would like to know, when developing official KDE Software:
- Icons
- Plasma Mobile
- Flatpak distribution
Some things would eventually overlap, but I think in these cases separate tutorials with deduplication via the cross-linking would be a good solution. The idea is that the developer for each section may know the stuff from another section: "Relying on" dev shouldn't know anything prior, "Extending" dev may know something about "relying on" to be able to extend, "Build" dev may know about extending and relying on to be able to build.