{WIP} Alternative/Complementary component libraries & Support for multiple frameworks

[WilliamKelley]

[[[ WIP ]]]

Introduction

Spark does not attempt to develop a component library or styling solution from scratch. To do so would be a tremendous task. Instead, Spark customizes and extends existing component libraries.

Judging Libraries

Which libraries does Spark extend? More to the core, how are those libraries judged to be the best choice for Spark?

---

https://ej2.syncfusion.com/react/documentation/introduction/

https://www.framer.com/

Articles

• Dariusz Krolikowski (at IBM) on the state of a11y web UI frameworks : https://darekkay.com/blog/accessible-ui-frameworks/
  • criteria in results
  • Best in class
    • React-spectrum (Adobe)
    • Reakit
    • Lightning Design System (Salesforce)
    • Material-UI
• CSSTricks on the perspectives on CSS in JS : https://css-tricks.com/the-differing-perspectives-on-css-in-js/
  • For a JS comfortable team and project, CSS in JS is a win

People's words

• Christopher (vjeux) Chedeau (part of core React team at Facebook) on React - CSS in JS in 2014 : https://speakerdeck.com/vjeux/react-css-in-js : asks to leave mind open for solving CSS problems at scale by using JS
• Alex Lande (creator of Radium) on styling components in 2016 : https://speakerdeck.com/alexlande/components-a-styling-odyssey : All solutions have + and -, but Better DX means Better UX

[WilliamKelley]

Probably should split this into two Discussions, one for alt/comp component libraries, one for multiple FE frameworks/libraries