ivorygates: (GEN WIKIPEDIA)
[personal profile] ivorygates
Now that we're in Open Beta, we're getting to see how actual people who aren’t us are using the site, and this is letting us know how we need to revise our documentation and, of course, write more.

One of the things we're viewing with enthusiasm now that many of our tasks are no longer as time-critical is the opportunity to allow many more people to participate in our process. In the past several months, a lot of people have wanted to get involved in site documentation, but there were a number of reasons we couldn't accept all the help that was offered.

We have now remedied that small problem.

The new community [site community profile] dw_docs_training is intended as a dedicated work and training environment for new volunteers, experienced members of the docs team, and for anyone who's working on related aspects of the GUI, such as the site copy team and the site styles team. [site community profile] dw_docs_training will be a closed, moderated, response-screened community so we can concentrate on the training and support aspects of docs writing.

In [site community profile] dw_docs_training, we'll expect you to write material off a supplied prompt and we'll the result in the community for critique. To ensure the critiquing process remains useful and focused, your sample exercises will be re-posted by one of the community moderators, and all comments will be unscreened at the same time, and only when everybody who needs to comment on the entry has commented.

Your material will be judged by three criteria: accuracy (does the site behave in the fashion you indicate?), clarity (can an inexperienced or confused reader understand what you've written and follow any directions included?) and conformity with the Dreamwidth style as laid out in the Manual of Style.

If you are participating in the community as a proofreader or copyeditor, the procedure you'll follow will be similar, except you won't be posting entries, you'll be commenting on the entries of others.

In addition to participating in [site community profile] dw_docs_training, all volunteers in training will be expected to read all of the FAQs. Not only will this give you a broad familiarity with the documentation, there are many places in which it hasn't yet reached perfection: this will be your chance to see if you can find errors.

You'll also need to familiarize yourself thoroughly with the Dreamwidth Manual of Style and the Dreamwidth Site Terminology, both of which can be found on the Dreamwidth Wiki.

The Dreamwidth Manual of Style:

The Dreamwidth Terminology Notes:

What we want out of this process, and we hope you want it too, is for you to be able to write a FAQ or other piece of site copy to site standard language, or (if you aren't one of our writers) to be able to review a piece of site copy, detect typos and other problems, identify those areas in which it does not meet the Dreamwidth standard, and prepare useful revision notes for its author.

We'll be posting the details of how to apply to the Docs Team here in [site community profile] dw_docs very soon.
[personal profile] rho
I have been neglecting you. Have kept having various things that I've meant to post here, but somehow never managed to find the time to be posting them. This is the result.

1. Site copy people! We have a fan! I received this in an email the other day:
I've just spontaneously squee'd at rah about the DW site copy and she says
you're the person to pass it along to. So forgive me if I become a little
incoherent here: god, I *love* it. Love it, love it, *love* it. *Wow* do I
love it. I click around to hunt something down and I wind up on a page
that's got information, it's got useful information, it's got clear
information, it sounds like it was written by a human being, and a helpful
and *knowledgeable* human being. (Also, and I've only just begun to
realize how hard this in particular must be to achieve, it doesn't make my
question sound dumb, and it doesn't make it sound like it'll be hard to do
whatever task it is I'm trying to do.)

It's, um, possible I may have clicked on a few links I didn't need just so
I could read a little more. Um, you know. As one does.


I know what we do can often be frustrating because it feels as if we're just invisibly moving things about in the background, with nobody ever noticing us or thanking us, so I thought I'd pass this on to you (with permission) in the hope that you all get as much of a kick out of it as I did. We're doing a kick-ass job, and I'm proud of what we've accomplished.

2. FAQ editors, if at any point you see a FAQ that we don't have yet but that you think we need, but that doesn't really seem to fit into any of the existing categories, please throw up a quick and dirty FAQ in the misc category, and then we can polish and categorise later, depending on what ends up there.

3. When you need to reference an example domain in any site text or documentation, use example.com, which is set aside specifically for the purpose. I've seen one or two people using website.tld, which I'd rather avoid because I don't think that's as obvious to non-technical people.

4. When we first went into closed beta, I decided that I'd keep membership here open, since the only people coming in at the start of closed beta would be people working on the site. We're now well into the stage of accepting users, and open beta is almost upon us. However, we've had a bunch of people join the comm and absolutely no problems so far, so I'm going to keep membership open for now, and revisit in the future if we do have any problems.

5. I'm lousy at tagging. 9 times out of 10, I forget to tag an entry, and on the tenth time, I can never figure out what tag to use. I've opened up tagging to all community members. If someone wants to go back through old posts, tag them, and come up with a coherent tagging system, I'd very much appreciate it. Once we have a robust tagging system in place, I'll probably restrict the creation of new tags down to community admins.

6. I'm fairly sure I had something else I meant to say, but I can't remember it. If I end up posting another entry in 2 hours, then I apologise.
chasy: (Default)
[personal profile] chasy
I tried copy editing four different pages and on all four, the [Save] button was grayed out. Does this mean someone is already proofing the page? Or is it something else?

Edit: And now it's not grayed out anymore...

Thanks, rho!
ivorygates: (Default)
[personal profile] ivorygates
When I post an entry to my journal I see:

Post an Entry

Updating journal...
Your update was successful. You can view your updated journal here.

And hey, what the fuck is up with the line: Updating journal... ???

Because it is annoying and confusing and the first time I saw it I thought the site was about to take a dirt nap. It doesn't mean the site is in the PROCESS of doing something. It's hard code somethingorother AND I HATE IT LIKE FIRE.
[personal profile] rho
Hot on the heels of introducing the site copy team, it's now time for me to introduce the copy editing team. Everyone, say hello to:

[personal profile] bohemianeditor
[profile] chasy_la
[personal profile] cheyinka
[personal profile] ivorygates
[personal profile] rainbow
[personal profile] ryan

Their job will be to go over all the text written by the site copy team and the userdoc team, and correct all the dumb typos we inevitably make. OK, all the dumb typos I inevitably make, and possibly one or two made by the rest of the team.

Copy editors, here's what I want you to be doing now:

I'm afraid you're going to be grappling with the translation system. I'm so very very sorry. There's a guide to it on the wiki that [personal profile] tajasel wrote for us, but here are the cliff notes:

* Go to http://www.dreamwidth.org/translate/edit.bml?lang=en_DW (I've given you the privs you need)
* In the top left frame, scroll down and select prf: no and upd: yes, then hit search.
* Select one of the pages in the bottom left frame to bring up a list of translation strings.
* In the list, select "edit" for one of the strings, then copy edit it, and select proofed.
* When you're done with the age, click save at the bottom.

In proof reading you should be checking for:

* typos
* spelling mistakes
* grammar and punctuation
* Manual of Style compliance
* correct use of terminology

(Please read through both of these thoroughly before you get started.)

If you see any problems with any of these, change them and mark the string as being proof read. If you proof read a string and see that it's fine as it is (hopefully most of them will be!) then mark it as proofed without making any changes. If you see anything that you think needs a more substantial rewrite, then don't update it yourself, but instead comment here letting me know which string you think needs rewriting, and what you think the problem is. We might revisit this if we end up with a lot that need substantial rewrites, but we'll go with this for now.

Above all, have fun with it, and don't be shy of contacting me if you have any questions.
Page generated Sep. 19th, 2017 01:40 pm
Powered by Dreamwidth Studios