Historically, I haven't had much to do with the
Editor Logs here at Everything2. Preferring, perhaps misguidedly, to use the
catbox as a transparent forum for my decision-making, I've never used this space to air my '
editorial philosophy' or chronicle my various projects unless my message was also a call to action directed at the userbase. It was along those lines that I staged
a tag-line contest here last year, and today I'm likewise going to appeal to your talent and energy. But I'm also becoming more sensitive to the need for a permanent record of my actions and initiatives, especially when they've become as collaborative and long-term as they have lately. It's been a busy month for me! Here are some of the things I've been up to that I hope you'll want to take part in.
E2docs wants you!
For the past few years, I've spent summers writing administrative and technical documentation in the oil and gas industry. I've learned that even engineers need things seriously dumbed down for them when they're first getting to know a new interface or instrument. Similarly, stuff that looks obvious to our veteran users is often anything but for the neophyte. E2 is unfriendly to new noders, but it doesn't need to be confusing too.
I am now the group leader of e2docs, which I've purged of all users who have been inactive for more than two months. We are beginning to update, improve and pare down our help documentation and I'm inviting you to be a part of it!
Specific goals:
- Fine-tune Everything2 Quick Start until it is as clear and tight as possible and establish it in Everything2 Help as the first thing every newbie should read. (Already made some great progress on this since the log was posted! Check it out!)
- Improve our how-to material for HTML in write-ups. We have a mess of these nodes right now, but they need to be pared down, consolidated and combed for errors and omissions. For example, E2 has been able to handle tables for some time now, but there is currently nothing that tells noders how to add them to their write-ups.
- Bring all documentation up to date. Among other things, this means it reflects the new Drafts system, accurate level power benchmarks, and omits mention of old or defunct features.
- Keep it simple, keep it short or just don't keep it. If anything can be more concise, make it so. If anything needn't exist, ready the potassium chloride.
When all is said and done, we should have an Everything2 Help that reflects our improvements, directing new users to fewer and better write-ups.
If this interests you, please join us at e2docs. Don't be discouraged if you are not a Content Editor and cannot edit documentation directly! You can always use Drafts to show me your improvements and I will promptly replace Virgil's versions with your own. If you're making largescale changes, I can probably just hook you up with Virgil's log-in and let you have at.
Everything2 First Contact
Lately some other users and I have been brainstorming ways to attract new contributors to Everything2. New Write-ups is far from inactive, but I don't think I'm alone in wishing for a steadier influx of unfamiliar faces. There are a lot of creative minds out there who'd benefit from the increased exposure Everything2 can offer their content, but many of them have yet to discover us. To this end, newly-minted editor misterfuffie recently spread the good word guerrilla-style with homebrew bumper stickers and Monkeylover has seeded his local library with some Everything2 bookmarks. I've decided to join the party with a slightly more personalized approach.
I've been combing the blogosphere for writers whose work, while very strong, isn't attracting much (or even any) notice. Often this material would clearly thrive here – these days even isolated blogs are full to bursting with film and book reviews, accounts of unique experiences and powerful creative work. I've been responding positively to some of these posts and suggesting their authors consider showcasing some choice content on Everything2, where they might increase their readership and benefit from the feedback of others. With our copyright policy as strong as it is, it certainly can't hurt.
I haven't streamlined my 'approach' enough to provide templates or examples just yet, but I welcome you to follow my lead in reaching out personally to those you encounter who might find a place with us here and reporting back on your level of success.