Onboarding, classes, ontologies and tables

[joepio]

For features like document, I'm not too worried about users misunderstanding them. However, the whole structured data part of Atomic might be a bit intimidating / confusing for newcomers.

• We've got the new Ontology editor, which is by far the best way to create intricate data models
• We've got a new Table editor, which is a great way of creating a data model iteratively while editing instances
• We've got ye olde "new Class" generic form as a bad fallback

There are some problems with this that I'm not entirely sure of how to deal with:

• Tables and Ontologies both create Classes under the hood, but in the case of Tables the Classes are kind of hidden away. Maybe that's a bad thing.
• Ontologies as a thing are kinda niche. People are more familiar with a schema, but even that is a little niche. Anyways, if they find it in the new page, they will probably thing "well I don't know what that is but I don't need it!". We could try to improve how the new page presents them.

Possible solutions:

Create an Ontology for every drive

• Force Class instances to be a child of an Ontology, also when we create a table
• Maybe use the name of the Drive by default and add Ontology, e.g. MyDrive Ontology

Force Ontologies in the sidebar menu

I know @Polleps has already built something akin to this. It may be a bit much in cases where a user