/    Sign up×
Community /Pin to ProfileBookmark

code or design?

Copy linkTweet thisAlerts:
Dec 13.2010

So, in this past 2-3 months i learn a bit from the internet for
– setting up webserver with apache,
– creating and connecting table with mysql,
– javascript and php coding,
– html and graphic design.

But, i just realize a main problem for me,
How to create a website to minimizing work time, so i dont have to go a lot back and forth later?
1. The database and table should created first? or
2. The forms, buttons, menu and scripts (without any graphic)? or
3. The graphic design per page + forms, buttons, menu and scripts? or
4. The graphic design for all pages of the website then forms, buttons, menu and scripts created last? or
5. Hows is your solutions? Please explain.

There are a lot and enough information available to make a website, but no one tells which one should go first.

to post a comment
PHP

5 Comments(s) ↴

Copy linkTweet thisAlerts:
@aj_nscDec 13.2010 — Design first, with function in mind, using some graphics editor - I like Photoshop.

Code you design in HTML/CSS.

Make your site functional (database, form submissions, etc, etc)

Add the scripts to make it pretty (like ajax, sliders, etc)

At any time during the last two steps if you think of a new function you'd like, toss it in and alter your design and thus HTML/CSS accordingly.

If it's quite a complex site you may want to figure out your database schema first just so you know where you're headed before you get a lot of work done and realize that you don't know how the backend is going to work.

This is my process. I do not claim it to be correct.
Copy linkTweet thisAlerts:
@criterion9Dec 14.2010 — My process flows from most utilitarian towards the polished final product. I start by listing out the "features" I want using conversational tone (which I can then use to create the "business case" if I need one for the current PMO (project management office) I have to work with). Then I create charts, diagrams, and schemas detailing what data is utilized and where is might go or be stored. Then I identify any objects I might be able to glean from the business case and turn that into graphical depictions (using plain old UML) including any methods, attributes, inheritance, etc. Then I can start breaking the project down into phases (if it is large enough) or more manageable chunks (if the project is smaller) that can usually be completed within a week or two. Then I begin coding all the various pieces and parts in their most functional state. Then because I'm really not very good at the creation of artistic assets I usually get a designer to create some assets (assorted graphics, icons, etc) to make the gui more sleek. Once all of that is done I'll add in the flashy ajax/javascript bits and other miscellaneous "Web 2.0" stuff everyone seems to drool over.

I spend at least 40-60% of the time on a project in the first parts identifying the scope and different parts and usually around 30% of the time on testing which leaves 10-30% of the time actually coding anything.
Copy linkTweet thisAlerts:
@Jarrod1937Dec 14.2010 — There is one main rule to follow, graphics and design should always be last. Beyond that, you should start the planning phase, this is because if the planning phase is done right, it doesn't matter what order you do from this point on. The planning phase should include feature sets (project requirements), data flow, data interlinking (mostly for database design)...etc. Most of this is backend development for your server side and ajax functionality. Some beginners tend to focus on the small 5-8% of what goes into a website, the flashy gui and html. But if you design your template system correctly (assuming you're not using an existing cms), then what the client side actually "sees" is only a small portion of the work that went into a full featured site, at least that is how it should be in my opinion. If you're spending more time on the design and graphics than programming then something is wrong (unless its a simple site).
Copy linkTweet thisAlerts:
@eval_BadCode_Dec 14.2010 — I start at the physical layer and make sure my Ethernet cable is plugged in.

Then I get a pencil and piece of paper. I draw an ERD for my database. Normalize it to 3N.

Web development can be summed up in 1 line of bash (GNU Bourne-Again SHell):
[CODE]>mysql --user=username -p && cd ~ && mkdir sessions && cat > index.php && echo "I hope it works"[/CODE]

[U]Tip:[/U] [B]Everything[/B] can be contained in 1 line. Images can be stored in mysql. There's only 1 file (index.php) and 1 line of code (line 1).

The exception is sessions. It's a good idea to make a folder called ~"sessions/" and store them in there.

The only thing I"m sure of is making a really good database first.
Copy linkTweet thisAlerts:
@tukangnanyaauthorDec 14.2010 — Thank you aj_nsc, criterion9, Jarrod1937 and eval(BadCode) for the advice.
×

Success!

Help @tukangnanya spread the word by sharing this article on Twitter...

Tweet This
Sign in
Forgot password?
Sign in with TwitchSign in with GithubCreate Account
about: ({
version: 0.1.9 — BETA 5.18,
whats_new: community page,
up_next: more Davinci•003 tasks,
coming_soon: events calendar,
social: @webDeveloperHQ
});

legal: ({
terms: of use,
privacy: policy
});
changelog: (
version: 0.1.9,
notes: added community page

version: 0.1.8,
notes: added Davinci•003

version: 0.1.7,
notes: upvote answers to bounties

version: 0.1.6,
notes: article editor refresh
)...
recent_tips: (
tipper: @AriseFacilitySolutions09,
tipped: article
amount: 1000 SATS,

tipper: @Yussuf4331,
tipped: article
amount: 1000 SATS,

tipper: @darkwebsites540,
tipped: article
amount: 10 SATS,
)...