Post hoc ergo propter hoc: approaching and defining support goals
Breaking out from the Codex thread below – and using, inter alia, Siobhan’s comment as a starting point, let’s get some outlining goals going on:
- A clear division between developer docs and user docs
- A self-contained, concise yet complete landing page for the user coming in
- Plot a useful journey for different people who want to “learn WordPress”, from beginner to ninja/rockstar/whatever the individual wishes to be - (imho this needs to both respect that not everyone will want to do everything, nor indeed have the nouse (everyone is unique, and has their own strength), whilst respecting and encouraging the learning process – it’s a balance to ensure that eveyone gets to where _they_ want to be, with the best tools and information not where we, or anyone thinks they should be. Without passion, we’d not be here – I think at this point I’m merely restating what everyone thinks and goes without saying, but, let’s just get it documented.)
So, there’s some overlap and a meeting point with the core contributors‘ handbook, and this is where we need to be super disciplined. I know so many of us, @ipstenu, @andrea_r, @lorelle, @esmi (and everyone here, and more!) have been mulling this over for a good deal of time, so I’m just very much about grouping the discussion and the years of thought and care into a thread.
Let’s go!
andrea_r 11:25 pm on August 5, 2012 Permalink |
Probably first point is to identify actionable items, break ‘em down into manageable tasks and start the delegating / voluntold process?
I;d say first thing is to get the wp.com useful docs over here with a first pass at editing to replace terms, then link it up to the main.
hanni 11:28 pm on August 5, 2012 Permalink |
sidenote on wp.com docs – @andrea_r I’ve just grabbed an export of en.support.wordpress.com. Where’d you like to start gathering these? A category here?
Ipstenu (Mika Epstein) 11:37 pm on August 5, 2012 Permalink |
I wish we had a CPT! Maybe @nacin will give us a sub-site make.wordpress.org/support/handbook?
Edit! Make a /handbook page, import there!
hanni 11:56 pm on August 5, 2012 Permalink |
OK, we had some quick ad-hoc “IRL”conversation action going on here with @ipstenu, @nacin, @otto, @jane and others – noting:
hanni 12:05 am on August 6, 2012 Permalink |
Done! @otto helped me mass move everything to under “Handbook”. Falling timber, but it’s something.
andrea_r 12:14 am on August 6, 2012 Permalink |
Dang, you guys work fast – and yeah, something somewhere anywhere.
Ipstenu (Mika Epstein) 12:29 am on August 6, 2012 Permalink
We ran back and forth across the room and tackled Otto and Nacin … or something.
hanni 12:42 am on August 6, 2012 Permalink |
So, the general principle of restricting isn’t something you’ll ever see me getting behind, and, was careful to only export / import “published” pages so there is no sensitive anything, I have made the pages private whilst we do a very quick _ initial triage – otherwise 340+ pages is a bit overwhelming to just dump out there, so:
This is just for 72 hours, whilst we scrub. If we can do it before then, that’s great.
Siobhan 3:42 pm on August 6, 2012 Permalink |
Amazing – I go to bed and loads of stuff has happened! Is there anything I can do to help? Have some time to review pages tomorrow if needed.
Ipstenu (Mika Epstein) 5:38 pm on August 6, 2012 Permalink |
As soon as we can go through and delete the totally non-relevant .com stuff (like how to set up email/domains with .com etc), and remove the links to .com support, I think we can roll the pages out, have everyone comment, and figure out how to structure a ‘user handbook’
@hanni and I were talking about this with the Core Handbook, and she has a great idea for overviews.
If we can come up with big ‘header’ sections, like in a book, and lead people through what you need to know, then we can present a guided path.
So with WP Codex we should figure out what our ‘path’ is.
1) What is WordPress
2) Installing
3) Using
4) Extending (? Themes and/or plugins … maybe Personalizing)
5) Coding
And then the Coding one would be where we’ve got all that advanced function calls etc. Core can link back to the Core Handbook.
Ipstenu (Mika Epstein) 11:49 pm on August 6, 2012 Permalink |
Pages sorted and done. I have a draft post, but since the handbook doesn’t list them all, I asked @otto42 and @nacin if we could have the shortcode for child pages like they do on .com (and like the plugin in the repo) so we could just list ‘em.
hanni 11:52 pm on August 6, 2012 Permalink |
@ipstenu, you are a marvel.
Ipstenu (Mika Epstein) 11:50 am on August 7, 2012 Permalink |
A 4.5 hour flight with free wifi is amazing
Lorelle 4:55 pm on August 10, 2012 Permalink |
Wow, I duck into academia and miss out on all the fun. Is there a place to find all these? What can I do?
WordCamp PDX is coming up and some people have asked me to do a Codex unconference meeting during it. I’d love to tap into their brilliance and point them at specifics. The WordPress PDX Meetup team also wants more directions when it comes to how they can help with the Codex, especially after the very successful recent Codex events.
Awesome.