website audience adaption

User come to f-droid.org with varying expectations. I think website visitors can be categorized into these 3 main interest groups:

• (potential) users looking to get setup with F-Droid, find apps, get support, etc.
• app developers seeking to publish their app or run their own repo
• contributors requiring information such as documentation, packaging status, etc.

Right now f-droid.org holds information for all these groups mixed into one place. While this probably provides a good experience for contributors, I doubt it's easy to navigate for the other 2 groups, because it's too easy to find information that's "way too far down the rabbit hole". I think for F-Droid it would make sense to separate the user experience for end-users from the experience for developers and contributors.

eg. the Android project itself is in a very similar situation. They solved it by splitting their online experience into these 3 dedicated sites:

• https://www.android.com/ - for people/companies interested in buying Android devices, getting user support, etc.
• https://developer.android.com/ - docs/tutorials for app developers working on their own android apps.
• https://source.android.com/ - docs/code/collaboration tools for OS developers working on Android OS code.

We actually started with that already by setting up https://gitlab.com/fdroid/wiki Which is a great place for documentation contributor information.

So What I'm proposing is to move (if it's not already there):

• all documentation/faqs/etc. for F-Droid contributors gitlab.com/fdroid/wiki and monitoring info to monitor.f-droid.org (not translated)
• all documentation/faqs/etc. for app developers to the sub-path f-droid.org/developer and add a little portal page there (translated)
• all F-Droid users content (app listings, F-Droid install funnel, F-Droid donation funnel, User support + FAQs, news, press, about) to f-droid.org. (translated)