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 this case. and as Scott stated, there is no such document or
tool that provide this information. ~ Prince Thanks both.I'd assumed
there was nothing OOTB but this is the second client I've had (my rol...
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 component' at the bottom for displaying
the x". I know it's not actually quite that simple - but hopefully that
description makes enough sense.Effectively a catalogue for people to
browse - could be UX,...
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 moment we're considering recreating the components in within
a design package: this (as you can imagine) has both up and downsides.