I want to design and develop a portal in PHP with responsive design. My query is about the design and development process for the same. I am thinking to hire someone from freelancing websites to do the same. My question is: Should I first hire a designer to design the homepage and inner page in photoshop and and then code it in HTML as responsive. And then I give that responsive HTML code to My programmer to convert it into PHP portal along with dynamic features I want? I am confused about the process. Am I doing it right? Can anyone guide me please?
Well, how we at eWebGurus like to work is that we design all the pages as PSD, and then convert it into HTML After the static website is designed and developed, then we start working on the responsiveness. Hope we helped! Nick from eWebGurus.com
Everyone has their own way of doing it. For example, we like to implement responsive capabilities only after making the PC version, whereas some people say the only way to go about it is to make it responsive from the very start (including Photoshop). So it's up to you how you do that. As far as development, good development can almost all be completed separate from the website, aside from the parts where the developer needs to know how the site looks. Think of it like any content management system: 99% of the underlying system stays the same no matter what theme you use, then the remaining 1% is code that is integrated into the design itself. Given that, the majority of your development could actually take place in sync with your design process, and then the final steps would be to tie them together. This approach would drastically reduce the time needed to complete your project. However, if you'd rather do things one step at a time, generally you would develop after the design is complete.
Hello yes you can hire freelancer web designer . Before hiring web designer must see his/her work. If you satisfied with his/her work then hire . When web designer make a design for your website then convert it to responsive and give to your programmer to implement it with your PHP code. For responsive design the bootstrap is the best option.
My advice is to forget all the PSD jockey BULLSHIT you were just told by some of the other posters. Dicking around drawing a goofy picture, or even multiple goofy pictures before you have semantic markup and a working responsive layout is putting the cart before the horse, and more often than not results in bloated slow inaccessible train wrecks filled with design concepts that have NO MALFING BUSINESS on websites in the first place. Usually anyone working from such methodology ask "WCAG, what's that?" when pressed, and have complete garbage inaccessible train wrecks as their websites. see eWebGurus.com with it's broken "gee ain't it neat" parallax bullshit, goofy background resizing that looks like arse, and typical turdpress "I can haz intarnets" markup.... no offense @eWebGurus, but if your site is typical of your work, I pity your clients! Figure out what your content is, or if need be make up a reasonable facsimile of your future content... mark it up semantically using separation of presentation from content; which is to say choose your tags based on their meaning, NOT their default appearance! Or as I keep saying, if you choose your tags based on their default appearance you are choosing the wrong tags for ALL the wrong reasons! Then create as your first (of many) layouts as a "screen,projection,tv" target a mid-size desktop layout, which would be fed to legacy browsers. THEN make all your various media queries to adjust that layout up and down from that point as needed... then and only then should one hand off to the PSD jockey for their paintover (if any, thanks CSS3!) and/or use scripting to enhance the page. (remembering the unwritten rule of JavaScript -- if you can't make the page work without scripting, you have no business adding scripting to it!) Anything else is usually a fat bloated slow inaccessible train wreck of garbage, that I can't fathom how anyone would be dumb enough to try and deploy... sadly that also describes ~70%+ of the web. All that said, responsive design is just the next logical step in the accessible design rules of the past decade and a half; if you're used to pissing out HTML 3.2 and slapping 4 tranny or 5 lip-service on it, using presentational classes, presentation in the markup with the STYLE attribute, fixed metric fonts, fixed width design, and the entire gamut of other halfwit broken "accessibility, what's that" development, I might as well be speaking an alien language... meanwhile if you practice elastic semi-fluid layout, separation of presentation from content, semantic markup, at least paying attention to the important parts of guidelines like the WCAG, responsive layout should be natural, easy, and in general a no-brainer.