Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...This page is not Valid HTML 4.0 Transitional!This page is not Valid HTML 4.0 Transitional!
Previous
 
Next
New Post
11/17/2006 12:34 AM
 

Hi Cam,

   Sheesh, should have searched before posting... oh well.  I've recently come across the very same irritation that you have.  It certainly doesn't stop the site from working, but while attempting to ensure a high rating by certain search engines, I attempted to test the html that was generated by DNN.  To my dismay, there are certain things that have been stated through research to be somewhat detrimental to being indexed by the likes of Google, etc.  (Certain Meta tags, etc).

I really would like all that I work on to be XHTML compliant and have gone as parsing through the idea of creating an httphandler to rewrite proper HTML, but that task should really begin at the source.  I just don't want my changes to be overwritten by new updates to the product.

Perhaps a standards committee might be needed for the project regarding XHMTL, etc?

Tim

 
New Post
11/17/2006 8:05 AM
 

For those interested in how Sweden, member in the European Unions, adsress this issue – visit Verva, Swedish Administrative Development Agency, and EU:s IDABC (Interoperable Delivery of European eGovernment Services to public Administrations, Businesses and Citizens).

By the way - how does DNN complies with Section 508 of the U.S. Rehabilitation Act of 1973?

Tomas Alsbro, disabled after a car accident

 

 


Trafic injured non profit Site owner/webmaster/admin/user without programming skills, eager to help other injured and sever ill persons.
 
New Post
11/17/2006 8:54 AM
 

I have been developing css based dnns kins for years now and it takes some extra work.

When I design a a skin I make sure that my basic template is error free and I change the default.aspx to be xhtml comliant and has xhtml transitional doctype. ( you need to modify the default.aspx for that )

When i develop custom modules I make sure that my output is also xhtml. Ofcourse i cannot control this from third party modules, so i try to use those as less as possible or i modify them. But then again most of the core mods dont comly either

And as an added bonus asp.net 1.1 out of the box doenst generate valid html

After i have made sure the skin is semantic and validly coded I dont care too much about the validation errors in the rest of the site, most are just because not recognizing of idtags because dnn core enerates it as uppercase

and a lot have to do with wrong replace of the contentpanes ( not in place of content panes but below an empty contentpane with tags that have nothing to do there )

there is no attribute "align".

...an id="dnn_ctr437_ContentPane" align="left"><!-- Start_Module_437 -->

And if you have a portal wher emore people edit content you can never be completly certain that others enter the correct data ( text html modules doent generate standard xhtml by default )

here are some of mine, the original code and skin validated the rest is just because of asp.net 11 and dnn, but at least they are completely table-less in the design

 

http://www.politieknieuws.nl

http://www.schwingsoft.com

http://z.nu.nl

Armand

 
New Post
11/17/2006 9:06 AM
 
Armand,

I'm curious why go through the bother changing the doctype and validating your skin against XHTML and then not care about the rest of the site?  I understand and advocate the use of CSS as a layout and site presentation tool and that's what I see you using it as.

However that really doesn't match up against getting your site validated against any standards. 

And why is it a bonus that ASP.NET 1.1 doesn't generate valid html?  Surely this is a hinderance and not a bonus?

As stated before in this thread, these standards that you use in your skins needs to be pushed all the way down to and through the DNN core.  Aside from all the benefits of standardisation, why do you only bother with a half attempt? 

Cheers
Cameron Church
 
New Post
11/17/2006 9:20 PM
 
For those of us that are hoping to grow an enjoyable past time into a profitable business - let me share a real life experience I went through in August. 

It came down to myself and another vendor bidding to do a site for a professional organization in my province.  The other vendor was offering a LAMP solution with Joomla as the CMS.  The potential client was not overly technical.  However, when speaking of compliance and standards, while they may not have fully understood what they meant or their implications, they knew it was a good thing.  The other vendor was flogging this big time.

DNN as a product is at a competitive disadvantage with many other CMS in terms of compliance.  I did in the end get the client, but it was an uphill battle.  DNN is a superior product with greater usablity - in the end that was what won it.

Whatever anyone says in terms of SEO...DNN sites can get indexed just fine.  Some very simple skin mods can help.  My first blog post talks about one easy thing folks can do to make their skins more SEO friendly.

I recently read a post by Nina (not sure if it was a current one) where she speaks a bit about compliance and she raised a few good points.  I do not want to misquote her...but maybe some searches for her and compliance or XHTML will lead you to it.  She was more tolerant in her stance and had several good reasons for it.
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...This page is not Valid HTML 4.0 Transitional!This page is not Valid HTML 4.0 Transitional!


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out