[Home-on-the-range] NFBk State Web Site

[David Andrews]

What do you mean "how is the login info."?

Dave

At 09:15 AM 8/27/2010, you wrote:
>Thanks for the info David! BTW, how has the 
>login info? Regarding accessibility, content 
>editing shouldn't be inaccessible given the 
>proper setup. It is also possible to set up 
>drupal to use wiki-style mark-up which very 
>simple. I was actually thinking about either 
>drupal or joomla because the ability to 
>integrate with CiviCRM to manage member lists, 
>mailings, events, etc. as well articles and 
>"generic" content. Sorry Floyd, I'm over here 
>coming up with software to automate the chapter 
>mailings too! Oh, well. We still love you. 
>Another note on CMS accessiblity. I know Plone 
>is accessible, and is also a great CMS in 
>general. It does, so far as I can tell, fall 
>short on CRM integration and depends on Python. 
>I must be honest, this would be the first time 
>I've done back-end admin work with drupal. 
>However, I am both quick and eager to learn and 
>have been wanting to use CMS for a while but 
>never had a use for it. If everybody's 
>interested I can go off and finishing reading 
>the Drupal docs, and we could back up the 
>current version of the website and give Drupal a 
>try. What do you guys think? P.S. Inaccessiblity 
>of Content Management Systems presents a bit of 
>a problem in regards to employment as many 
>multinational corporations use them to 
>facilitate decentralized workflows. On Wed, Aug 
>25, 2010 at 9:11 PM, David Andrews 
><dandrews at visi.com> wrote: > The nfbnet.org site 
>where your site is houses has drupal for your > 
>installation.  From your cPanel page go to 
>fantastico deluxe and you can > install it from 
>there. > > Dave > > At 01:50 PM 8/25/2010, you 
>wrote: > > Hey Floyd, > > I was actually 
>thinking that a content management system would 
>be a great > idea for the affiliate website. > > 
>In short this would be a system that would allow 
>authorized people to make > content postings 
>without having to worry about formatting and 
>stuff. This > would allow us to develop a design 
>once and then focus on content > 
>generation/delivery in a fashion not unlike 
>wikipedia (though with much > better access 
>controls and without everybody seeing an "edit" 
>link). > > This would also help with the "one 
>webmaster" problem and allow the many > people 
>in our affiliate who are great at creating 
>content to more easily > leverage their 
>skills. > > Examples of these systems include: > 
>http://www.scribus.net/ (using drupal) and > 
>http://berkeley.edu/ (running TikiWiki) > > 
>These are very simple to install as they simply 
>require put a few files on > the server just 
>like a regular web page, and could be maintained 
>fairly > easily. > > I think it would make 
>building/maintaining/updating the site a lot 
>slicker > and make it easier to integrate some 
>of our other projects like posting our > 
>newsletter, meeting minutes and/or convention 
>media. > > If your interested I can use my old 
>netbook to put together a demo of a > couple of 
>these packages for state convention so people 
>can get a feel for > what it would look like and 
>how it might work. > > Â Â Â Â Â Â Â Â  Â Â Â Â 
>Â Â Â Â  Â Â Â Â Â Â Â Â David Andrews:Â  dandrews at visi.com > Follow me on

                         David Andrews:  dandrews at visi.com
Follow me on Twitter:  http://www.twitter.com/dandrews920