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

0 height component in sitepublisher

Cxchu2

We need a way for author to maintain the extended metadata tags in the HTML Header section for SEO in SitePublisher pages. We are planning to create a component with no presentaiton logic. However, it still shows the minheight:30 of the div container in Edit mode which presents inaccurate view of the page.

Is there a good way to hide the height a specific component in Edit mode? Is there a better way to go than a component?

Thank you.

Find more posts tagged with

Comments

Rick Poulin

If you're using LSCS (or some other form of storage that makes EAs available to the runtime) then using a PreController to render data captured in the TagUI is a better way to go.

Otherwise, depending on where the min-height is applied, just create CSS that very carefully overrides this rule, or change the top-level XSL to skip printing divs for components with that particular name.

Cxchu2

I am not using Livesite. Just SitePublisher. I am running into another issue which is that the layout xml can't read the values unless they are writtin out in the component body.

nipper

So if you are not using Livesite, does that mean you are generating HTML ?

Rick Poulin

Cxchu2 wrote:
I am running into another issue which is that the layout xml can't read the values unless they are writtin out in the component body.

Not sure why that's relevant.... but if you're generating pages out of sitepub, then a precontroller is your best bet.

Cxchu2

Yes, I am generating HTML (ASPX in fact). The issue that I am having is to create a component for user to manage SEO tags in the HEAD section. Since they are not visible elements, I need to hide them from view. It's not preffered solution but I think I am going to override the minhight class of SP component container from the EDIT view. However, I'd like to hear others solution is there is a better one. Thank you for your response and help. - alan

Rick Poulin

I just gave you the better solution... If you use a precontroller instead, you don't need a component at all and the issue of the min-height is moot. You also get better control of metadata validation that way, should it be necessary.

Cxchu2

Let me make sure I understand, the suggestion is to use metadata template for SP page. and use the pre-controller to write the values into the <head> section on-page-generate? I thought it requires livesite runtime rendering? If not, can you give me a quick pseudo example to explain what's needed? Thank you.

Rick Poulin

Sorry, it's been a while since I've generated pages. I just doublechecked and controllers don't actually execute in this mode unfortunately.

So my recommendation would be to create an area in your layout specifically for this component, give it an HTML ID, and to edit your CSS such that this element (which should be fairly easy to match) overrides the min-height rule.