Hi Robin,

The first thing I notice is the different doctype between pages - the last
one you mentioned (.net) has a HTML4 strict, and the other one you developed
has XHTML transitional. I expect that this is a big part of the difference.
Also, because of the different doctype, the page doesn't validate.  Try
fixing these problems and see if that fixes the layout problems.

 

 

In regard to your larger issue of web standards on .net platform - I work
for a company that uses .net programming base; I do the design, html, css
front end stuff and am responsible for web standards stuff in our office.
The way I see it is that there should be no reason why web standards can't
be used in both types of environments (granted I am ignorant of programming
in either PHP or .net, but I achieve web standards front-ends in both
environments). If there is separation of content, functionality and
presentation which is best for programmers too, then you should be able to
work in a web standards front-end even if it is a .net back-end.  Web
standards should be separate from the programming language/platform used.

 

So it might pay to pitch it to them as a programming best practice for
.netters, instead of a LAMP vs. Microsoft thing.  If they can separate the
functionality from content and presentation then it will actually make their
programming lives easier too (or so our developer says - again I can't speak
from personal experience here) and enable you to develop web standard HTML
and CSS.

 

There are also .net developers on this list, so you could always ask someone
at your affiliated company to register to this list for advice.

 

Cheers,

Rachel

 

 

 

  _____  

From: listdad@webstandardsgroup.org [mailto:[EMAIL PROTECTED]
On Behalf Of Robin @ Xplore.net
Sent: Tuesday, 20 February 2007 1:07 p.m.
To: wsg@webstandardsgroup.org
Subject: [WSG] trying to justify webstandards

 

Hi Group,

 

Our web development company is a LAMP based company and we are affiliated
with another web development that is .Net based. I have been preaching to
our affiliated company about the benefits of developing using web standards
(which they see as pie in the sky) and best practices, but my bleating has
mainly fallen on deaf ears, so to try and prove a point I have taken one of
their recent site builds http://www.needanerd.co.nz
<http://www.needanerd.co.nz/>  and quickly rebuilt it in Lamp environment
(http://training.xtools.co.nz/need_a_nerd/index.htm ) to show how the code
can be leaner reducing band width more accessible etc, I have now been asked
to put this on to their cms (.net)
http://dev18.xplore.net:99/need_a_nerd_test_44.aspx  but even though I use
the same style sheet and the same html I am still having problems with the
page displaying in IE, could some one shed any light on this problem for me
please.

I know the test site still needs polishing but it's the concept I am trying
to prove at the moment.

 

Thanks for your comments

 

Robin Gorry

Senior Web Developer

Xplore Net Solutions 

d:  00 64 (0)6 834 24 84

f:  00 64 (0)6 834 24 86

e :  <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] 

w: www.xplore.net <http://www.xplore.net/>  

 

Take control of your website - ask me today about Xsite-tomorrows Content
Management System

CONFIDENTIALITY: This e-mail and any attachments are confidential and may
also be privileged. 
If you are not the named recipient, please notify the sender immediately and
do not disclose the contents to another person, use it for any purpose, or
store or copy the information in any medium.

 


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************

Reply via email to