I need to create a proper pattern/component library for our organization. Ideally, it would include:
- images (examples of the component)
- attachments (wireframes)
- notes/conversation (to document changes/decisions over time)
- handles versions
- could include sample code snippets (at least sample HTML)
In the past, we've built this by hand, creating a static web site that we maintain internally. It works, is customizable, but a chore.
I need to do this again in a new organization and am hesitant to build a static site again--mainly because if I leave, no one else will pick up the reins.
I always thought there could be a good market for this--a content management system or blog or wiki specifically designed for pattern/component libraries.
I recently came across http://patternry.com
Has anyone used it? I don't know much about it other than it has a funny name and the sample screens seem OK. Not great, but at least handles some of the functionality I am looking for.
I'd be interested in hearing opinions on hit, but really am more interested in what others have done to build and maintain their own component libraries...especially those of you that, like me, are stuck inside a corporate firewall that tends to a) mean we're stuck with crappy enterprise options like SharePoint and b) means that they usually don't allow hosted solutions outside the network.