Render all fields, not just those rendered on the page

Models might have fields that we also want to render in the sidebar in Edit mode even if they were not explicitly marked for editing in the template (by wrapping them in a cs-field or a {{content.field}}).

Marking a field as sticky (other name suggestions: pinned, editorial) means that field is always rendered for editing, no matter if it shows up on the page. Care should be taken not to render such fields twice (which can be the case if it’s also rendered explicitly in the template).

[ef4]

You’re right that the fully-owned relationships make the right-edge editing more complex, but I think that would be true for any of these solutions. I don’t see an obvious way to automatically discover which owned child resources should have their editorial fields included in the sidebar at any given time.

I think a cs-editor-fields-for component is plausible, but it feels to me like not truly a concern of the component.

I don’t think we should over-curate the right edge. We already have one system for determining which fields a user can see or edit (the grants), and if they have permission, there’s no reason they shouldn’t be able to find those fields in the right edge, regardless of what fields a particular card is using.

[balinterdi]

Closed by #408