> Our goals are:
>
> 1) To be able to have our news editors submit stories via the web or a
> thin Mac client without knowing HTML
Ok, they could cut and paste into a textarea, or use the "upload
file" form tag.
> 2) To have our webmaster simply create page templates in BBedit for the
> news stories, daily changing front page section, etc.
Most "publishing systems" support this. Golive also supports a
"component" mode where you can have web pages include parts of other
web pages.
> 3) To have our graphics department (we are also a print publisher and
> have been for 8 years) create the sites graphics.
Anything could do this, just always point your image links at one spot.
> 4) To have these elements sit in a database and have the pages generated
> on the fly as requested. This is not as necessary for brochureware
> sites, but would be very helpful for new sites. When something like
> "copyright 1998" needs to be changed to "copyright 1999" there are only
> 15 templates that need to be changed, not 300 static html files.
Ok, here is where you actually start to need WO (database access).
Otherwise, you can run unix and use #include "file.html" and the cpp
tool to build pages.
> 5) Netobjects is no longer developing their client for the Mac. Site
> Server really works better if you are an NT/95/98 house. Rather than
> worry about this issue, if it could be as web based as possible that
> would be best. A thin web server based web client for 90% of the people
> involved in any site is a goal with that other 10% using anything else
> necessary- probably BBedit. We have a lot invested in Macintosh
> hardware because we began in the print world with Macs and Quark Express
> (which has the Quark Publishing System by the way)
>
>
> Notes: We don't care what it is served off of- I work with Solaris,
> Linux, NT, and Mac mainly though. My point is that we are not trying to
> keep 100% Mac as this is not only crazy but impossible, but we do want to
> keep 90% of the desktop machines Mac.
>
> I guess I'm in a situation where I can't describe exactly what we want
> because all I know is that the way we are doing things now is not
> scalable. We do everything manually.
>
> Maybe I need some case studies with WebObjects and Go Live, Webobjects
> and Article Base, or maybe I just need to look at some 100% custom
> solutions written in a WebObjects environment.
Well, the GoLive Web Publishing System seems to have disappeared
since they were bought by Adobe. But it was supposed to do things
like this.
ArticleBase can do stuff like this. Its also WO based.
And you could implement all these Goals in WO.
So what you want is a web publishing system where articles can be
submitted via the web and automatically classified and uploaded to
your website.
Use Case:
Sportswriter submits story to sports editor.
Sports editor edits and approves story.
New headline appears on the "sports" page of web site.
User reads headline.
Is that a typical user cycle?
Pierce
----------------------------------------------------------------
Pierce T. Wetter III, Director, Twin Forces, Inc.
e-mail: [EMAIL PROTECTED] Phone:520-779-4227
<http://www.twinforces.com/>
U.S. Mail: 1300 South Milton Rd, Suite 206, Flagstaff, AZ 86001
