[RWP] ok people, lets fix the reaaccess site

[Derek Lane]

I'd be willing to help in  any way, if it let the reaaccess team spend more time 
developing

  ----- Original Message ----- 
  From: Bryan Smart 
  To: Reapers Without Peepers 
  Sent: Tuesday, December 21, 2010 6:04 PM
  Subject: Re: [RWP] ok people, lets fix the reaaccess site


  Right now, the site is a Wordpress. That's fine if a single person wants to maintain the entire site. It isn't as easy for a team of people to collaborate on a Wordpress site, though. The best that you can do is to add several people as authors, and give them permission to post articles in certain areas of the site. They can't update any of the site structure, or perform any other large scale edits.

   

  It's obvious that the ReaAccess people don't have the time to work on the site. They can either let the site be another obligation that they can't meet, dragging them down, or they can deligate part of the work to others in the community. In the first case, the site will only be updated irregularly and in spirts, if ever, and it will be harder to attract new users to your project. If the second, then you need to put a system in place for deligating the tech writing projects.

   

  If you have the time to rearchitect, then it would be better to create a site based on Drupal or Joomla. That would give you lots of options for passing out responsibility of different areas of the site to different people. You can, for example, create authors that can only write in their assigned section. However, you can also create users to serve as editors. Editors would be trusted users that can write or edit in multiple sections. They'd take most of the editing/approval/site admin tasks off of you, while not being able to edit the core functionality of the site.

   

  If you don't have time for any of that, then, at minimum, you need to create some users on your Wordpress site as editors, Give them assigned sections, such as FAQ, getting started documents, etc, and add widgets to the sidebar and archive references in the main body of the page that would display content that has been created in their sections.

   

  Anyway, unless you're making lots of money, you can't come up with resources to do it all internally. You either must learn to spread the work around, properly supervised, or get buried under the mounting to-do list.

   

  Bryan 

   

  From: rwp-bounces at reaaccess.com [mailto:rwp-bounces at reaaccess.com] On Behalf Of Derek Lane
  Sent: Tuesday, December 21, 2010 4:36 PM
  To: Reapers Without Peepers
  Subject: [RWP] ok people, lets fix the reaaccess site

   

  The developers of rea access are some amazing people.  Their work is solid, and, at least for me, itlets me be very productive in tasks from  tracking/mixing to mastering/restoration.

  The problem is, the reaaccess site is  broken.  So it keeps the community from growing due to the fact that the actual project isn't available as a link, anywhere on the site.

  If someone could  fix reaaccess.info, I'd appreciate it.



------------------------------------------------------------------------------


  _______________________________________________
  RWP mailing list
  RWP at reaaccess.com
  http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://bluegrasspals.com/pipermail/rwp/attachments/20101221/fc5fb9c8/attachment.html>