Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

fatbaldboy
fatbaldboy
Offline

Badges

Badges
6

Accepted Solutions

Accepted Solutions
1

Likes

Likes
2

Posts

Posts
4

Discussions

Discussions
0

Questions

Questions
4

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by fatbaldboy
Customize the badges you want to showcase on your profile
Re: Creating a 'playbook' of components for page creators/designers
Avatar
Give Back 3
Level 2
fatbaldboy
Level 2

Likes

2 likes

Total Posts

4 posts

Correct reply

1 solution
Top badges earned
Give Back 3
Give Back
Ignite 1
Validate 1
Boost 1
View profile
fatbaldboy
- Adobe Experience Manager
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

Views

88

Like

1

Replies

0
Re: Creating a 'playbook' of components for page creators/designers
Avatar
Give Back 3
Level 2
fatbaldboy
Level 2

Likes

2 likes

Total Posts

4 posts

Correct reply

1 solution
Top badges earned
Give Back 3
Give Back
Ignite 1
Validate 1
Boost 1
View profile
fatbaldboy
- Adobe Experience Manager
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...

Views

88

Likes

0

Replies

0
Creating a 'playbook' of components for page creators/designers
Avatar
Give Back 3
Level 2
fatbaldboy
Level 2

Likes

2 likes

Total Posts

4 posts

Correct reply

1 solution
Top badges earned
Give Back 3
Give Back
Ignite 1
Validate 1
Boost 1
View profile
fatbaldboy
- Adobe Experience Manager
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,...

Views

193

Like

1

Replies

6
Re: Styleguides / Pattern library / Component documentation
Avatar
Give Back 3
Level 2
fatbaldboy
Level 2

Likes

2 likes

Total Posts

4 posts

Correct reply

1 solution
Top badges earned
Give Back 3
Give Back
Ignite 1
Validate 1
Boost 1
View profile
fatbaldboy
- Adobe Experience Manager
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.

Views

208

Likes

0

Replies

0
Likes from