Collection and attributes improvements

A collection does not define its attributes, but it defines the attributes of its children. It acts as the parent who controls everything.

In the header of the collection we need to see the whole attributes applied on the collection (how is now is very confusing)

An attribute can be added individually to a children, and it will affect other siblings. It will change the children schema.

When user creates a new collection from scratch, it should not inherit any attributes. It should be 0 attributes and let me shape it as I want.

When the user creates a collection it creates one Table view by default. He can add other views and delete them too. It is deleted by tapping the View name.

The reader will see the views the creator configured.

Change the collection header to one line, grouping like this 👇

Search will expand when tapped.

When creating a new collection user should be able to add a document before publishing the collection, from the button and from the empty state of the "collection".

Each view has its own properties that can configured. These are opened. by tapping on the view when they are active (See notion example).

We need to define better the properties that are shown on each view (TBD). Do not add anything yet, the only thing we have clear is columns for card views.

Remove the 3 dots until we have generic actions that makes sense.

Make activity icons consistent on all views.

Remove duplication on cards

Change the backlink icon for the new one (not sharing).

Remove bookmark from cards everywhere (not just collections). it is weird that you can bookmark on a card but not on other views . Bookmark is done on the omni-bar from the doc. itself

When an item on a collection is a collection, it should have the collection icon not the doc one.

Add icons in all views including table to differentiate types (doc or collection)

When creating a document inside a collection and not publishing it, it should show it but with draft look and feel (grey and draft tag)

Unreferenced optimization

The current version is much better but still when I see the error I don't know what to do. There is a lot of information and no clear call to actions to solve the issue.

Solution:

@Untitled Contact will review the potential errors and classify and in the modal we will have:

Title

Paragraph explaining the error (Bea will define when she knows the errors)

A clear action to do by the user (move, delete, rename) + dismiss

Dismiss will solve the issue and not show anything else