That run across the top of the page and are replicated on all pages.
- Projects/Software: Where we list the most prominent projects KDE produces:
- Plasma/Plasma Mobile (of course) with links to related tech, such as Kirigami, Halium, etc.
- Most popular projects of the moment (may change with time, as popularity shifts)
- Project of the month - a rotating project that changes every month (week?), so as to give fair coverage to a wider range of projects (?)
- Planet KDE
- Press kit - Include hi-res logos, photos, and other media for the press to use.
- Press contacts - People journalists can contact for information or who can route them to source of news (i.e. the board, a project leader, etc.). Also links to press mailing list for press releases and news.
- Get Involved
- Become a Contributor
- Events - This needs a better name; but basically, it would be a page for events where people can meet other KDE contributors, or where they can represent KDE (conferences, release parties etc)
- How to Donate
- KDE e.V. - Include information about vision, board members, legalese, budgets, etc.
- Community - Include description of community, links to wikis, IRC groups, etc. Also descriptions and links to international groups.
- FAQ - Maybe this should be it's own main menu item?
- "Store" - I am putting this in quotes because some people don't like the term "store". Personally, I think it should be up to what users usually call these things, and for them, this will always be a store.
- Gear - Whoever came up with the name for this is a genius. This is where people can buy mugs, apparel, pins, etc.
- Apps (?) - Could contain Flatpacks, AppImages of apps that can be installed on several platforms (GNU/Linux, Windows, macOS, etc.). Could also contain links to apps for PlasmaMobile, when things take off. Could also contain links to downloads of KDE-enabled OSes, such as KDE neon, openSUSE, Manjaro KDE, etc.
In the body of the page in the shape of buttons, lists, etc.
We want to help people quickly find what they are looking for. As KDE technologies is of interest to a wide variety of people with different needs, it makes sense to route them to different services and applications.
- End user - Would be user that come looking for Plasma for everyday use and end-use applications, like Kdenlive, Krita, Okular, etc. Direct to: app store and/or FAQ (?)
- Contributor - Or potential contributor: person who is or wants to be a user, and participates or wants to participate more actively with the community. Direct to: New users can be sent to wiki page how to help ("Get Involved" page). Registered users to services for reigstered contributors (Phabricator, Wiki, etc.)
- Business - Companies that want to work with use or with KDE technologies. Direct to: how to... a human? Someone who can find out how we can help them?
- Educator (?) - Not sure about this one, but as we have KDE-edu, it may make sense. It is for teachers, principals, students, parents, who want to use KDE apps for educational purposes. Direct to: Subsection of app store form where they can download educational software-
Boxes that shows feeds with links from other sources.
- Releases - Shows up to date information of releases, such as Plasma, applications, frameworks, etc. Headlines are links to full announcement.
- Dot - Shows headlines from dot.kde.org. Headlines are links to full story.
- Twitter (?)
The above is condensed from T7847 and discussions held on the matter during the sprint. Check to see if there are any glaring absences or mistakes.
WARNING: NO BIKESHEDDING AT THIS STAGE PLEASE
For example, at this moment we don't care whether the place where users can download software should be called "Store", "Shop", "Repository" or whatever. We will iron those kind of things out when we have decided on the actual pieces we want and their content.
Also, this will obviously change over time. Let's get the basics done and not worry too much if the structure of the site does not fit each of our exact ideal expectations.
To avoid having this stretch off into infinity, I'm giving this task 48 hours for discussion and suggestions, and then we are moving forward an closing the task.