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/18/2006 4:14 AM
 
Armand Datema


Joined: 9/16/2003
Posts: 787

Cameron

Its not that I dont care about validation, I just try and make as much valid as possible without having to modify core code, except for the realy special proects.

I make sure that my skins is valid xhtml to be sure that if i use a tableless skins with floated divs that they are correctly rendered on almost any browser and with teh css portals that I did this is the case and thats the most important to me.

as an added bonus, that was mean in a cynical way. meaning that even if you can get it to work nicely you will always have validating errors because of asp.net 1.1

I make sure all my xhtml validates in certain portls by using the telerik controls and the telerik editor . I have been using and implmenting these since ibs days ( made me telerik MVP ;)

This is why I bother with the best attempt, out of the box dnn doenst work with tableless skins and with a few modifications it does. I started out with basic css ksins and added some dnn only hacks and now i have a nr of large portals runnign on them.

At least I know the validation errors that are generated are notmy fault. And i can live with that, after all it may seem like a lot of errors but they are all duu to the rendering of uppercase tags,invalid html declaratiosn in the generated pane code and nome other trivial issues

 

 

 

 

 

Armand Datema

Get my new skin ( lots of design variations [18 headers, 30 titlebars, 30 breadcrumbs, 3 footers ], 50+ typography containers , 50+ page templates and an online theme builder for unlimited skin variations) Aura>

For all your skin conversions

2DNN

Follow me on Twitter
 
New Post
11/20/2006 6:06 AM
 
Cam Church

Joined: 10/17/2006
Posts: 7
_Trip wrote

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



Hi Tim,

I completely agree and I guess that's the crux of the argument.  In my opinion the XHTML standards need to be enforced from the core outwards.  That obviously requires work and planning but I'm a believer in making sure that you have a solid foundation on which you build a heap of features and that maybe the drive to pack DNN with feature after feature needs to be put into a lower gear so that the core house can be put in order first.

I'm more than happy to throw my hat into the ring and roll up sleeves with any members of the community and development teams to get this moving forward as I do believe in DNN and what its trying to accomplish is full of merit.

Cheers
Cam
 
New Post
11/20/2006 3:52 PM
 
Neil Phaby

Joined: 11/26/2003
Posts: 26
I work for Sacramento County in California and am governed by this policy.

One of the great concepts of DNN is that it allows seperate jobs to be done by developers and designers... not so with accessibility.

Even though I've got a good skin going that will match the rest of Sac County's portal I've got to go through the config file and module code, which is going to require this designer to recompile. That's to bad because up to now I've done most of my dnn work with notepad and Dreamweaver.

Cathal has mods loaded in Gemini. It sounds like his solutions will allow folks like me to implement accessibility/508/xhtml features while letting those who don't care continue not caring.

I'd love to hear a projected implementation date of his mods.

Until then I've got to modify the core, log my changes and implement them again with each upgrade.

I love and appreciate dnn, it's developers and it's community, but I reserve the right to be a bit pissed that this stuff isn't already built-in so we could all move on and just skin!
 
New Post
11/20/2006 4:07 PM
 
Armand Datema


Joined: 9/16/2003
Posts: 787

Well if you use good modules and a good skin and non dnn menu controls you can create accessible sites following that policy.

For example all the telerik controls follow the 508 rules and i have done sites before that matched this. But it were all custom modules and a nice css skin. Youc an do it it just akes some time and less relying on on standard modules.

There are a lot of modules that can be coded better. But i wont get pissed that a free portal frameworks doenst work as I want iI just accept it and take all the good parts of the frameworks and add some minor changes myself. A bare dnn with a rel xhtml edir can be made to fix 508

the challenge is the rest of the modules

 

Armand Datema

Get my new skin ( lots of design variations [18 headers, 30 titlebars, 30 breadcrumbs, 3 footers ], 50+ typography containers , 50+ page templates and an online theme builder for unlimited skin variations) Aura>

For all your skin conversions

2DNN

Follow me on Twitter
 
New Post
11/20/2006 4:55 PM
 
cathal connolly


cathal connolly's Avatar

www.cathal.co.uk
Joined: 4/9/2003
Posts: 9676

phabyn wrote
I work for Sacramento County in California and am governed by this policy.

One of the great concepts of DNN is that it allows seperate jobs to be done by developers and designers... not so with accessibility.

Even though I've got a good skin going that will match the rest of Sac County's portal I've got to go through the config file and module code, which is going to require this designer to recompile. That's to bad because up to now I've done most of my dnn work with notepad and Dreamweaver.

Cathal has mods loaded in Gemini. It sounds like his solutions will allow folks like me to implement accessibility/508/xhtml features while letting those who don't care continue not caring.

I'd love to hear a projected implementation date of his mods.

Until then I've got to modify the core, log my changes and implement them again with each upgrade.

I love and appreciate dnn, it's developers and it's community, but I reserve the right to be a bit pissed that this stuff isn't already built-in so we could all move on and just skin!

1. i have a number of the changes tested and implemented locally, i will be checking them in for inclusion in the 4.4 release. They have not been checked in for the past few releases as they have been stabilisation releases.

2. this is an opensource project, feel free to contribute your list of changes to improve DotNetNuke for all - that way you don't have to implement them again. We can only do so much, community help is always appreciated

Cathal

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
 Page 3 of 4
Previous1234Next 
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.