How to best model Hierarchical Types?

[Oshyan]

@Chr1sG

Perhaps there is an easy win, in the short term, whereby fields can be grouped, and then shown on the entity card on different tabbed pages, so that there would be a tab for ‘Projects’, a tab for ‘Website’, a tab for ‘Brochure’ etc.

Indeed. I made similar observations when I discovered Ninox some time ago:

Today I discovered Ninox - Fibery's past *and* future

I came across an interesting app today called Ninox. Has anyone heard of or used it? It reminds me a lot of Fibery in many ways. It has been around a lot longer, since 2014 at least, and in some ways is more capable than Fibery (more on that in a moment), while in other ways less so. The UI/UX is a bit outdated and clunky, but the set of capabilities is actually fairly impressive and broad in its core database area. Ninox focuses entirely on databases, there are no “documents” at all, and no w…

Also some related discussion here:

Individual Layouts for a node, hide fields etc

This may be some work … Currently the displayed layout of a Model shows all items. One good thing is, you can sort the fields. But you can not hide any. Seeing “creation date” and other fields for example is most times useless and overloads the page. BUT it is not a good idea to make it globaly for all views of a model anytime. It should be a way to have different layouts. Not sure what could be a good logic. Maybe it may depending on where you opened it? In any case a toggle for “show all f…