Thread Subject: Pondering CMS options for TEITAC
Note
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
Return to this mailing list's archives
From: Bailey Bruce
Date: Sat, Oct 14 2006 7:30 AM
Subject: Pondering CMS options for TEITAC
My expectation is that the Access Board staff is pleased to support
whatever NCAED is comfortable offering. But I see no compelling reason
to add to Jared's workload and I remain unconvinced that more compelling
tools will do much to move the committee and subcommittee members to
change their work habits.
I spent an hour Friday trying to get Don Barrett as excited about the
Wiki as I am. I was not successful.
That said, I have been considering pitching Drupal as an internal tool
for the Board staff, so I am pretty impressed with what little I have
found about it. But such an initiative will have to wait at least a
year.
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Jim Tobias
> Sent: Saturday, October 14, 2006 8:03 AM
> To: = EMAIL ADDRESS REMOVED = ; 'TEITAC Communications Task Force'
> Subject: Re: [teitac-tools] A few odds and ends
>
> or *cough* drupal *cough*
>
>
> > -----Original Message-----
> > From: mike paciello [mailto: = EMAIL ADDRESS REMOVED = ]
> > Sent: Saturday, October 14, 2006 7:49 AM
> > To: 'TEITAC Communications Task Force'
> > Subject: Re: [teitac-tools] A few odds and ends
> >
> > I'd have a very difficult time arguing against this notion. I think
> > Jim is write. Functionally, all of this could be done using
> > MediWiki as the CMS...
> >
> > -Mike
> >
> >
> > -----Original Message-----
> > From: = EMAIL ADDRESS REMOVED =
> > [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
> > Jim Tobias
> > Sent: Saturday, October 14, 2006 7:36 AM
> > To: 'TEITAC Communications Task Force'
> > Subject: Re: [teitac-tools] A few odds and ends
> >
> > I think we're approaching the point where the advantages of an
> > integrated CMS are becoming clear!
> >
> > On one site:
> > 1. public home page with all the usual
> > mission/news/why-you-should-care/links to related programs 2.
> > login for members that identifies the member's role(s) and
> > promotes/formats the info accordingly 3. contains several tools for
> > different purposes: blog, wiki, static pages for reference, etc.
> > 4. supports subscription/aggregation/notification AND listservs,
> > letting users and members choose