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

Are Page Properties available?

System

In ContentCenter Professional if you select the Properties for the .page file one of the properties is TeamSite/LiveSite/DependentURIs. Is there a way to get this in an External?

Find more posts tagged with

Comments

vpatel

You may be able to get to those on the TS end via CSSDK API....Do you need it on the runtime side as well? What is the use case? If you need them on the runtime side then LSCS repo may be the way to go or deploy them to a DB..

Migrateduser

I need them in the run time. I think LSCS might be better. On that note I asked another question in the forum. If you dont mind passing on your thoughts that would be appreciated.

Migrateduser

The page properties are available via the .page file in lscs. It's just xml but we have changed directions so this is not an issue anymore.

AlexC

Contents of the .page file are internal and the structure is subject to change without any warning from release to release, caveat emptor.

Migrateduser

Ouch, thanks for the warning that is the exact thing I was worried about. This and other things pointed out the need to move the metadata to the .page file instead of the DCR. Originally, we were going to do dynamic .page files to display the DCR. One location.page for all location dcr and so on. That decision was made to eliminate the maintenance of updating .page files when components or templates change. But then we were made aware of the Get Latest Components menu option under the SitePublisher menu in CCP, that changed everything.