We have moved to GitHub Issues
Created by Stephan 15 May 2018, 08:17:05 Updated by Sebastiaan Janssen 20 Jun 2018, 12:17:45
See [this post on Our|https://our.umbraco.org/forum/using-umbraco-and-getting-started/91894-open-discussion-about-the-umbraco-repository-pattern-to-define-re-usable-contentdata]. The idea is to list here (in the description part) practical things that we could do to improve management of OutOfTree data.
Proposing that the discussion takes place in comments, and I'll update the list below with things that could become action items / tasks / PRs.
Should repeatable content/data be in the "content" tree at all?
In UI-o-Matic and Fluidity you define your data in a new, separate panel. If this idea was to be part of the core, you would use document types as you would with content but maybe mark them "special" in some way so that they can only be used in the data panel.
I don't see any reason why this data couldn't still be complex and recursive. Built out using a tree structure in the same way as content in the content tree. Or simple and flat depending on need.
It would be important to ensure the same access to data happens via the user section. This would be at the highest level the panel itself all of the way down to individual nodes.
Just doing some issue tracker clean-up.
This is a discussion that fits perfectly on the forum, once that results in practical things we can and should pick up and start doing, we can create issues for them.
I'll close this for now until we actually decide work is going to happen on this.
Type: Feature (request)
Backwards Compatible: True
Due in version: