Ticket #144 (new Enhancement)

Opened 1 year ago

Last modified 5 months ago

Make BOINC website valid HTML

Reported by: Simek Assigned to: Rytis
Priority: Trivial Milestone: Undetermined
Component: Web - Project Version:
Keywords: xhtml website html Cc:

Description (Last modified by Nicolas)

BOINC website have "poor" quality code.

For example: (from index.php)
<hr width=80% size=1>

In new web standards it should look like:
<hr style="width: 80%; height: 1px" />

The code need some improvements. If not XHTML improvements, it needs quotes (" ") in tags values.

Additionaly I suggest to use CSS files. Save them outside the php file and link to elements by "id" or "class" tags.

I think that the XHTML standard of website is very important and it is the future of Internet.

P.S.

I offer my help with working on this task. I made some XHTML 1.1 valid sites and I can spend some time (approximately 8h-10h per week) to make the code valid.


Edit by Nicolas: XHTML won't be used, we're staying with HTML4.01; see comment 4.

Attachments

download.php (5.3 kB) - added by Simek on 05/02/07 08:41:41.
boinc/doc/download.php -> test version in XHTML 1.1

Change History

05/01/07 11:41:13 changed by Nicolas

XHTML? I'd be happy with valid HTML 4.01. Using the latest standards or not isn't really important, BOINC HTML pages aren't currently following ANY standard anyway! (I do want them to be valid, I'm just saying they're not, under any standard)

But definitely HTML 4.01 will do. Personally I don't see what XHTML can provide that HTML can't, other than being able to read it with a strict XML parser.

05/01/07 22:14:09 changed by KSMarksPsych

  • owner set to Rytis.
  • component changed from Undetermined to Server - Web - Project.

05/02/07 08:40:55 changed by Simek

Nicolas I know that BOINC Website aren't currently following any standard and I think that this must be changed! HTML 4.01 isn't worse then XHTML, but making website validate take much time. When we choose HTML 4.01 after some period of time we shoud change it to new standard. Personally I think that making website now valid with new standard in future allow to save valuable time.

Sorry for my bad english ;)

P.S. I attached file to this ticked. It's a XHTML 1.1 test version of root/trunk/boinc/doc/download.php file. If some one can test this and tell me what is wrong, I will be grateful!

05/02/07 08:41:41 changed by Simek

  • attachment download.php added.

boinc/doc/download.php -> test version in XHTML 1.1

05/02/07 08:52:33 changed by Rytis

We will not go for XHTML because it's unsupported by Internet Explorer. Yes, I know we can send XHTML as HTML, but that's just as bad as sending tag soup.

Since the web won't be able to correctly use XHTML for quite a long time (until 99% of people in the world use the browser that can handle it), the only logical thing is to use HTML 4.01.

Now, to making the pages valid. This is the hard part. I don't think that it's a high priority task. Even if you make the changes, I will have to review them before I check them in, and I don't really have time for that. However, I make (at least the parts of) the pages that I modify valid.

05/02/07 08:53:53 changed by Rytis

  • priority changed from Major to Trivial.

07/14/07 13:52:26 changed by Nicolas

  • keywords changed from xhtml website to xhtml website html.
  • description changed.
  • summary changed from Make BOINC website XHTML 1.1 valid! to Make BOINC website valid HTML!.

Title edited to reflect we won't use XHTML

10/03/07 20:11:15 changed by mtughan

Nicolas has offered his help, and so do I. He and I have worked on a site together, and we both are able to do valid (X)HTML.

04/04/08 20:33:42 changed by Nicolas

  • summary changed from Make BOINC website valid HTML! to Make BOINC website valid HTML.

Removing exclamation point from title; made it look more important than the rest on a ticket list...


If this page is incomplete or incorrect, please edit it or add it to the wiki to-do list. To do this, you must be logged in; click Login or Register above.