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

LiveSite runtime environment

manish_rathi

TS content management system is used to modify existing contents of a website. So a content of a webpage is modified and deployed on the website using OpenDeploy. Web surfers access this content. Now if, website is dynamic then when this modified webpage is accessed by the user and then it gets the dynamic contents as per the web page "action". Thats when runtime environment is needed to process application code. So this code is outside the purview of LiveSite. So whats the point in integrating LiveSite with runtime environment ?

Find more posts tagged with

Comments

Faizi

So this code is outside the purview of LiveSite. So whats the point in integrating LiveSite with runtime environment ?
[color=Black][/color][color=Black]What you exactly want to say?

If you are talking about previewing a dynamic page within SitePublisher (not runtime) then that can be previewed by setting preview server.

You should also mention the TS/SP version and Environment.
[/color]

vpatel

If you want your site visitors to view pages (.page files) created via SitePublisher most likely you have one of the two primary ways to do so:

1. Generate static HTML (or .jsp or or some other format) from .page and deploy that. In this case you do not necessarily need LiveSite.

2. You deploy the .page files to your production servers and have LiveSite render the pages. In this case, you need LiveSite Runtime -- a huge benefit is that you have dynamic / targeted content capability for your site visitors.

HTH