##About ReactFoo Bangalore:
ReactFoo Bangalore comes back to its original home after completing five successful editions, India-wide:
- ReactFoo Bangalore - September 2017
- ReactFoo Pune - January 2018
- ReactFoo Hyderabad - March 2018
- ReactFoo Mumbai - May 2018
- ReactFoo Delhi - August 2018
ReactFoo Bangalore will bring together over 250 developers working with React, and who are invested in building a space for conversations around experiences using React in production.
ReactFoo Bangalore is a single-day, single track conference with talks, office hours and Birds of Feather(BoF) sessions. Workshops will be held on 1 and 3 March, before and after the conference.
##Who should attend ReactFoo:
- Front-end engineers
- Teams and companies who are evaluating frameworks to use for running applications in production
- Cross platform mobile developers
ReactFoo provides you the opportunity to:
- Learn from and network with peers from the industry
- Gain insights from case studies of practical implementation, and evaluate ReactJS and React Native for your work
- Understand how to run React in production, end-to-end, rather than only build an application with React
Session video
Submission video
XL
Xavier Lefevre
@xavierlefevre
Kickstarting a library of internal React components for multiple teams
Submitted Feb 6, 2019
Section:
Full talk
Technical level:
Intermediate
In a company, as the technical teams grow and work on different projects, the question of creating a set of common components naturally arises.
This is what happened to us: over the years different teams redeveloped very similar components, from simple UI elements to complete business features. 9 months ago, it was time for us to take a step back and think: how can we do better?
This talk will present you our journey toward:
- What we’ve tried in the past... and the reason behind many failed attempts. 😢
- The technical design that worked for us, a mono-repository architecture with helpful tooling: Verdaccio, Lerna, React, Flow, Storybook, Yeoman… 🤓
- The indicators and processes that we set up to ensure that we maintain a good quality and speed of development. 📈
- And finally, the most important: how to onboard other teams in this long running task. 🧐
Today, five teams re-use and contribute to our common libraries on a daily basis, and other departments are expressing a big interest in it. And we even worked through extracting performance indicators, proving us that it was worth maintaining such a collaborative project - that could help you convince your co-workers that it’s worth investing time in such a project. You won’t regret it!
Outline #
Talk break-up:
- The need of sharing components between projects
- Our failed attempts to answer this need
- The final successful attempt architecture, tools and development flow
- Our processes to sustain and improve such a collaborative project
- The key to onboard the other development teams
Speaker bio #
Professionally, I am the result of tangled business and technical interests. Coming from a business background, I am today an architect on web/mobile projects, with the aim to one day build a product that will improve people’s lives.
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}