redo this page, since it has little to do with 'naming convention ' as is.
What I think we need is
- (for sure) a "registry", list of class names (rather then element #id's) that are introduced by kauri (specially the widgets) and capture some 'meaning' or 'purpose'
- (unsure) a technique (naming convention? namespacing technique) to forge new such names in the future

Kauri css class names

  • focused
    • field/widget has keyboard focus
  • unfocused
    • no focus
  • valid
    • field/widget is valid
  • invalid
    • field/widget is invalid
  • failValMsg
    • this block contains a failed warning message
  • collection
  • repeatblock
  • delblock
  • handleblock