Hypercomponents

[Chalarangelo]

Provide custom components that are more powerful than regular components and make up the main API of the library:

Mappers

Components that produce mappings of data (Array/Object) to a view (set of components):

• [x] Table
• [x] List
• [x] Menu
• [x] Form
• [x] Card(s)
• [x] Media Object
• [x] Item(s) / Tweet(s) / Post(s)
• [x] Graph, Chart
• [x] Profile, Avatar
• Map
• Timeline

Functionality

Additional features that can be added to certain components:

• [x] Sorting (as a feature for tables and maybe other components)
• [x] Auto-pagination (as a feature)
• Scrollspy

Simplification Layers

Easier ways to write components that require a lot of code and micromanagement:

• [x] Accordion
• [x] Tabs
• [x] Radio Set
• [x] LabeledInput
• [x] InputWithIcon
• Text from Markdown

Prefabs

Prebuilt components for common use-cases:

• Login Form
• Pricing and Plan Comparison
• Splash Screen / Hero
• Feature breakdown

[Chalarangelo]

Scrollspy is something that is neither extremely necessary nor super modern anymore. I am going to remove it from the list of thing to implement for now.

[Chalarangelo]

Automated markdown conversion will not be available for a multitude of reasons such as the fact that there are a lot of great tools out there for this.

[Chalarangelo]

Map seems to require an API Google if Google Maps is to be used. Removing as it will also make the bundle significantly larger.

Timeline is... well not much of an elaborate idea, so I'm gonna let it go as well. Better focus on Card layouts that make more sense.

[Chalarangelo]

CardHOC has been removed from the Hypercomponent API and instead Card will now accept non-CardSection children, casting them as necessary.

[Chalarangelo]

Prefabs will be migrated to #23 as they are part of the demos that will ship with the library.