Consistent experience across pages
Rapid application development
Support CONVERGE and TRANSCEND
WYSIWYG implementation for UX designs
Proven high quality UI
adapt-css
adapt-angular
adapt-avatars
adapt-charts
adapt-chatbot
adapt-customization
adapt-radar
adapt-rte
adapt-table
dpl-iconfont
web-components-demo
atf (test framework)
retrospective tool
splash screen
adapt-demo
Gantt calendar
Nrwl - building tools
Nexus - registry server
Staging sandboxes
Jenkins CI
commit and code conventions
design guidelines
When I get back to my old uncommented code
Before
Now
<html>
<head></head>
<body>
<div></div>
<input type="button"/>
</body>
</html>
<html>
<head></head>
<body>
<blog-title></blog-title> // <- my element
<user-card></user-card> // <- here too
</body>
</html>
...is encapsulation — being able to keep the markup structure, style, and behavior hidden and separate from other code on the page so that different parts do not clash, and the code can be kept nice and clean
Source: https://tinyurl.com/yd8a6vqh
Components
Platforms
Angular, React, Vue
Reuse the same markup structure
Browsers support
When teams ask us to support IE7-8-9-10
...but customers are using it
github issues (preferable, all community benefits from it)
slack (better than emails, good for quick questions)
emails (don’t do that unless you are stuck on a desert island with email only)
(docs, wiki, change log, source code for sure)
(spoiler - yes)
Good because:
dependencies - are required in both development and prod
devDependencies - are required in development
peerDependencies - allow you to state compatibility
npm home (works for public)
npm repo (same)
npm ls
npm list package
npm outdated
npm pack
npm prune
npm link
npm audit
npm cache clean -f
npm completion >> ~/.bashrc