Look ma! A FAQ!

[rho]

Thanks to the hard work of the FAQ team, the FAQ is now at a stage that's close to "completion". I use the scare quotes deliberately, because it's not anywhere near completion, and there's still a whole lot that needs adding and what have you. What's there at this point is pretty stable though, so I'm saying that we've now reached FAQ 1.0.

If you have time, go take a look at the FAQ and comment here to let me know what you think. We've done our best to make the FAQ clear and easy to read and to navigate, and I'd be especially interested to know how you think we've done with that. I'd like to know what you think we've got right, and I'd also like to hear any constructive criticism you have on things that you think we've got wrong.

This is also the place to comment if you find any typos or factual inaccuracies in the FAQ. We've had at least two pairs of eyes looking over every FAQ to try to cut down on errors, but it's inevitable that some will have slipped in. If you find any, comment here, and we'll get them fixed when we get a chance.

Comments

[ephemera]

http://www.dreamwidth.org/support/faqbrowse.bml?faqid=5
Would it be worth adding a paragraph to mention email posting for paid users, and client software with links to relevant FAQ pages for those methods?

******

FAQ page for email posting, especially as the email command bit hasn't yet been LJ-stripped, and I know at least two people who assumed that that meant it didn't work yet.
http://bugs.dwscoalition.org/show_bug.cgi?id=721
http://www.dreamwidth.org/manage/emailpost.bml?mode=help&type=headers

******

http://www.dreamwidth.org/support/faqbrowse.bml?faqid=101&q=email
visible work-in-progress in the final paragraph, with a log in date of a week ago. Is this work in progress, or did it slip off someone's radar?

******

http://www.dreamwidth.org/support/faqbrowse.bml?faqid=33
"There will be a few instances where we won't be releasing our code; one is that we're keeping the code for our site scheme (the look and feel of the site) closed-source so it's unique to us. However, we want these exceptions to be few and far between and will provide our reasoning in all cases."

Suggestion - re-order the sentence so it's
"There will be a few instances where we won't be releasing our code. We want these exceptions to be few and far between and will provide our reasoning in all cases. For example, we're keeping the code for our site scheme (the look and feel of the site) closed-source so it's unique to us."

Suggestion 2 - regardless of sentence structure, where are they going to provide reasoning? Link to the community or FAQ section?

Suggestion 3 - is it just the default site scheme, all the colour shifts of Troposcopic, or all the site schemes? 'look and feel' is a bit vague.