question about mix Sitepublisher and Formpublisher

Hi,

We currently have a content store that is built with Formpublisher, there are a lot of component DCTs and page templates developed and content created. Now we would like to start a new project using Sitepublisher/LiveSite. I have a few questions.

> Can Sitepublisher project be in the same content store and in a separate branch from the formpublisher one?
> If it is possible, is there a way to reuse some of the component DCR files in Sitepublisher?

Thanks very much.

Find more posts tagged with

Comments

Garth McMillan

Yes. They can be used side-by-side in the same branch if you want.

After you've created a branch/workarea you can add a "Site" to it. All the Sitepublisher-specific stuff sits in a folder called "/sites" alongside your existing "/templatedata" folder.

Obviously, how you manage (juggle?) the content within that combined branch is up to you.

Faizi

One point i would like to add here that FormPublisher approach can have multiple workareas in same branch however SitePublisher approach should have only one workarea in a branch.
So, there is no harm in keeping both implementation in a single branch. Make sure your content will not messed up with merging of two approaches.

Haiyan

Thanks for confirming that I can keep them in the same branch. My question about reuse content in Sitepublisher is a scenario like below.

We have a promotion DCT and it has a bunch of DCR files created, each DCR file also has a XML generated as output.

Can those promotion DCR files being converted to components in Sitepublisher so users can drag and drop them to the LiveSite pages?

Faizi

Thanks for confirming that I can keep them in the same branch. My question about reuse content in Sitepublisher is a scenario like below.

We have a promotion DCT and it has a bunch of DCR files created, each DCR file also has a XML generated as output.

Can those promotion DCR files being converted to components in Sitepublisher so users can drag and drop them to the LiveSite pages?

As you said DCR has XML file as generated output. So I assume that UI of generated XML is handled by some other application.
In that case there might be three ways of creating SitePublisher component.
1. Write your UI in XSL and use DCR datum type for selecting a DCR. Use same XML generation logic while fetching content in XSL based on UI.
2. Change DCT to XML type and create same structure as generated XML file, now in component use DCR Datum to fetch DCR and handle the UI part in XSL.
3. Create external component using java class for rendering existing generated XML files from DCR based on certain logic/condition and handle UI in XSL.

For more details go through SitePublisher Developer Guide.

Adam Stoller

Can those promotion DCR files being converted to components in Sitepublisher so users can drag and drop them to the LiveSite pages?

Unless I've missed something in recent changes to LiveSite - the answer is "no" in terms of what you asked. You cannot really "convert" a DCR into a "component". However, you can use (or create) a component to "wrap" (or more accurately, "reference") the DCR such that the content can be re-used in its existing form.

You would then have to replace (code a replacement) for the PT in XSL within the component, since that's what generally renders the content on the run-time side.

Take the above with the proverbial grain of salt, I've been "exposed" to LSCS/LSDS - but haven't really done any real development with it (just a lot of installation / administration work thus far)

Haiyan

ghoti & Faizi, I think you both provided the same solution, we should be able to create a wrapper component which uses pre-existing DCR file as data source and UI will need to be converted to XSL. Thank you both for the help.