A practical guide to moving from server-rendered search results to detail or edit screens with Cotomy while keeping list ownership, navigation, and edit lifecycle boundaries clear.
A practical guide to the search-screen baseline I usually use with Cotomy, using server-rendered results, URL query state, and clear navigation to detail screens.
A practical guide to field validation, submit errors, and API failures while keeping Cotomy screens in one clear flow.
A practical guide to Cotomy form classes, including QueryForm, ApiForm, EntityApiForm, and EntityFillApiForm, with real override points and usage examples.
Why Cotomy ended up with multiple form layers, and how that structure came from the gap between desktop application habits and web runtime reality.
This article explains how the Cotomy Razor Pages template package is distributed, why the root README is the first thing to open, how Standard and Professional differ structurally, and why the correct start path is template install followed by solution generation.
A practical guide showing how I usually structure search screens, edit screens, and read-only screens in Razor Pages with Cotomy.
Cotomy project templates for Razor Pages are now available in Standard and Professional editions. They are designed for CRUD-heavy business applications where teams want to avoid rebuilding page structure, form flow, authentication, and persistence from scratch.
In CRUD screens, the core problem is often not where state is stored, but whether the mutation path is defined. Once load, input, save, and reload are allowed to diverge, the screen becomes difficult to reason about.
Server-side postback screens were limited, but they kept one execution path. Once Ajax became the main update mechanism, keeping display, input state, and server truth aligned became a structural problem.
