Thanks Geoff Features, system requirements, screenshots showing interface to all the tools, and examples of implementation is available here:
http://www.assetnow.com/anx/index.cfm/1,8,html Everything you need to do as routine CMS duties are browser based. Including setting permissions, search indexing, log files etc. Templates, Widgets and CSS are built via the browser interface. Since in my view a developer/designer implements/tests these and then they are simply uploaded to the required system directories. Workflow - unlimited steps based on groups or users assigned to a category with workflow permissions. No complex routing rules - my experience with our previous product "DX" which was released about 4 years ago was that most customers were in fact happy with 3 steps for approval. More complex workflows are typically handled by other systems/procedures in the organization. Remote authoring - web browser and java editor, so anywhere with a Internet connection to the server. What does it address: simply you can publish a web site immediately after install, nothing else required. However you are obviously likely to spend time customizing the CSS and templates (and creating new templates) to suit your layout and visual requirements. As an example: http://www.assetnow.com/anx/index.cfm/1,8,106,html Eric Meyer's lightweight slideshow solution - as you can see the layout is quite different to the main site. Simply a different template and CSS applied. Content is published from the CMS as for any other page. Regards Johan > ------------Original Message------------ > From: "Geoff Deering" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Date: Thu, Oct-7-2004 12:38 PM > Subject: RE: [WSG CMS] Re: digest for [EMAIL PROTECTED] > > > From: Johan Steenkamp > > > > Hi Geoff > > > > As the developer of AssetNow I am interested to find out what you > > need to know and happy to help out. > > > > Thanks > > > > Johan > > I'd like to know the features, what is required on the backend, the > admin > interface, the workflow principles, just what is easily configured > using the > interface, remote authoring, modules, components. Just what does it > address. > > Especially if it is worth paying money for then I want to make sure > that > everything is documented and addressed and just what fundamental > architectures of CMS it provides and doesn't provide and how flexible > they > are, and how they work. > > ----- > Geoff > > ********************************************************* > The CMS discussion list for http://webstandardsgroup.org/ > ********************************************************* > > > ********************************************************* The CMS discussion list for http://webstandardsgroup.org/ *********************************************************
