I was excited about this feature hoping that it would allow me to embed "live values" from a database in other documents. It sort of does, but the experience for doing that is too noisy to be useful for this use case.
Consider this (contrived, simplified) example; a database with two columns:
Now in some of the application's specific documentation I want to embed the status only from this database. This "works" but is homely to say the least:
I'd like to just insert the status badge (or even the text of it) wherever I want, without the database wrapper. You could call it out as "live data from the database" by coming to a design decision like (for example) live data has a dotted underline and/or a lightning bolt icon next to it or something like that.
I don't always want to insert the whole database row into the sub-page, which is the other option. I want to use the values like a database and reference them wherever I want - so I could render it something like this [mocked] in regular paragraph text:
Again this example is simplified/contrived but demonstrates the behavior I'd love to see to make the database values useful across many different types of documents
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.