For example: it would be useful to have readily-accessible information on the syntax and more clarity on how to use different features. I'm used to worse documentation than this and I managed to hack my way through after a few questions asked, but it probably shouldn't be that way. Examples of syntax, direct examples of writing code X will have effect Y, that sort of thing. If I understood a little more of how it worked (a matter of time and some explanation) I'd be happy to help out with this. Thoughts? Ideas? Something to put on the back burner?
-
- 餓狼霊 (
electricdog) wrote in 
lj_userdoc,
Documentation for styles and variables thereof
For example: it would be useful to have readily-accessible information on the syntax and more clarity on how to use different features. I'm used to worse documentation than this and I managed to hack my way through after a few questions asked, but it probably shouldn't be that way. Examples of syntax, direct examples of writing code X will have effect Y, that sort of thing. If I understood a little more of how it worked (a matter of time and some explanation) I'd be happy to help out with this. Thoughts? Ideas? Something to put on the back burner?
-
New FAQ: How do I deal with spam?
This FAQ is meant to tie together all of our spam-related information, currently spread over several different categories. Ideally, I'd like to have…
-
Chart comparison for owner/maintainer/moderator?
Would it be useful to have a table in 225, 330, or 332 (or maybe all of them) showing the differences between what an owner, maintainer, and…
-
FAQ 82
FAQ 82 lists the URL for a community incorrectly; they should show as user URLs now. Thanks!
- Post a new comment
- 7 comments
- Post a new comment
- 7 comments