Looking for Answers?
Browse our articles to find the answers you need
Contribution Process in WSR
Contribution with WSR
The purpose of the contribution is to allow the development of a component that has been approved by us (the WSR team) (in terms of both product and development) in order to allow the re-use of that component by additional teams in WIX and thus to share the component in the WSR library. Contribution is a process of product that somebody else is doing, and we give the guidelines and resources (if needed), and the components will be shared into our WSR library for reuse across Wix.
Important!
Independent component development for back-office page without sharing it to WSR library is not allowed! Exceptions can be made only if approved by us.
The more we get involved in the early stages as kickoff, the better we can make the contribution process, and so we can prioritise it as part of our backlog and part of our roadmap. However, the contribution process is a binding process to meet the times and meet the reuse components requirements for all the company's products. It is important to understand that we may not be able to comply with the Contribution process if we know about it just before development, in this case, we may request to repeat the entire process with the aim of preventing the development of a component that has no meaning of reuse and sharing the whole company.
Principles for Contribution
In the collaboration process, we specify where required: Inform, Review, Approval, Commitment
Inform
We need to know that a process starts, to understand its purpose and schedule. On our part, we will add the project to our backlog list and prepare according to the schedule.
Review
We go through the process together with the other group, raise important points to continue, and agree with the following.
Approval
Get our approval for product and UX decisions that affect the products and components in the shared library.
Commitment
Agree on the schedule and deliverables and the list of components and who is developing it and how. This list can share responsibility between the WSR team and the Vertical / company both in looking at the resource and times.
Sharing the process with WSR
1 - Share Your Kickoff
2 - Product Review
Create a new component with WSR
A new component or adjustments to existing component can come from:
1. Wix Style React Team
Within the WSR team, while identifying needs from users or verticals which lead to, improvement, adding or updating components.
2. Vertical team
A Requirement comes from a vertical, then the process of collaboration with us begins.
On this page you will find the process of both options clearly.
On this page you will find the process of both options clearly.
When to contact
Contact us in the most early stage of the process - in the research or wireframe stage, when you think you won’t be able to use an existing WSR component.
Why to contact
A. You think you might need a new component
B. You think you might need an adjustment to an existing component.
Contact us in the most early stage of the process - in the research or wireframe stage, when you think you won’t be able to use an existing WSR component.
Why to contact
A. You think you might need a new component
B. You think you might need an adjustment to an existing component.
The process
Here you can learn about the full process for creating a new component – what your part is, where we do a review, when get approval by us and where is our commitment.
You can see here the flowchart showing our full process: https://wix.invisionapp.com/share/NUW98YVJ4BE
01 - Kickoff (Request)
02 - Research
03 - Design & Test
04 - Review
05 - Spec & Jira Task
06 - Development
07 - QA
Was this article helpful?