[Evergreen-web-team] editor proposals

[Rogan Hamby]

At the last web meeting I volunteered to start brainstorming an
organizational scheme to the website.  As I promised this isn't a proposal
but hopefully a launching point for discussion.  I've been looking at both
the old and new site and obviously the Evergreen site has more evolved than
been designed.  (No intelligent design jokes please.)  I waited to send
something until the new site was out because I thought that would be less
confusing.  But thanks to Ben's hard work that's where we are now.

There has been an effort in the past to blend the web site and the wiki
together and I think everyone doing that were too good at the task and it
caused occasional confusion and issues.  And I think as we talk about
content we have to talk about the WIKI as well as the web site and having
editors who review and solicit content for both where appropriate.

This may not even be the type of approach we want to take but we have to
start the discussion somewhere.  So, proposals for editorial roles based on
content and organization:

Editor in Chief - Depending upon the number of volunteers involved on the
site this person may or may not also be the managing editor.  This person
needs to liaison with the Oversight Board to make sure the site reflects
the community appropriately and things are properly coordinated.

Managing Editor - On a newspaper the managing editor actually makes sure
the paper gets out every day.  In our capacity the managing editor needs to
be a bit like a release manager - they are making sure that the editors are
doing their jobs and greasing the wheels.  Furthermore they are ultimately
responsible for layout, making sure things are logically organized, looking
at usability issues, and that some static content gets updated
appropriately for the mailing lists, IRC information, etc....

News Editor - This person would be in charge of the blog, soliciting
content and making sure that outside sources are linked to or highlighted
correctly.  I had to think about the newsletter when thinking about this
role and realized I don't see it archived here.  This person would handle
most timely things including the calendar.

Section Editors - These would need to do more of the macro (content) and
micro editing (punctuation, speling, grammar).  Each of these would be
responsible to breaking out content on the web site and WIKI and working
with the managing editor to make sure it's accessible in a reasonable way
and organized as intuitively as possible.

Possible sections:

   -

   Documentation (self explanatory)
   -

   Advocacy (about us, FAQs, installation maps, this is an area I think we
   could do more in as the oversight board has discussed over the last 8
   months or so).   Heck, I'd like to see things like sections "Evergreen for
   Public Libraries", "Evergreen for Academic Libraries", "Evergreen Success
   Stories", etc...  I could easily see this becoming several sub sections.
   -

   Code - There is a big need to have a technical presence on the blog,
   especially reviewing code related sections of the WIKI.  This includes much
   of the contribution section though I'd like to see language changed since
   contribution can be in technical tasks, advocacy, documentation, etc....
    This person should also maintain the download page.  This could probably
   be broken up into several sub sections.
   -

   Above I listed the communication channels as static pages that the
   managing editor maintains but I could see that being more active and being
   it's own section with issues brought up in IRC and email lists archived
   with detailed FAQs, folks being welcomed on the listserves, etc....  Some of
   the ideas brought up with tutorials to Google Hangout would dovetail very
   well into this.





-- 

Rogan Hamby, MLS, CCNP, MIA
Managers Headquarters Library and Reference Services,
York County Library System

"You can never get a cup of tea large enough or a book long enough to suit
me."
-- C.S. Lewis <http://www.goodreads.com/author/show/1069006.C_S_Lewis>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-web-team/attachments/20130909/e78590d5/attachment.html>