After the model schema is designed, the form should be a thin UI over that shape. The easiest pattern is: prepare data in the wrapper, draw fields in the Template.
Server page prepares create defaults or parent ids.
Template reads `st.use.articleForm()` and renders fields.
Modal wrappers handle quick client-side edits.
Keep Template Simple
A Template should not decide where the form came from. It only reads the current form state and connects each field to a store setter.
Article template
Create With SSR
Use `Load.Edit` on a server-rendered page when the page already knows default values. This is useful for parent ids, current org, default status, or values from the URL.
New article page
Update Page
For a full edit page, fetch the model on the server and pass it to `Load.Edit`. The Template can stay exactly the same as create.
Edit article page
Client Modal Edit
When the user is already looking at a list or detail card, editing in a modal is often faster than moving to a new page.
Edit current item
View and edit modal
Tips
Reuse one Template for create, update page, and edit modal.
Do not ask the user to choose hidden values such as parent id. Prepare them on the server.
Use `onSubmit` for normal page movement and `submitOption` for special submit paths such as `self`.
If field logic grows, split small field groups, but keep the form owner as the Template.
