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

Minimizing the div/table tags from content of site and moving to css based content?

sam_cancer

How to minimizethe div/table tags from the content of the site designed using livsite/teamsite components and moving to css based content.

What will this mean in terms of activities involved?

Find more posts tagged with

Comments

tec_iwov

not sure what your trying to ask could you elaborate?

sam_cancer

What we need to do is to use cascaded style sheet in place of table/div html tags for page layout and other purposes. Livesites creates some tables by itself. Our main purpose is to minimize the table/div tags.

rexstaples

LiveSite comes with tabled and div-based layouts out of the box for those customers who are not interested in the rendering implementation details. Because of this these two methods are built to be robust and resistant to customers’ styles (CSS) which could possibly impact the layout. That is why you see inline style rules on the div and table tags themselves.

We recognize that there are others out there who also demand total control over the generated HTML output, and for these customers we have included the ability to define a custom page layout. Creating a customized page layout can be as simple as deriving a new XSL stylesheet by tweaking the existing div-layout XSL or table-layout XSL.

If a customer has special needs or demands even more control over the page then they may create a new com.interwoven.livesite.layout.LayoutIfc implementation class which acts as a pre-processor on the container geometries for the page layed out in the WYSIWYG editor. This pre-processor creates the layout portion of the XML document that will be transformed by the XSL stylesheet.

The only other source for DIV/TABLE tags is from the components themselves. Many of the original out-of-the-box components contain TABLE tags; however, we have prioritized a revisit of those components to only use DIV tags which conform to stricter XHTML standards.

If you still have questions, please do not hesitate to ask.

sam_cancer

Rex, thanks a lot for your input.

sam_cancer

Rex thanks a lot for your response, can you tell me from which place I can get some documentation on custom page layout implementation in livesite.

Also, Is there any documentation available which can guide me on steps which you have mentioned for creating a new com.interwoven.livesite.layout.LayoutIfc implementation class which acts as a pre-processor on the container geometries for the page layed out in the WYSIWYG editor. This pre-processor creates the layout portion of the XML document that will be transformed by the XSL stylesheet.

Thanks,

hubub

I know this is an old post but is this sort of thing still possible? If so where can I find the relevant documentation?

I am a bit of a control freak when it comes to HTML and already have clearly marked up pages and would like to avoid unnecessary modification where possible.

Custom output classes sound interesting and a logical way of approaching things so any info people can provide is much appreciated.

Cheers

hubub