According to Tables Project Proposal, Tables are a Block Type. However, we will also want Tables to be a query block view. I think it is fine! Let's have both!
Our latest View Definition:
A View is the composed and potentially shareable presentation layer through which content is seen and interacted with. A View can apply to multiple scopes: to a single block, a group of blocks, or an entire document. It is the overall representation of the content in a given context. This allows us to talk meaningfully about things like Card View, Doc View, or other named views as real representations of the same underlying content.
Notion also has both:
1. Simple tables
These are normal document tables. They are for visual structure: rows, columns, notes, comparisons, lightweight layout. Notion says simple tables are useful for adding structure and clarity to notes/docs, and they can be converted into databases.
2. Databases with table view
These are real Notion databases displayed as a table. Each row is a database page, and each column is a property. They support things like properties, filters, sorts, views, relations, formulas, etc. Notion’s help describes “Table” as one database view where database pages appear as rows and properties as columns.
So the distinction is:
Simple Table = document/layout object
Table View = database shown as a table
Database = structured collection of pages/propertiesAttributes
For Seed, this is a useful precedent: you can ship simple document tables first, while leaving room for future queryable/data tables later. Queryblocks query documents, resources and attributes.
Set attribute to a document with
Users can't create custom attributes.
We want Maps in Attributes.
There is a problem with namespaces.
We need schemas to disambiguate namespaces.
Seed:Content
References
Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime