EPIC Develop a functional unsupported AnyField

[jakxnz]

Description

The world needs a Silverstripe-official way to manage the data of related objects and the preference is a lightweight way of editing the fields of a related record within the CMS. Something that's simpler than a GridField, but more sophisticated than other rudimentary ways of inline-editing the fields on a related record. There's some great benefits to having a dedicate Form Field for this, and we already have interest from our user-base to make it a reality. We believe we are ready to release an "alpha" module outside of of our commercial support to incubate in the OSS community. And, we will be coming back with a later epic to advance the alpha to the standard of an officially supported module.

Big story

As a Silverstripe CMS editor, I want an intuitive way to manage the data of related records, so that I can easily and reliably edit relationships in a simpler experience than GridField.

Success metric

A pre-official AnyField is being used and is providing a good source of feedback to incubate the module towards formal support.

[michalkleiner]

I'm not 100% sure that something being a preferred solution for a specific agency/vendor should be a success metric for an epic/a user story.

[GuySartorelli]

@jakxnz looks like you created this in the wrong place - anyfield is not related to elemental. I'll migrate it to the .github repo for now

[mfendeksilverstripe]

Relates to / Overlaps with maxime-rainville/silverstripe-anyfield#28

@jakxnz @GuySartorelli