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; } } }

Is LiveSite and sitepublisher is same?

AmsB

Find more posts tagged with

Comments

Adam Stoller

Is LiveSite and sitepublisher is same?

At one point, several versions ago - yes.
Now - SitePublisher is the back-end development-side interface within TeamSite for developing pages and LiveSite is the front-end application-server-side interface/engine for rendering pages.

Migrateduser

Kinda yes. Livesite earlier packaged as Livesite development and Livesite Runtime and You install Livesite Development on Teamsite and Runtime is Runtime. SO Livesite development is nothing but Sitepublisher now just packaged differently. Also Sitepublisher now has generation capabilities.

In the older livesite version, if you are installing liveiste, you will have the menu as livesite instead of sitepublisher today.

Hope this helps

vpatel

I guess it depends on what context you are asking the question in.

From installation perspective: one (SP) is the authoring environment versus the other (LS) is the runtime / dynamic-presentation environment. They are separate installs.

From development perspective: you do your development on the SP side and then "port" (I'll resist using the word deploy here) it over to LS. Somewhat similar to J2EE/.NET apps.

From documentation perspective: it gets blurry. In the past, there was a single guide under the SP banner. Now there are two separate guides - one for SP and one for LS.