diff --git a/docs/kitchen/sink.md b/docs/kitchen/sink.md deleted file mode 100644 index e5825bfc..00000000 --- a/docs/kitchen/sink.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -foo: 123 -bar: 234 ---- - -# Kitchen Sink - -## Relative Links - -- [Go home](../README.md) -- [Setup](../setup.md) - -## Syntax Highlighting - -``` js -const a = 123 -``` - -``` html{2,10-13} -
Original message: "{{ message }}"
-Computed reversed message: "{{ reversedMessage }}"
-{{ 1 + 1 }}
+
+Directives also work:
+
+**Input**
+
+``` markdown
+{{ i }}
+```
+
+**Output**
+
+{{ i }}
+
+The compiled component does not have any private data but do have access to the [site metadata](./theming.md#site-and-page-metadata). For example:
+
+**Input**
+
+``` markdown
+{{ $page }}
+```
+
+**Output**
+
+{{ $page }}
+
+## Escaping
+
+By default, fenced code blocks are automatically wrapped with `v-pre`. If you want to display raw mustaches or Vue-specific syntax inside inline code snippets or plain text, you need to wrap a paragraph with the `v-pre` custom container:
+
+``` markdown
+::: v-pre
+`{{ This will be displayed as-is }}`
+:::
+```
+
## Using Components
Any `*.vue` file found in `.vuepress/components` are automatically registered as global async components. For example:
-``` bash
+```
.
└── .vuepress
└── components
@@ -22,9 +68,11 @@ Inside any markdown file you can then use the component like so:
```
::: warning
-Note **components must be nested inside a ``, which can only contain inline elements. +Note **components must be nested inside a `
`, which can only contain inline elements. If your component contains block level elements (it mostly likely does), it will cause hydration mismatch in static builds. ::: -## Style & Script +## Script & Style Hoisting (TODO) + +Sometimes you may need to apply some JavaScript or CSS only to the current page. In those case you can directly write root-level `