Skip to content
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.

HTML pages vs API endpoints

  • Explain the separate directories or conventions used for APIs.
  • Explain how content negotiation and response type affect routing.

What API logic looks like

  • 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.

Clone this wiki locally