Re: [Sigia-l] storing pattern libraries

We have a company wiki and use this for our pattern libraries, among
other things and have found it to be quite useful.

I also wouldn't let Ziya direct you on how you or your company decides
to create it's own libraries; remember they are for your own use, no one
elses. We've done a lot of work on creating ours, and yes, the UE group
put it together with the intent that developers will need a place to put
their items.

Again, remember the library is for your own use, and though asking for
advice is great, but we're not the ones using it.

brett taylor + R O U N D A R C H + bus 312.529.2502 + mob 773.844.5233 +
web www.roundarch.com

-----Original Message-----
From: sigia-l-bounces@asis.org [mailto:sigia-l-bounces@asis.org] On
Behalf Of Ziya Oz
Sent: Tuesday, September 25, 2007 8:46 PM
To: SIGIA-L
Subject: Re: [Sigia-l] storing pattern libraries

Juan Ruiz:

> What we are trying to create a database of patterns that can be reused

> by the User Experience team as well as other web team members.

Therein lies the problem.

Who exactly will benefit from the adoption of these "patterns":
designers or developers?

What may be convenient for prototyping purposes or expedient for quickly
getting a project deadline met for designers may not be the most
efficient choice for system or architectural considerations for
developers at all.

If you're (also) not a developer, I wouldn't recommend that you make the
decision.

> Can you recommend of a tool to store pattern libraries?

Hmm. These Web 2.0ish libraries are really a bunch of text files. So
anything from a simple folder structure to a simple DB should suffice to
store them.

> At the moment, in our organization we are using Visio as the tool to
> create wireframes, sitemaps and workflows.

Well, that's different, because now you're talking presentation. Problem
with tools like Visio or PowerPoint is that they are largely static,
whereas much of these libraries are interactive/animated/etc., dependent
on DHTML and Ajax. It'd be hard to fully demo/browse these libraries in
static tools.

So I'd keep it simple and store thumbnails/brief descriptions and URLs
to sources in an outliner, Excel or, really, a (bookmarks) web page.

--
Ziya
It depends.
If it didn't, you'd be out of a job.
------------
IA Summit 2008: "Experiencing Information" 
April 10-14, 2008, Miami, Florida
-----
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments
Searchable Archive at http://www.info-arch.org/lists/sigia-l/
________________________________________
Sigia-l mailing list -- post to: Sigia-l@asis.org Changes to
subscription: http://mail.asis.org/mailman/listinfo/sigia-l
------------
IA Summit 2008: "Experiencing Information" 
April 10-14, 2008, Miami, Florida
-----
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments
Searchable Archive at http://www.info-arch.org/lists/sigia-l/
________________________________________
Sigia-l mailing list -- post to: Sigia-l@asis.org
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l