Welcome to WebmasterWorld Guest from 22.214.171.124
Forum Moderators: open
I am Kang a Webmaster for 9 years. I got a quick question for you. It is a pretty important question for me, as it appears in this project requirement. It is:
"Polyphony look and feel template based on wire frames and team requirements".
Really appreciate it if any of you can reply to this as soon as you're free.
This comes from a project requirement. What I need you guys to help me with are: "Polyphony" and "wire frames", what do they mean here? I know vaguely wire frames and sketches for graphic or animation design. But no more than that.
I would politley ask you clients to rephrase that requirement into something not quite as overbearingly pretentious. How you ask that will be the tricky bit - but you'll be better positioned to deliver on the brief if you understand it (I haven't a clue BTW - sounds like marketing jibberish to me)
Poly - means "more than one" opposite of "mono".
Phony - comes from the noun "phonic" meaning sound/audio.
Polyphony usually refers to an instrument making more than one sound at a time (example : a piano playing chords), as opposed to a monophonic instrument (i.e. saxophone).
There is no real place for this word in terms of visual design - I don't believe that whoever wrote the sentence you posted actually knows what the word means. So it also sounds like made-up marketing jibberish to me.
Kang could you post more of the requirements? Perhaps if the statement was put in a wider context we could offer some more help.
Welcome to WW. :)
Wireframes are plain vanilla versions of early Web site page designs, sans design elements.
Their intent is to allow the agency and client to focus on the content and functionality of the page, without being overly distracted (as most of us are) by some ugly color that the new hip web/graphic designer wants for an accent color.
Design is added later, once the serious page characteristics and functions are decided upon...
Depending upon the players, wireframes can be a very useful tool in the middle stages of site development, especially if the site has numerous bells and whistles.
Why not ask them what they want though. As long as you know now the basic intent and use of a wireframe, you'd only be asking for detail. That would not bother me if I were the client; I'd appreciate it.