Best way to display a whiteboard in an entity

Get Help
1

I’m only now trying to make Whiteboards work for me…so I’m a bit late at the party (intentionally) and the first thing that strikes me is how Whiteboards are not really integrated in the fibery UI very well?

The whiteboards field is a list view :face_with_raised_eyebrow:

Say for example I have a Page database and now and then I want to display a whiteboard in the Page entity view. It appears only possible by embedding it in an existing rich text field or create a dedicate rich text field to embed it in. This all is manual work.

Apart from the manual work, the closest that I can get to displaying whiteboards in entities in a more integrated way, is to

  1. create a database ‘Whiteboard’ which entities embed a whiteboard each.
  2. Then create a Feed view of the Whiteboards entities.
    that results in this example:

image
image1732×1339 161 KB

But why do we need this workaround in such a complicated and manual way?
Is there anything planned with regard to a whiteboards entity view?

Apart from all this, the border around an embed is very big and takes up a lot of screen real estate.

2 Likes
2

Very interesting the solution you are trying to create to be able to preview whiteboards. I also have interest to be able to show Whiteboards in some views with the preview.

3

Just a couple of thoughts here:
The current Whiteboards field is basically a collection field, and list view is the simplest layout. It sounds like your primary use case is for having a Whiteboard field which allows to create/display a single whiteboard, right?
Or did you want a collection field which supported multiple viewable whiteboards (and perhaps allowed you to tab through them)?

It’s true that the simplest way to currently show a whiteboard in an entity view is to embed it in a rich text field.
But given that all databases start with a Description field by default, it doesn’t seem like too much manual work :person_shrugging:
Did you know that you can create an embedded view from scratch by typing << followed by the name of the view to be created, and then choosing the view type?