Adding a Custom Editing Form Inside the Resource Edit Screen

Sometimes the resource edit screen needs to manage more than the resource itself. A common pattern is adding a custom form that edits related records from another table while the editor is already working inside the document.

The goal is not to replace the manager. It is to embed one extra operational panel into an already familiar editing workflow.

What makes this viable

• the extra data is strongly tied to the current resource,
• editors benefit from seeing both layers together,
• the custom form is narrow and purpose-built, not a second full manager.

In practice this often means rendering an additional block through a manager event, loading the related data for the current document id, and handling its save flow separately from the core resource fields.

Done carefully, this turns the resource editor into a better operational workspace without making the standard manager feel alien.