nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

new site, components based on old site

Parag

Hi all,
I want to create a site which will be replica of existing site in SitePublisher, but will use the components from different branch. What would be the easier way to accomplish this?

Regards,
-Parag
TS6.7.2 LS3.2

Find more posts tagged with

Comments

vpatel

Hi all,
I want to create a site which will be replica of existing site in SitePublisher, but will use the components from different branch. What would be the easier way to accomplish this?

If you are using different components then its not a replica, is it?

Parag

Hi,

The component set which we are referring in new site are also copy of old components. We don't want to touch the existing site as it is released and freezed. So for next release existing site and components will be its base.

We want to create new site and components in new place(different directory). For this we can make copy of components in new directory similar for sites/pages. In this case new pages will refer old set of components. How can we make refer to new components(copy of old components but placed at different location) with less efforts?

Regards,
-Parag

loanReport.rptdesign

vpatel

Hi,

The component set which we are referring in new site are also copy of old components. We don't want to touch the existing site as it is released and freezed. So for next release existing site and components will be its base.

We want to create new site and components in new place(different directory). For this we can make copy of components in new directory similar for sites/pages. In this case new pages will refer old set of components. How can we make refer to new components(copy of old components but placed at different location) with less efforts?

Regards,
-Parag

What exaclty is the purpose of this? If you update a given component for your next release, do NOT do "update/overwrite" on your SP pages -- will that work? If that doesn't work, you should really consider having a separate server (QA/Dev) where you are doing stuff for your next release.

Also how do you plan on merging back your current content + content from next release that you'll be working? How are you going to merge SP pages? How are you going to merge components? You'll have to consider all of these items. IMHO a separate server will be the way to go here.

If either of those options are not feasible then you are probably looking at an unsupported customization. You'll have to test it out yourself. I haven't tested it but in theory it should work -- definitely unsupported. You may have to take care of multiple scenarios -- at minimum you'll have to think through when you first create a copy of your current site and then when you merge it back with current site....

HTH!

report.rptdesign