Merge pull request #1069 from preactjs/refactor/tutorial-titles

refactor: Keep tutorial titles in w/ markdown content

Author: rschristian

content/en/tutorial/01-vdom.md

@@ -1,10 +1,11 @@
 ---
 prev: /tutorial
 next: /tutorial/02-events
-title: Virtual DOM
 solvable: true
 ---
 
+# Virtual DOM
+
 You might have heard people refer to "Virtual DOM", and wondered:
 what makes it "virtual"? How is a "virtual" DOM different from
 the real DOM we use when programming for the browser?

content/en/tutorial/02-events.md

@@ -1,10 +1,11 @@
 ---
 prev: /tutorial/01-vdom
 next: /tutorial/03-components
-title: Events
 solvable: true
 ---
 
+# Events
+
 Events are how we make applications interactive, responding to inputs like
 keyboard and mouse, and reacting to changes like an image loading. Events
 work the same way in Preact as they do in the DOM – any event type or behavior

content/en/tutorial/03-components.md

@@ -1,10 +1,11 @@
 ---
 prev: /tutorial/02-events
 next: /tutorial/04-state
-title: Components
 solvable: true
 ---
 
+# Components
+
 As we alluded to in part one of this tutorial, the key building block
 in Virtual DOM applications is the Component. A Component is a self-contained
 piece of an application that can be rendered as part of the Virtual DOM

content/en/tutorial/04-state.md

@@ -1,10 +1,11 @@
 ---
 prev: /tutorial/03-components
 next: /tutorial/05-refs
-title: State
 solvable: true
 ---
 
+# State
+
 Now that we know how to create HTML elements and components, and how to
 pass props and event handlers to both using JSX, it's time to learn how
 to update the Virtual DOM tree.

content/en/tutorial/05-refs.md

@@ -1,10 +1,11 @@
 ---
 prev: /tutorial/04-state
 next: /tutorial/06-context
-title: Refs
 solvable: true
 ---
 
+# Refs
+
 As we learned in the first chapter, the DOM provides an imperative API,
 which lets us make changes by calling functions on elements. One example
 where we might need to access the imperative DOM API from a Preact

content/en/tutorial/06-context.md

@@ -1,10 +1,11 @@
 ---
 prev: /tutorial/05-refs
 next: /tutorial/07-side-effects
-title: Context
 solvable: true
 ---
 
+# Context
+
 As an application grows larger, its Virtual DOM tree often becomes deeply
 nested and composed of many different components. Components at various
 locations within the tree sometimes need to access common data - typically

content/en/tutorial/07-side-effects.md

@@ -1,10 +1,11 @@
 ---
 prev: /tutorial/06-context
 next: /tutorial/08-keys
-title: Side Effects
 solvable: true
 ---
 
+# Side Effects
+
 Side effects are bits of code that run when changes happen in the Virtual
 DOM tree. They don't follow the standard approach of accepting `props`
 and returning a new Virtual DOM tree, and often reach out of the tree

content/en/tutorial/08-keys.md

@@ -1,10 +1,11 @@
 ---
 prev: /tutorial/07-side-effects
 next: /tutorial/09-error-handling
-title: Keys
 solvable: true
 ---
 
+# Keys
+
 In chapter one, we saw how Preact uses a Virtual DOM to calculate what
 changed between two trees described by our JSX, then applies those
 changes to the HTML DOM to update pages. This works well for most

content/en/tutorial/09-error-handling.md

@@ -1,10 +1,11 @@
 ---
 prev: /tutorial/08-keys
 next: /tutorial/10-links
-title: Error Handling
 solvable: true
 ---
 
+# Error Handling
+
 JavaScript is a flexible interpreted language, which means it's possible (and even easy)
 to encounter errors at runtime. Whether the result of an unexpected scenario or a mistake
 in code we've written, it's important to be able to monitor errors and implement some form

content/en/tutorial/10-links.md

@@ -1,9 +1,10 @@
 ---
 prev: /tutorial/09-error-handling
-title: Congratulations!
 solvable: false
 ---
 
+# Congratulations!
+
 You've completed the Preact tutorial!
 
 Feel free to play around a bit more with the demo code.