Fix HTML validation errors & CSSify site

[GoogleCodeExporter]

HTML validation reports a lot of errors in the markup of the pages. They
should be reduced to the minimum, eventually trying to move towards XHTML
compliance.

Original issue reported on code.google.com by simone.b...@gmail.com on 4 Sep 2007 at 6:44

[GoogleCodeExporter]

I need some feedback on this. Should we go XHTML? Because otherwise we should 
use
HTML-only compliant syntax. Say, autoclosing tags like <meta ... /> or <link 
... />
are not supported in HTML and should be replaced with <meta ... > and <link 
...>. If
we want to go XHTML we can leave them there but fix the lot more other errors.

Original comment by simone.b...@gmail.com on 4 Sep 2007 at 7:04

[GoogleCodeExporter]

I have a valid XHTML/CSS translation of the current default template. I'll fish 
out
the source for this and attach it to this issue later today.

Original comment by gavinjo...@gmail.com on 4 Sep 2007 at 9:20

• Added labels: Component-UI

[GoogleCodeExporter]

Original comment by simone.b...@gmail.com on 4 Sep 2007 at 7:16

[GoogleCodeExporter]

The valid XHML/CSS designs are in /trunk/Misc/Designs/XHTML and CSS

Original comment by gavinjo...@gmail.com on 5 Sep 2007 at 8:03

[GoogleCodeExporter]

Have they always been there?
However, this looks like lot of work, do you want me to take on it? Is there a 
way we
can keep in touch to exchange feedback?

Original comment by simone.b...@gmail.com on 5 Sep 2007 at 12:23

[GoogleCodeExporter]

They have been there for a while, yes.

It is a bigger task than most, Anthony Waters also indicated that he would like 
to
take this on. I'll be adding him to the project members soon, perhaps you would 
like
to liaise with him?

You can always contact me at gavinjoyce@gmail.com.

Original comment by gavinjo...@gmail.com on 5 Sep 2007 at 1:04

[GoogleCodeExporter]

I'm not such a great designer, if he wants to work on this I'm fine. I can 
surely
exchange feedback with him if he needs it however.

Original comment by simone.b...@gmail.com on 5 Sep 2007 at 1:14

[GoogleCodeExporter]

OK, lets wait to see if he wants to take this task on.

Original comment by gavinjo...@gmail.com on 5 Sep 2007 at 1:18

[GoogleCodeExporter]

Allocating task to fuzzyfeeling (Anthony)

Original comment by gavinjo...@gmail.com on 5 Sep 2007 at 1:31

[GoogleCodeExporter]

Has there been any progress on this? James indicated that he may like to take 
this on
(issue 10)

Original comment by gavinjo...@gmail.com on 12 Sep 2007 at 8:42

[GoogleCodeExporter]

I would like to work with James on this.  I'll circle back with him.

Original comment by fuzzyfee...@gmail.com on 13 Sep 2007 at 12:56

[GoogleCodeExporter]

I'm going to make this my next priority for the week. I'll work with Fuzzy 
there :)

This is going to require touching a lot of files, so we'll tackle a few at a 
time.

After making sure everything is XHTML compliant, I want to make sure everything 
is
also CSS'd. So when we get to the redesign, we can just mess with the CSS 
instead of
getting into the code. 

I'll make sure there's enough classes and containers to support any redesign. 
And
I'll move any of the current CSS classes/styles/hardcoded values into the 
existing
stylesheet file.

Original comment by james.e....@gmail.com on 18 Sep 2007 at 12:40

• Changed title: Fix HTML validation errors & CSSify site

[GoogleCodeExporter]

Good work to you both ;) Lots of stuff to do here!

Original comment by simone.b...@gmail.com on 18 Sep 2007 at 12:43

[GoogleCodeExporter]

Thanks, this will be a huge improvement. When this is done we can a few 
templates.
I'd like users to be able to choose which template to use.

Original comment by gavinjo...@gmail.com on 18 Sep 2007 at 12:58

[GoogleCodeExporter]

Yep, that was my major goal. Once we get the CSS in place, we can even develop
template HTML files and hand out to others to work offline on CSS redesigns, 
etc. And
whenever someone deploys DNKs they can do their own CSS to make it look however 
they
want it to look.

Original comment by james.e....@gmail.com on 18 Sep 2007 at 1:00

[GoogleCodeExporter]

Yes, not many websites out there are designed correctly on CSS. A post from 
jgalloway
of a couple days ago made it very clear.

Original comment by simone.b...@gmail.com on 18 Sep 2007 at 1:17

[GoogleCodeExporter]

I read that a few days ago. I'm hoping to make DNK more like CSS Zen Garden 
style. Of
just providing enough named containers. The two rules he mentioned about CSS 
Zen Garden:

* The HTML is very simple, structured around the page's information rather than 
design
* It's got ID's assigned to all of the containers elements

These are my two main focus points. After we remove the tables into CSS, then I 
want
to redo the layout and CSS so that it can be redesigned without changing the 
code by
just CSS (like how CSS Zen Garden does).

reference: 
http://weblogs.asp.net/jgalloway/archive/2007/09/12/taking-css-beyond-a-simple-s
tyle-library.aspx

Original comment by james.e....@gmail.com on 18 Sep 2007 at 5:55

[GoogleCodeExporter]

In order to do this, I'm having to make some changes to the root MasterPage 
file. I'm
trying to keep the edits to a minimum since it's going to take a while to redo 
some
of the information/layout.

I'm moving the content from the default.css to the default/template.css (there's
already mixed content in there now between template and root), so I can work on 
the
higher level structure of the pages and work on CSS recoding without messing up 
the
existing CSS. The current site (using default for host profile) will continue 
to work
fine - there will just be a blank default.css file for now.

I don't think the root master page should have a css file. And I think that the 
CSS
file(s) should come from the template directory. Any ideas?

Original comment by james.e....@gmail.com on 19 Sep 2007 at 12:32

• Changed state: Started

[GoogleCodeExporter]

The idea with the root template.css was to allow the [template]/template.css to 
be as
lightweight as possible. The root would define some styles that could be 
overwritten
if needed.

I'm happy if you want to remove the root css file.

Original comment by gavinjo...@gmail.com on 19 Sep 2007 at 6:50

[GoogleCodeExporter]

I had wanted to finish this over the weekend, but RL and work has been sneaking 
up on
me rather fast over the last couple weeks (had a lot more free time when I first
joined the project than now). 

This issue is one of those that is a pain to do a little at a time and would 
work
better if done in one sitting/commit, but I'm lacking the time to do it right 
now. Or
this issue might be better incorporated into the redesign and do it all at 
once. I
don't feel comfortable doing a site redesign without doing mock ups, 
discussing, etc.
with the other team members.

I have time for the small ~30 mins to 1 hr updates that I've been doing, but 
not much
else right now. If someone else wants to pick up the issue and run with it, 
then I'll
be more than glad to help.

Original comment by james.e....@gmail.com on 6 Oct 2007 at 7:35