|A suggestion. Mature discussion responses tolerated.
||[Sep. 11th, 2001|01:22 am]
Since there are so many people who don't know much programming and don't know how livejournal works, but still want to help, it might be a good idea to develop some way of letting them know what they CAN help with and HOW.|
It seems like a lot of devs who are more "advanced" are doing "mundane" things because they can't find or don't trust newer or less knowledgeable people to do them, like us peons who are interested in LJ_dev but haven't contributed. Things like writing FAQs, organizing pages around the site, I don't know what, just non-programming things. It seems that there's a marked gap between developers and people who are interested in lj development, and that the gap is we don't know a thing about most of the topics thrown around here since they're highly lj specific, and we don't know how to get started learning and practicing this stuff so we can get to your level.
I bet a lot of us are at the level where we don't trust our programming skills or don't have many such skills, but we're still techy enough to be able to help manage a site in other ways. We just aren't sure what the ways are, and/or need someone to sort of show us the inner LJ ropes, give us permissions, and we're off.
I know there is a little bit of documentation somewhere about such inner workings of LJ and perhaps how to get in and edit stuff once you've volunteered, but it's hard to find. I can't find it. I may be hallucinating that it exists. But anyway, my point is:
-There's stuff for us to do, isn't there? Tell us what it is.
-Give us directions on how we need to do it (
such as "add this page, find a better way to organize these documents, etc, here is where all the stuff for X part of site is, here's how you get in, good luck).
-Tell us who to pass our work by for approval or who won't mind if we bug them with questions.
Also, my apologies if it's a matter of me just not looking hard enough for documentation that covers *ALL* of this, and if said docs are hard to understand, but if such docs exist, that's also an issue standing in the way of us helping out.