Joe Brinkman wrote:
While I appreciate the sentiment, I think you would find if you look at the markup that there is very little room for the removal of markup. It is important to understand where the different markup is generated. Getting rid of some of this HTML would also get rid of features which are used by many devs/designers for achieving their designs.
<a name="xxx /> are generated by the module rendering framework</li>
<li><div class=">
Realistically you might be able to get rid of the
, but everything else is needed to support specific DotNetNuke features and are artifacts of the .Net control hierarchy.
I appreciate the input Joe. I challenge the assumption that there is no room for improvement in this regard. I think it's become this way because features have been added over time, or were originally implemented without regard to the markup output. Heck I know. I've been fighting the markup battle with DNN modules for years, whether it be table based output or invalid html. Historically, it's never been a priority.
Instead of declaring we can't change, how about talking about what features are impacted and how can those could be implemented differently. What would it take? (If you noticed in the second example I provided, I combined some of the output, merged classes in the same div etc. )
Compared to other platforms, the output is a joke. If you've ever created a WordPress theme in comparison, you would know what I am talking about. Obviously, this isn't going to be a priority over neat features like "drag n drop", but I really just want to raise the awareness a notch so when new features are added, the bloat can be managed.
I struggle every day with the perception that this is platform written by .net developers, for .net developers.