Page views

• Define a page view as the HTML that represents the response.
• Explain why views stay in HTML rather than being assembled with string output.

Static HTML as the starting point

• Explain authoring pages as normal HTML first.
• Explain how default placeholder content can remain useful before binding.
• This is really good for starting a prototype, and can convert a prototype to production without needing to rewrite.

How views are loaded

• Explain the relationship between the requested URL and the matching view file.
• Explain how multiple view files can contribute to one response: custom components and page templates - link to the relevant sections of the relevant pages.

Good practices for page views

• Encourage semantic HTML and clear structure.
• Encourage designing the page shape before introducing logic.

---

When views need to be made dynamic, we'll use page logic.