Jason Pruim wrote: > > On Feb 12, 2008, at 1:03 PM, Nathan Rixham wrote: > >> Jason Pruim wrote: >>> Hi Everyone, >>> I know this isn't 100% on topic... But when is any post to this list >>> 100% on topic? :) >>> I've been doing some googling trying to find info on how to plan for >>> what a website needs. Stuff like Does it need a forum, live support, >>> database driven etc. etc. Does anyone have a form that they use to >>> give to the client asking them to outline some ideas that they have >>> about the website? >>> What I'm looking for is something that I could give to a potential >>> client and ask them to describe some basic aspects of their target >>> audience, a rough idea of what they want it to look like, or at least >>> other sites that they like. Stuff like that.. >>> Even if you don't have such a form, I'm sure you all have standard >>> questions you ask each client before giving a quote :) >>> Anyone want to share with the class? >>> If there is interest, I may even put it together on a webpage to help >>> future people :) >>> -- >>> Jason Pruim >>> Raoset Inc. >>> Technology Manager >>> MQC Specialist >>> 3251 132nd ave >>> Holland, MI, 49424 >>> www.raoset.com >>> [EMAIL PROTECTED] >> >> I always take the simple approach, ask them what they want to >> achieve/expect from the website. Then verbally work backwards with >> them to figure out what the website needs in order to reach the >> clients goal. >> >> (personally) In all honesty I'd stay away from any kind of form, as >> they'll just pick "nice to have" boxes and end up with something >> overpriced, not suited to there needs and you'll get complaints in 6 >> months time. >> >> hope that makes sense! >> >> ps: the only thing I've found useful that way after many years, is to >> make the base site structure with very short text descriptions on each >> page + links to the next page | and for god sake, leave the "home" >> page will very very last! >> >> Nathan > > Hey Nathan, > > Thanks for the reply. I'm just getting more and more into freelance web > work and have my first client asking for a quote. Before now, it's all > been internal applications, and the companies website that I have worked > on. Nothing for other people. > > I was actually thinking that the form would be for me to make sure I > covered the basics... I'm alot better if I have something written down > and I can ask the client "Do you need to support multiple languages?" > Which to me then, would lead me into using a database[1] for storing the > pages and using browser sniffing to find out what language preference > they currently had selected to display in that language :) > > > [1] As I was typing this I realized that maybe a database isn't the best > idea for that, but it's the only way I can think of. Anyone who wants to > give me another option is more then welcome to do so! > > > -- > > Jason Pruim > Raoset Inc. > Technology Manager > MQC Specialist > 3251 132nd ave > Holland, MI, 49424 > www.raoset.com > [EMAIL PROTECTED] <--Email and Googletalk/Jabber IM ID.
As to the multilingual; many approaches use defines for site words, buttons, links etc... but since you most likely keep dynamic content in the database then it makes sense to store the translations there too. Then you can build a management interface for the customer to add content and the associated translations. -Shawn -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
