While we don't use it for precisely this scenario, it would be pretty simple
to implement.  We use Cascade from Hannon Hill.  It was the tool that best
fit our model of web site management (aka complete chaos).  I was involved
in selecting Cascade, so if you want to know more about that just hit me up
off-list.

The "wins":
Publishes static files, so the CMS isn't the web server
LDAP Auth
Template system allowing for easy site creation while still maintaining
control over the page structure.
Multiple publishing targets (pushes over SFTP)

The "fails":
It doesn't magically update your content based on what you're thinking that
day.

On Thu, Jun 9, 2011 at 9:56 AM, Debra Kurtz <[log in to unmask]> wrote:

> Hi All,
>
> Do any of you work in libraries that use the same content management system
> for both their intranet and public websites?  I'm interested in learning
> what tool and how well (or not) you like it.  I'm especially interested in
> hearing from those of you involved in the selection and implementation of
> these tools.
>
> Thank you in advance,
>
> -debra
>