When choosing a vb3 skinner/coder. Things to make sure they know?

[TheDPQ]

Sometime in the future i'll need to look into getting a vb3 skinner and coder. However i'm afraid that currently most people are just vb2 skinners/coders who port into vb3 missing most of the features and functionality put into the new system.

I'm still new to the understanding of all the features and the way the system works so i would be so grateful if someone could help me compile a list. Like many places there are conditionals that are hooked up to the ACP.

1. Legacy
2. Phrases
3. Drop Down Menus.

Yes my list is woefully short which is why i'm asking for help.

[Zachery]

DHTML isnt nessary,

Phraces are. and a designer doesnt have to design for both, they can design to one or the other (if were talking about the postbit, most users are one way or the other about it)

[TheDPQ]

Well the drop downs aren't something thats required anymore then the legacy, however its something to consider. Which is all i'm asking for here. What options must i consider. I don't want all these choices to be made by the limited knowledge of the coder or designer. I've already had people offer to create me vb3 skins already but failed to even know about the legacy option.

I might not care about having any real legancy option, however i'd rather it was me who made that choice rather then the designer. Unless the designer knows how it works they can't really effectively design something that works about this feature.

Phrases aren't required either however it does help keep things consistant even if you aren't planning on even having another language.