Radium Component Guidelines

[ianobermiller]

Let's come up with a set of guidelines/rules to follow when creating Radium components. Things like code style, naming conventions, and guiding principles. Off the top of my head (many from @coopy):

• Accessibility is a first-class citizen
• Inline styles, exclusively (except where we can't ;) )
• Sensible defaults (e.g. very few required parameters)
• No abbreviations in component or attribute names, unless very well known and unambiguous (e.g. URL)
• Default style, but easy to theme or completely customize
• Default grid size (24px?)
• Browser support (evergreen, IE10 and IE11?)

...and probably many more. What are some of your internal guidelines?

[coopy]

• 80% code coverage (aiming for 100%)
• Developer experience consistent with Victory
  • No surprises in APIs
  • Consistent code style