1. Who will need to access the guide?
At the moment, our web design team and anyone creating something user experience related. We'd like it to be scalable though for a larger team, however our company has a very small web team at the moment and it would be hard to imagine it growing too much in the next couple of years. So far we have a pretty good grip on everything that falls onto us.
2. Where will they access it from? (eg workstation, home, on the move)
Most likely workstation, possibly from home if circumstances arise.
3. What devices might they view the guide on? (PC, laptop, phone, paper copy)
Probably a personal computer and/or paper copy if applicable (pdf)
4. Will the guide be frequently updated?
It shouldn't need to much updating but our team is relatively new and we are slowly revamping the site that was created by a firm who specializes in creating sites for more conservative companies. It is fairly outdated and I foresee design changes in the future. This is the long term driving force for the style guide. We're thinking more for the future than the next 12 months.
5. If updated frequently how do you communicate that fact, and how quick do changes need to be implemented?
Not very quickly. This isn't a HUGE priority. Our company has a long track record of planning very far ahead and that's why we do so well. We sort of have the same philosophy in our department, and that's why we want to develop a nice clean, somewhat scalable and dynamic style guide now rather than wait a few years when we're knee-deep in header styles :eek:.
6. What technologies do you and your authors have at their disposal?
We have the hardware, software, and ability to learn just about anything we need to if necessary. We have nearly unlimited resources for a team of our scale.
7. Is the guide likely to cover a dozen items or hundreds?
Probably a few hundred maximum if we start including spelling.
Thank you all for your help. And ShyFlower, those were kind of the same things I was thinking. I'm leaning toward a CMS at the moment, especially considering the scale of our team who will most likely be the only ones using it. We could just set up admin/editor accounts for the few we will trust to change the guide and it would be pretty simple. Any other ideas are welcome! Thanks again!