[wp-docs] The main page.

[Mika A Epstein]

There's only so much you can do to make certain things "simple enough".

My concern with your changes was how MUCH data we had up there. People don't read.  They just don't, not for WordPress, and not for their jobs (if I go postal, it will probably be over people telling me that they didn't read the documentation because at 6 short sentences, it was too long).  Even right now, we do have too much going on.

So in my eyes, the question we need to answer is: Why do people go to the FRONT page of the codex?

I would say it's because they've heard about WP and they either want to see what sort of documentation there is at all before installing, or they have their first question about it.  So the first section should be how to install, how to add themes/plugins, how to get help.

Next we have the 'how do I use this?' set.  So we need a section on how to make posts and pages and links.  Also how to use widgets in themes.  In fact, something for a basic "this is how a theme works, this is how you can edit it." WITHOUT touching any code.

Finally you have the creationists (not those, the ones who wanna write stuff).

People who make plugins and themes already know how to Google.  People who want to learn to do that, though, should have a quick "this is how you make A theme. This is a child theme." and a plugin one.

But after that, we're getting into heavy lifting, and there's really not a perfect way to avoid learning code and how to read technical docs to learn things. We shouldn't lower the bar, but we should build some stepladders so they can climb up and join us :)

On Aug 26, 2011, at 1:14 PM, Spencer Hill <spencerhill at theportlandco.com> wrote:

> Hey everyone. This is Spencer Hill, the person who made the edits to the front page.
> 
> I apologize for the late introduction and for any inconveniences I may have caused. Thanks to mrmist I realized my post on the "Discussions" section of the "Main Page" wasn't the correct place to hold discussions... about the main page. Heh.
> 
> I've had the opportunity, now, to read through all of the threads and, if my opinion is valued here, I agree with most of the feedback. Before I note anything else though I thought I would include the note I put on the discussion for the main page as I assume only mrmist was able to review it before the constructive criticism of the changes:
> 
> "I've spent several hours today revising the Main Page and a few of a subsequent pages and I wanted to make some notes, comments and requests to the community.
> 
> First, I've reorganized the Main Page to include descriptions for each section. This will allow future users and contributors greater ease while navigating this codex.
> 
> Secondly, there are many similar articles and landing pages throughout the codex that leave users and contributors confused or following links in circles and down rabbit holes. I want to encourage and plead with fellow contributors to focus on condensing and organizing all subsequent landing pages and articles according to the Main Page. That way we don't have three "Getting Started" sections and information that's geared towards developers mixed with information that's geared towards absolute beginners who have no interest in programming WordPress.
> 
> Lastly, I'd like to suggest the following structure improvements for the codex:
> 
> Main Page displays a title and description, as well as a few popular quick links to all of the primary areas of the codex. By selecting section title, the user should be redirected to a dedicated page for that section. This will help prevent the Main Page from becoming a confusing conglomerate of links.
> Each section's dedicated landing page should include a more thorough description and a list of links beneath each of the following section titles "Resources", "FAQ", "Popular Topics" and "Training & Documentation". These sections should not cross pollinate by sharing links among each other.
> For example: If a link to a PAGE under FAQ happens to contain information that is related to some of the other sections, fine, users can certainly include links to these others sections when it's within content on a page. But users shouldn't put these links in the links list beneath each of those sections.
> Well, those are my thoughts. Hopefully they all make sense and are on the same track as the rest of the community. Though I suppose some may object, but let's get the conversation rolling. I've got clients who want to learn how to use WordPress and I'm tired of rewriting training materials and reshooting screen casts for every client! ;)"
> 
> Now that I know the proper place to hold discussions about changes to the wiki you guys can count on me sharing ideas and joining the discussion here before making any serious changes to the front page.
> 
> That being said, I hope you guys weren't too rattled by my changes but rather that it sparked an important conversation so developers and non-developers alike can find the codex useful and helpful.
> 
> One last note, regardless of the content or structure of ESMI's layout, it's lacking clarity for people who are not developers. We have to provide a safe location for people who don't know, understand or care about WordPress' functions, installation, etc... to get their information without being slammed with loads of technical terms, FAQ's and links.
> _______________________________________________
> wp-docs mailing list
> wp-docs at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-docs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.automattic.com/pipermail/wp-docs/attachments/20110826/c58cb177/attachment.htm>