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

Solution Approach??

kaalraa

Hi,

Please provide any suggestive solution for the following requirement. I know its out of the box requirement, but trying to acheive the same to an extent.

Requirement:
- I have different HTML components created by Content Authors using TS and XSL based PTs.
- Site Publishers (Managers) have been given the leverage to drop and drag the components or banner images as per their wish on the .page template.
(Till now business as usual)
- NOW, each component developed has its own stylesheets and javascripts associated and business wants that each component html would be deployed individually (might be to different folder) instead of .page deployment. (Reason: Each HTML has been tagged with a unique ID through PT)

Queries, i have:
- Can i extract all the different HTMLs/images from the .page template and invoke a workflow attached with all the files to be deployed individually?
- Also, is there any kind on internal/config file through which i know as which .page include what all component files?

To the least, we are NOTusing LiveSite Runtime Env on our production server.

Find more posts tagged with

Comments

kaalraa

Waiting for Will Scott / Shanon to reply, if not by anyone else.

tec_iwov

>Can i extract all the different HTMLs/images from the .page template and >invoke a workflow attached with all the files to be deployed individually?

the standard ls worklfow will pull in any dependent files for image, dcr and page site resources configured for the page.

>Also, is there any kind on internal/config file through which i know as which >.page include what all component files?

the page file itself as information as to what base component it is and which version was placed on the page