Forms that belong with the Laravel CMS
Forms often start as one-off controllers and grow into validation rules, notifications, spam protection, storage, permissions, and reporting. Capell gives form work a place in the CMS surface without turning it into a separate platform.
Use forms for contact flows, marketplace submissions, package feedback, newsletter interest, access requests, and page-specific calls to action.
Where forms fit in a CMS-backed site
Capell keeps form behavior reviewable in Laravel: validation, authorization, notifications, persistence, and follow-up actions can use the same application conventions as the rest of the site.
Forms questions
Forms are most useful in Capell when they support public content, marketplace operations, customer workflows, or publishing decisions.
Are forms rendered by the CMS or by Laravel?
The public output stays Laravel-owned. Capell can provide the CMS context and package surface while Actions handle form behavior.
Can forms be page-specific?
Yes. Forms can be connected to campaign pages, package pages, access gates, and content workflows when the project needs that context.
Where should form logic live?
Business behavior belongs in Actions or services. CMS pages and widgets should provide the public surface, not hide domain logic.
Turn visitor intent into Laravel workflow
Forms pair well with packages because deeper workflows can be installed deliberately instead of becoming hidden one-off page code.