Assuming you didn't leave out VoIP or Video Conf equipment:
1. As above, take a CCNA course or find the materials. That will give you a good basis.
2. Read everything you can in regards to VLANs and how they work/best practices/management by hardware OS
3. Read everything you can about switch port management (i.e., access port vs. trunk port, again relies heavily on the chosen hardware OS)
4. Choose your hardware: If money is no object, Cisco is reliable but more upfront and much more for yearly support. HP ProCurve is a very good economical option.
a. Either way, use two stacked Layer 3 switches for core routing with Layer 2 switches for access layer.
b. For Cisco products, I'd recommend a pair of stacked 3750X's, with 2960 for access layer switches.
c. Save yourself pain later - have each access switch trunk to the core stack with an aggregated trunk, one port to each half of the core stack. (if half your core stack goes down, most of your network stays up. If one line/port of the trunk goes down, whole network stays up but speed may be affected depending upon bandwidth used)
5. Use one VLAN for infrastructure (i.e., switches, servers, printers, appliances), use one VLAN for workstations, use one VLAN for wireless if necessary.
a. Avoid using VTP, even if it seems like a good idea to you
b. Do all routing between VLANs on the core stack, access switch trunks should carry all VLANs however
c. Test the hell out of your config in a lab if you have time, lot less pressure telling them that the project is delayed by testing than telling them all work is delayed because you can't find the problem on the prod network
d. Thank god you get a test network
4. Once everything's built, configured, and running well - BACK ALL OF THE CONFIGS UP, and repeat whenever a config change is made.
Good luck, and you'd really better love troubleshooting problems with very little info to go on...