Open StevenDufresne opened 9 months ago
I think the word "Help Center" has emerged as the most common way to talk about this type of information.
"Help Center" can be confused with Support or the Forums, in the case of WP.org.
But I do agree with you that we need to start differentiating the type of documentation each repository has. So a tagline or an intro paragraph describing the type of information and who is it for, is doable.
FYI, the documentation in this repository is geared to non-developers
Maybe:
Another suggestion, "Learn how to use WordPress"
I would suggest the following ones:
There are several proposals that could be used, but because we already have "documentation" in the URL and the title, I think is better to add a tagline to the title, something like
Documentation / non-developer user guide
The tagline in the browser title is "We’ve got a variety of resources to help you get the most out of WordPress." so I tried that:
Desktop | Mobile |
---|---|
It's a bit long, but it works pretty well. Or maybe just "Resources to help you get the most out of WordPress."?
Yeah, I like "Resources to help you get the most out of WordPress." better. I don't think "we" should be used.
"Resources to help you get the most out of WordPress."
It sounds good, but I feel it still needs clarification that they are non-dev/no code resources
WordPress.org has a lot of different types of documentation in many different places. We have this product documentation, developer documentation, process documentation (handbooks), etc..
When I arrive on
/documentation
, it isn't clear what documentation I'm about to see. For me as a developer, I think of WordPress as a developers ecosystem and therefore assume documentation is code documentation.Although there are probably larger changes to how we talk about documentation, could we add a simple clarifying statement to contextualize what I'm going to find on this sub site?
If this is better clarified in newer designs, feel free to close.