**Motivation**
KDE documentation is not its shining star, in my humble opinion. However, it is the backbone of all good software. Documentation is the bible of a software, and if KDE were to reach simple users, its script should make sense to them. It must also be easy enough, where non-gifted people like me who can't code can easily contribute to. As of today, if I go to the documentation section in Get Involved page, my head spins. It shouldn't be that complicated.
**Plan**
Mozilla has already done all the heavy lifting for us. Just go to the all new, [[ https://developer.mozilla.org/en-US/ | MDN website ]]. Look how shiny and beautiful it is!
However, my main focus caught on, how easy and fail proof contributing to MDN is now. All of its contents are in a giant [[ https://github.com/mdn/content | git repository ]]. Anyone can make a change as a pull request in the git repository. Maintainers review the pull request, and as soon as it is merged it becomes live in the main website. How cool is that?
Just imagine, a novice users find a typo in the documentation, and he/she is capable enough to open a GitLab account. Just by opening a PR, he/she can change KDE documentation. That is just the beginning.
**Benefits**
Major benefits I can think of are,
# There will be a central documentation page that will have all the KDE Plasma, and application documentation. People can just search and find what they need.
# Contents would be in Markdown format, which can easily be converted to offline documentation bundled with the app (Even R program has that functionality).
# Even moderately skilled users who can write will be able to contribute to the project.
# As each of the changes will go through some review, it will most likely be safe.
# Mozilla has laid the foundation for MDN, it will be supported for decades.
**Alternative**
The only alternative I can see is the [[ https://wiki.archlinux.org/title/Main_page | Arch Wiki ]]. However, there are two barriers,
# Arch users are advanced Linux users who write quality documentation. KDE is planning to be a software for all.
# It won't have the mentoring that PR of GitLab will have.
**Plan**
As Mozilla is a complete open source white knight, it is possible to follow MDN [[ https://github.com/mdn/content | guide ]] to make a variant for KDE. All the rendering is done by a piece of software called [[ https://github.com/mdn/yari | yari ]].
**Additional Steps**
# Create a process that help old documentation to be converted into the new process
# Keep room for special processes for standalone big projects (Krita, Kdenlive)
# Separate documentation for users and developers, as new developers need hand holding too!
**Community**
It will be the biggest community collaboration of KDE. Everyone will contribute and nurture users who can't code but write poetry in documentation.
**Risks and needs**
This endeavor will not be easy in any way. It will take massive planning and execution to run this get this project up and running. It will solve one of the KDE's biggest problem and solve it in a ridiculously beautiful way. Problem I can think of are,
# Special skill for developers to maintain this project,
# Maybe collaborate with Firefox developers to make this a project for both Firefox and KDE,
# Creating a centralized website, backend, and infrastructure won't be easy.
**Champion**
And thus, I have reached the weakest part of this proposal. I am a FOSS user, advocate, and avid KDE lover. Although love might help you to move mountains, it can't teach you code. I would not be able to help out in this project in any meaningful way at the beginning. I am hoping, someone who can see and share my vision, will be able to take this great labor, and sail through it.
**Interest**
Even if you find this whole proposal hilarious, can I have your support?