"one thing you said you were looking for is a way to "make my
work easier to understand and accomplish.""
for me I feel more in control with my coding projects if I start every
project with a stupidly detailed to do list.
Then I keep a to do list going as I worked, generally on paper. This is key
"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.
I start with a print-out of all the pages- or a quick sketch
I then measure things out, check font-sizes, colors etc.. and write them on
the sheet.
I check for common elements first then I use pencil to design my strategy-
this is one container div , this will eb the header etc on those first
I guess the thing most people here said is true: everyone has it's on
way of "starting". Try different approaches and figure out the one that
suits you best.
I always do "it" like that:
1. project in my favorite graphics editor
2. xhtml structure (with almost whole content in)
3. scripts (js, php+
> 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 acco
"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.
Stephen Kortz wrote:
> 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 t
MAIL PROTECTED] On Behalf Of Stephen Kortz
Sent: Tuesday, November 15, 2005 8:53 AM
To: css-d@lists.css-discuss.org
Subject: [css-d] Question from a beginner
Hi all,
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
Stephen Kortz wrote:
> Hi all,
>
> 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 think most folks *start* by doing it piece meal, as you say --a trial
and error (
Of Stephen Kortz
Sent: Tuesday, November 15, 2005 8:53 AM
To: css-d@lists.css-discuss.org
Subject: [css-d] Question from a beginner
Hi all,
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 p
Stephen Kortz wrote:
> Hi all,
>
> 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
Hi all,
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 acc
12 matches
Mail list logo