Extending views - adding custom components

[joepio]

A crucial part of making this project a success, is developer adoption. I'm trying to provide developers various layers in which they should be able to do something nice with (serialization format, server, library, etc.). Perhaps the most important missing abstraction, at this moment, is the view layer. This repo aims to provide two libraries: one for react, and one for js in general.

But... I think it might make sense to also provide a different type of abstraction. Being able to extend views dynamically.

Usecase

User is using their Atomic Data server for storing various types of personal data. One day, they want to store calendar data on it. They can already create Calendars and Events by instantiating these Classes, but the default views that Atomic-Data-Browser provides aren't very fitting - the user needs a custom View.

Ideally, this custom view can be added during the browser session. Perhaps the user opens a View resource, and an 'install' button appears. If this is done, the view is saved to their Atomic Data server (or in their session only?).

This requires way more thoughts.