Thanks for the insights Rob and good to know I'm not alone in the chaos.
Your process sounds much the same as what we have in place currently,
yet whats also proving difficult to manage within our team of six Visual
Designers. Perhaps we need a Keeper, like you suggest. Or perhaps pass
this role onto a project manager to maintain.. seems like more their
area in a way.
A resource site is something we've considered, it just comes down to
allowing development resources, and in a way, it seems it's for reasons
like this that Version Cue was invented. What added benefits can you
foresee a Resource site having..?
Re: PDF Delivery
PDF is not our company standard, so I'm up against a huge amount of
resistence in that area (we've resorted to offering annotated, sliced
(pdf exported).png's inside a word .doc to overcome it!). But the
advantages far outway the extra time taken to produce the word doc, so
thats where we're headed. Hopefully development and internal resistence
will grow to love the review features as much as we love staying inside
the joys of CS2.
Anyone else out there inside large firms requiring a similar workflow..?
I'd love to hear how you tackle the issues.
> > So far, I am the keeper of the master Photoshop prototyping template > that contains all our widgets on different layers in the psd. We are a > small team though. I have used just simple version control to monitor > the progress of the prototyping template: "template v3.4.psd". As time > permits, I make updates to the template that includes visual > representations of coded widgets we have used, and variations of > existing widgets. > > We are in the middle of creating a "resource site" for us UI designers, > to better manage the different versions of our widgets we use. Similar > to your email, we have standard widgets and controls, but many times we > have to customize them to a specific project. We have one "calendar > popup" widget, but many variations to account for the specific > requirements for a project. We want to track all of this on our resource > site (internal for us only). > > We deliver our screens and documentation in pdf form, because you can > add some simple security to the document. We want people to be able to > print our pdf's, but not be able to change any of the content. We can > add editability security in the pdf. I just do a "save as" in Photoshop > to create the pdf's of my screen designs. > > Does this help? Or answer your questions? > Rob