You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the foundation which we have agreed upon, so far.
This is why we are talking!
● Our users must have consistent design: World-class experiences.
● Better quality/less mistakes.
● Save time.
● Easy to change when needed.
Purpose of this forum
● One representative/owner/coordinator/manager per framework to take ownership of components for front-end. A deciding forum. A forum that acts on issues.
● See how front-end development and design can work better together with common components.
● To increase use/contributions of common components:
Remove obstacles and make it easier for others
Communicate to colleagues as ambassadors. Information is key
Target groups (ultimately SEB customers)
Front-end developers (FrontX Guild, smaller group from last meeting, framework specific perspectives, teams)
Design community (CX-designers, Design Management team, teams)
What is our responsibility as group?
● Address our issues, collect and iron out everyone’s question marks
● Push the limit of the way it works today, aim for positive change
● Discuss with FE architects. Name? - Leopold checks
● Time allocation is up to everyone. 20-50% - Discuss with your managers
● Create and use the same guidelines
● Support, communicate and lead
What is the responsibility of a “community manager”?
● Manage the github repo and issues, reply to questions
● Help out new members so they contribute
● Gather statistics on components (see Yousif’s way for React and Angular)
● Keep track of status’ for components
● Tips: Bring in a backup for you
The text was updated successfully, but these errors were encountered:
This is the foundation which we have agreed upon, so far.
This is why we are talking!
● Our users must have consistent design: World-class experiences.
● Better quality/less mistakes.
● Save time.
● Easy to change when needed.
Purpose of this forum
● One representative/owner/coordinator/manager per framework to take ownership of components for front-end. A deciding forum. A forum that acts on issues.
● See how front-end development and design can work better together with common components.
● To increase use/contributions of common components:
Target groups (ultimately SEB customers)
What is our responsibility as group?
● Address our issues, collect and iron out everyone’s question marks
● Push the limit of the way it works today, aim for positive change
● Discuss with FE architects. Name? - Leopold checks
● Time allocation is up to everyone. 20-50% - Discuss with your managers
● Create and use the same guidelines
● Support, communicate and lead
What is the responsibility of a “community manager”?
● Manage the github repo and issues, reply to questions
● Help out new members so they contribute
● Gather statistics on components (see Yousif’s way for React and Angular)
● Keep track of status’ for components
● Tips: Bring in a backup for you
The text was updated successfully, but these errors were encountered: