Hello everyone, This issue is to discuss the upcoming website called **join.kde.org** that will act as the entry point for new and veteran contributors and guide them to the correct place based on their interest. It will cover all kinds of contributions from **code to design to documentation**. The idea behind the site is **not to replace existing resources** but give new contributors a **structured path** to access them with ease and utilize them to their best. --- ## Explanation of what the site is going to cover Right now the site will be organized around a few sections: ### Learn An introduction to KDE's learning and mentorship programs and routing people to the mentorship website. ### Add A section for contributors with paths based on interest like: - code - design - testing - documentation - translation ### Divulge This section will be for people who are interested in: - creating tutorials - outreach - knowledge sharing - creating blogs ### Work on a Project This section will be mainly for people who have already worked in open source and are experienced with working on projects. This will further be divided into: - **Work on a project**\ (directly jump into projects under work) - **Incubate your own project**\ (for people who want to integrate their own projects with KDE) ### Meet This will contain information about: - webinars - meets - forums - workshops - discussions - and so on ### Suggest Will cover: - bug reports - feature suggestions - feedback ### Read This section will contain blogs that will be from: - devs - event highlights - mentorship programs ### Explore KDE A section where people can simply explore the KDE ecosystem\ (Plasma, applications, initiatives, etc.) Basically just to get familiar with KDE. {width=900 height=570} --- ## GOALS The main goals of this project are: - Reduce the initial friction for new contributors - Provide clear contributor pathways - Improve discoverability of KDE projects and initiatives - Encourage long-term contributor engagement --- ## Discussion Currently the project is in its **initial phase** and the insights from the community are extremely valuable. Especially on: - whether the structure is fine or there needs to be any additions or removals - suggestions for improving new contributor experience - suggestions on contributor retention Any critiques, suggestions and discussions are more than welcome.