Separation of form and content - Page 2

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View

Re: Separation of form and content (Griff) wrote in

> Hi there
> I'm after some suggestions as to how one might best separate form and
> content in a normal run-of-the-mill web application.

> The situation I'd like to end up with is the ability to split web
> development work into two halves - programmers writing back-end logic,
> and web designers building the look and feel of web pages.

> In summary, we don't want our graphic designer to EVER see a line of
> server side code/scripting, and we don't want our programmers to EVER
> write a line of HTML or client-side JavaScript. I realise this is
> unlikely to be achievable, but as close as possible would be good.

It may not be practical in your situation(for a whole variety
of resons), but I'd suggest considering thinking about a
"non-software" component to the problem - hiring a 'third
person', who is, depending on your point of view, both a
"programmer" and a "designer", or neither of the above.

A "web developer" who can 'sit in the middle', and understands
at least some aspects of both sides, and has the ability to
communicate with both "sides", may be a valuable asset.

In my mind it's always a mistake to "isolate" people into
groups such as "programmers" or "designers". In a practical
sense, many companies feel they have to do this. As a
'jack of all trades', I don't fit into one 'category',
and in some situations, that's just what is needed. Too
often there are problems caused by the infexibility of
having different 'compartments', and/or there are no
"problems" per se, but the end product is not as good
as it could have been.

Sometimes, even if the addition of someone "in the middle"
isn't possible, either by adding staff or contract personel,
some in-house changes can help accomplish similar goals.
For example, set aside some time each week(e.g. lunchtime,
with mandatory attendance, and where the company provides
the lunch) where both "groups" get together, and one or more
people provide a "talk" - one week it may be a programmer
explaining basics of databases to the designers, the next
week it might be a designer explaining the basics of
good visual design to the programmers.

Dave Patton
Canadian Coordinator, Degree Confluence Project /
My website: /

Site Timeline