Explained in this loom:
Problem:
- We want a master template for a type of record to re-use across different navigation areas
- Noloco makes you navigate to the source of the template that you want to use (navigating away from where you are) - Users are confused and taken away from the section they were just in.
Proposed solutions:
- Completely separate the concept of a Template from where the data for that template lives
- Allow re-use of a Template in another navigation tree (and keep the URL/tab within the section you’re in)
- Allow a collection/view to “sync with” another type of template so that the developer only needs to maintain one
I’m sure you have thoughts / roadmap items on this so I’d love to hear what you’ve exploring here.