SitePublisher and Output Code

alanhill

Hi,

We're currently investigating the use of SitePublisher and I have a general question that I would appreciate any feedback on.

We don't intend to use LiveSite - we still want to create our pages in Teamsite and deploy them to our web farm where they will be served through IIS.

Our business colleagues are looking for a much nicer UI for their content creation, with the ability to select and drag/drop elements of a page (which is why we are looking into SitePublisher as well as various other options).

My understanding so far of SitePublisher is that it produces a lot of markup code that the developer has little control over.

My main question is - can SitePublisher actually be used to provide JUST a nicer front end on our current template solution, while allowing us to retain complete control over the markup generated?

I'd really appreciate input on this from anyone who has gone down the same route.

Many thanks,

Alan

(Windows 2003, Teamsite 6.7.2, SitePublisher installed but no LiveSite)

nipper

SP components are broken up into 3 parts, Datum, XSL and compiled Java.

End users have a page template (which is a selection of components in specific locations).

When a user edits a component, they change the Datum, which can be a simple field, a TinyMCE editor or a node in a TS Forms Publisher Template.

so yes, you can retain as little or as much control as you want.

HTH

Andy