mirror of
https://github.com/silverstripe/silverstripe-framework
synced 2024-07-05 19:09:27 +02:00
6888901468
* First cut * Temporarily disable composer.json for netlify build * POC * New recursive directory query, various refinements * Fix flexbox * new styled components plugin * Apply frontmatter delimiters * Mobile styles, animation * Search * Redesign, clean up * Nuke the cache, try again * fix file casing * Remove production env file * ID headers * Move app to new repo * Add frontmatter universally * Hide children changelogs * Add how to title * New callout tags * Revert inline code block change * Replace note callouts * Fix icons * Repalce images * Fix icon * Fix image links * Use proper SQL icon
1.2 KiB
1.2 KiB
| title | summary | introduction |
|---|---|---|
| Controllers | Controllers form the backbone of your SilverStripe application. They handle routing URLs to your templates. | In this guide you will learn how to define a Controller class and how they fit into the SilverStripe response and request cycle. |
The Controller class handles the responsibility of delivering the correct outgoing HTTPResponse for a given incoming HTTPRequest. A request is along the lines of a user requesting the homepage and contains information like the URL, any parameters and where they've come from. The response on the other hand is the actual content of the homepage and the HTTP information we want to give back to the user.
Controllers are the main handlers for functionality like interactive forms, rendering the correct templates and performing and navigating around the permission checks on the users actions.
[CHILDREN]