Component design conventions

This page is a work in progress

Component property & attribute names

• For component properties, we use camelCase naming. For example hasBackButton.
• The only exception to this is for properties that are tied to native HTML attributes. For these, we copy the same casing as the native one. For example formenctype and formnovalidate.
• If the property is a boolean value, we aim to prepend the name with is. For example isOpen, isStrong. The only exception is when the property shares a name with a native HTML attribute. Such as disabled or checked.