I think we'll probably end up with a couple of solutions serving different needs, maybe:Confluence to track changes and component detailsAxure/Sketch for a visual catalogue to browse

Prince Shivhare wrote... Hey, Its a good approach but every time client is having a different requirement for pages.and is it really possible to get all the component information from different projects? I don't think it is possible. however you can make document for OOTB component which can help in...

Hi,Has anyone found an effective (and hopefully efficient) way of providing an illustration of the different components/templates available for making pages.  Something where people can (effectively) say "I'd like to use 'that' component at the top, then 'that one' below...and then we'll use 'that c...

Hi Jonathanb - did you get anywhere with this?I'm looking at the same issue.Trying to create a kind of 'playbook' for components that someone in UX (or anyone I guess) that'll be considering the creation of a page might use as a reference to help make decisions.  Very much a reference tool.At the mo...