diff --git a/site/content/docs/01-component-format.md b/site/content/docs/01-component-format.md
new file mode 100644
index 0000000000..94c19c2e44
--- /dev/null
+++ b/site/content/docs/01-component-format.md
@@ -0,0 +1,34 @@
+---
+title: Component format
+---
+
+Components are the building blocks of Svelte applications. They are written into `.svelte` files, using a superset of HTML:
+
+```html
+<script>
+	// logic goes here
+</script>
+
+<style>
+	/* styles go here */
+</style>
+
+<!-- markup (zero or more items) goes here -->
+```
+
+All three sections — script, styles and markup — are optional.
+
+
+### Script
+
+A `<script>` block defines the behaviour for a component.
+
+* TODO explain run-on-initialisation
+* export
+* $:
+* $
+
+### Styles
+
+
+### Markup
\ No newline at end of file
diff --git a/site/content/docs/99-outline.md b/site/content/docs/99-outline.md
index f53bb2c784..57d2197387 100644
--- a/site/content/docs/99-outline.md
+++ b/site/content/docs/99-outline.md
@@ -4,7 +4,17 @@ title: Outline
 
 (This isn't the actual documentation, this is just me getting my thoughts straight so that we can create the documentation.)
 
-I think it makes sense to split the docs into compile time (`svelte.preprocess` and `svelte.compile`), then run time (component API, `svelte`, `svelte/store`, `svelte/motion`, etc). I'm not sure where template syntax, style scoping (and `:global(...)`), `context="module"` etc goes.
+I think it makes sense to split the docs into component format (script, style, markup), compile time (`svelte.preprocess` and `svelte.compile`), then run time (component API, `svelte`, `svelte/store`, `svelte/motion`, etc). I'm not sure where template syntax, style scoping (and `:global(...)`), `context="module"` etc goes.
+
+
+### Component format
+
+* .svelte
+* `<script>`
+* `<style>`
+* markup
+* `<script context="module">`
+
 
 ### Compile time