Do you have an internal UI component library you struggle to tame? We'll discuss how to package, distribute, and deploy components, and look at tools that can help - TypeScript, Webpack, Artifactory, and npm/yarn. You'll learn how to create beautiful documentation, avoid the next leftpad incident, and leverage TypeScript interfaces to implicitly document component APIs, among many other things.
Do you have an internal UI component library you struggle to tame? Together, we'll take a journery to learn how to package, distribute, document, and use component libraries to improve organizational productivity.
Your component library doesn't have to become a hard-to-manage hydra. An internal component library can help improve visual consistency, quality, and consistency, and DRY out your code. At my company, we decided to build our own component library, using Angular, TypeScript and Webpack, as part of our re-brand. There's a lot we didn't know when we started out.
Here are some of the things you'll learn from our component-driven journey:
- Should you build your own component library?
- The advantages and tradeoffs in approaches to component packaging and distribution - whether you're managing them as dependencies, or keeping them together
- Use Artifactory and never worry about another leftpad
- TypeScript isn't just about autocompletion and refactoring fun. It's a productivity multiplier, preventing hard-to-find bugs, and implicitly documenting components
- What does Webpack have to offer?
- How do you create attractive documentation to quickly on-board newcomers?
- Team organization - Who's developing components? Who's writing documentation? How does everyone else find information?