-
-
Notifications
You must be signed in to change notification settings - Fork 5
API responses
Greg Bowler edited this page May 9, 2026
·
3 revisions
- Explain that WebEngine can serve structured responses as well as HTML pages.
- Explain the benefit of one routing model for both page and API endpoints.
- Explain the separate directories or conventions used for APIs.
- Explain how content negotiation and response type affect routing.
- Explain similarities to page logic.
- Explain what changes when the response is data rather than a document.
- Explain the JSONDocument vs HTMLDocument.
- Typically there's no need to write API logic for background updates to the page: server-side rendering can be made into a fluid user interface without the use of API page updates.
Next up, let's learn about how WebEngine handles configuration.
- File-based routing
- Page views
- Page logic
- Dynamic URIs
- Headers and footers
- Custom HTML components
- Page partials
- Binding data to the DOM
- DOM manipulation
- Hello You tutorial
- Todo list tutorial
- Address book tutorial WIP
- Blueprints
- Application architecture
- Coding styleguide WIP
- PHP environment setup WIP
- Web servers WIP
- Background cron tasks
- Database setup WIP
- Client-side compilation WIP
- Testing WebEngine applications WIP
- Production checklist WIP
- Security WIP