New and just starting business for web design / development. Long
So here is what I am considering
1. Do crude mockups using Balsamiq or equivalent. I am looking at Balsamiq, Wireframe Sketcher, and Iplotz. These tools will not create a high fidelity mockup and I am hoping to skip this step and if clients need more, doing it in HTML / CSS.
I would consider something like Adobe Fireworks if I determined that a high fidelity mockup is required for my workflow. Like many starting out, I am broke and would like to avoid that expense, but I can get it and learn it if it is required (I can be influenced here)
2. I have a copy of PHPStorm and it is an excellent HTML/CSS/PHP/Java IDE. I will be using it for most of my work Stylizer (a cool CSS tool) and will be incorporating it to do the CSS work.
3. If the site requires a database / interaction develop the interaction in some type of tool (perhaps MySQL Workbench, free and I understand, powerful, or something else if there is a better solution. Any suggestions are welcome)
4. Implement the necessary PHP/HTML and test / refactor / test like crazy.
I know this is a bunch. Any feedback I can get from experienced designers/developers would be great.
Do crude mockups using Balsamiq or equivalent ... I would consider something like Adobe Fireworks...
Another option—which is growing in popularity—is to design within the browser itself. I'm a fan on this, and it makes sense. From simple wireframes upwards, why not work in the actual medium of the web? Some clients like to know what the final design will look like from the beginning, but this is the wrong approach, IMHO. Before any kind of design, the content and its structure should be determined, as this will inform the basic layout, which you can then present as a simple, web-based wireframe. Then the client can see what will happen to elements at various screen sizes etc ... something thats not practical with a graphics editor. Then add in styles as appropriate ... meaning you don't kind of build the site twice.
My other comment would be that it's worth considering a CMS for building database driven sites. There are many good ones out there, like MODx or ExpressionEngnine. They save you from reinventing the wheel.
Thanks for the quick reply. I have a couple of thoughts. I have found that having a crude markup helps me alot, forget the client Then going straight to HTML / CSS. I actually read that article you recommended before and it made a lot of sense to me from the beginning, especially die Photoshop die. It takes way too long for me and its hard to make changes quickly. Maybe I could forgo the cheezy Balsamiq like mockup as well. Further, the other thing I like about your suggestion is that if I need a high fidelity mockup, HTML / CSS can do that perfectly (obviously) and better than some cheezy unuseable export from any graphics program. I am new, but already I feel good about styling pages expertly, so why not leverage that? Anyway, great suggestion.
I have been playing with Wordpress and modifying templates for awhile. Your comment about a CMS for database driven sites is interesting (Wordpress doesn't really have a clue about databases per se unless you add it) Specifically, how do these CMS's help with the database? I really have no idea, so a quick concise answer would be great. Of course, I can always just start looking
Yes, the other problem with designing in Photoshop et al. is that you may not be able to recreate what you did there reliable on the web, so the client also gets unrealistic expectations. For example, if your clients insist on using an older browser, they'll never know that they are missing out on rounded corners and drop shadows if you are desinging in-browser, whereas if they have a Ps mockup by their side ...
Originally Posted by jskintauy
Specifically, how do these CMS's help with the database?
They look after it by themselves. You just set up your pages how you like, enter content and so on, and the CMS stores everything in the database wihtout you ever having to touch it at all. Of course, you can play with the database, but you don't have to. So you can build a database-driven site with little or no knowledge of backend technologies at all. (Perhaps not ideal, but great for being able to deliver nifty sites to clients.)
Another option—which is growing in popularity—is to design within the browser itself. I'm a fan on this, and it makes sense.
Sitepoint seems to be populated by a disproportionate number of "design within the browser" advocates. (That includes myself!) Other design forums feature mostly designers who advocate designing via PS or Illustrator or whatever before starting the actual code. It's a matter of taste, training, approach, and preference.
Originally Posted by ralph.m
Before any kind of design, the content and its structure should be determined, as this will inform the basic layout
This is why I like to design within the browser. It has nothing to do with my rank incompetence in PS, so stop saying that!
Ralph, great link. I hadn't read that before.
Last edited by Black Max; May 27, 2012 at 20:40.
Reason: fixed word choice