> Is there a preferred way to get a project started. What I mean to say is, do
> you type of all the HTML first, mark it up and then write the CSS or do you
> do it piece meal? I am just trying to figure out a logical process which to
> go by so that I can make my work easier to understand and accomplish.

First of all, could anyone on this list please stop using Subjects
that are generic or don't contain the idea of the request? A message
like "question from a beginner" is not likely to be found if somebody
is looking for best practices in development.

As to your question:
I taught myself to develop the HTML completely and document the ID /
class / element structure before starting my CSS.

While this can appear a bit tedious - and you may have to revisit the
HTML at a later stage when fixing for MSIE^H^H^H^H bad browsers out
there - it will ensure that:

- your HTML is well structured and makes sense without CSS and/or JavaScript
- you have a bit of documentation to hand over to the maintenance
developers and more importantly to prove later on that they messed up
your code, not you.
- you could give the HTML to the middle ware developers to turn into
templates or mess up^H^H^H^H^H^H^H^H convert into ASP.NET, that way
ensuring that you can work in parallel.
- as some CMS solutions offer different classes to the editor as
styles in the WYSIWYG editor, this also means you can create a small
style guide for those to fill in later when you do the CSS

HTH
Chris


--
Chris Heilmann
Blog: http://www.wait-till-i.com
Writing: http://icant.co.uk/
Binaries: http://www.onlinetools.org/
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Reply via email to