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

W3c compliance for Site Publisher generated HTMLs

Antharix

Hi All,

We are in the process of generating HTMLs using Site Publisher ( Without LiveSite runtime). Pages are generated using components and the then HTMLs are generated from these pates.

The requirement is that these generated HTMLs need to be W3C compliance.

We tried running the w3c validator check and the tool did throw up a few errors.

Can any one suggest as to now W3C compliant code be generated using site publisher?

All you valuable inputs are much appriciated.

Find more posts tagged with

Comments

vpatel

I have successfully generated W3C compliant pages in the past from SitePublisher. For this, you have to code all of of your components, page templates (including page level XSL), etc. in accordance with whatever you are trying to go after (whether it is XHTML or HTML or Strict or Transitional). It is not something that happens auto-magically by switching different page types.

ChartSeriesPatternScript.rptdesign

arujoh

I have successfully generated W3C compliant pages in the past from SitePublisher. For this, you have to code all of of your components, page templates (including page level XSL), etc. in accordance with whatever you are trying to go after (whether it is XHTML or HTML or Strict or Transitional). It is not something that happens auto-magically by switching different page types.

Could you please elaborate on this.

vpatel

Could you please elaborate on this.

When using SitePublisher, the HTML that is sent to the browser is "assembled" from two primary sources: 1.) Page XSL and 2.) Component XSL (or directly Component HTML).

In order to make sure that your entire page is W3C compliant, you have to make sure that any / all of your components as well as the page level XSL conforms to W3C standards.

In order to get anywhere, you'll first need to know what is a component and page level XSL. Have you worked with that before?

HTH!

Antharix

When using SitePublisher, the HTML that is sent to the browser is "assembled" from two primary sources: 1.) Page XSL and 2.) Component XSL (or directly Component HTML).

In order to make sure that your entire page is W3C compliant, you have to make sure that any / all of your components as well as the page level XSL conforms to W3C standards.

In order to get anywhere, you'll first need to know what is a component and page level XSL. Have you worked with that before?

HTH!

Can you please suggest a way/ approach by which the componenet HTML can be modified.
The issue we are facing is that , even though we are using w3c complient code for building the components and pages are built using these components. The generated HTML is observed to have additional

and other html tags.

There is also a need to incorporate Webtrends related code and meta tags into the generated html.

Any suggestions, guidance in this regard is highly appreciated.

vpatel

What version of LS are you using? What errors are you seeing that are not validating against W3C standards?

You probably need to hire somebody who knows how to do this. IMHO, this is not something that would be easily done over the forums. Also it is a bit tedious and time-consuming activity -- not sure if someone is willing to do that for you over the forums :-)!

Antharix

What version of LS are you using? What errors are you seeing that are not validating against W3C standards?

You probably need to hire somebody who knows how to do this. IMHO, this is not something that would be easily done over the forums. Also it is a bit tedious and time-consuming activity -- not sure if someone is willing to do that for you over the forums :-)!

Hi Patal,

Thanks for your inputs.

We are on teamsite v7.2 and trying to address the w3c compliance issues by customizing the page templates and using w3c complient html's in component development.

The issue we are facing is that there are few additional "Div" tags being inserted and this is causing problem.

We are trying to address this on priority.

Also, We are trying to integrate Webtrends and in this context trying to check if there are any plugins already available that can be leveraged.

Thnaks Very much.