Should we have a "recipe book" of common layouts using best practices? - Githubissues

telus / tds-community

TELUS Design System Community Components

https://tds.telus.com/community/index.html

MIT License

28 stars 7 forks source link

Should we have a "recipe book" of common layouts using best practices? #87

Open jesdavpet opened 6 years ago

jesdavpet commented 6 years ago

Problem statement

As a Developer, I would like to have a "recipe book" of common layouts employed using TDS components, so that I can:

understand current best practices
save time writing boilerplate markup, and
get a more consistent result

Recommendation

Determine if the practice of using layout "recipes" is an improvement over current practice of ad-hoc implementations by each squad
If "recipes" are a favoured / scalable approach, decide what would be the best channel to share them

Designs

Should be based on existing tds-core, tds-community, and DSM assets

Meta

Include component name and version: N/A
Willing to design solution: Yes
Willing to develop solution: Yes
Has workaround: N/A
Do any similar components already exist in TDS (core or community): No
Which teams/applications do you think would use this improvement?: Design to Developer handoff
High impact: Unknown

jesdavpet commented 6 years ago

The approach of creating a layout "recipe" would be another way to get consistent implementation of layouts such as the proposed Comparison Card (https://github.com/telus/tds-community/issues/21)