move table of contents further down

This commit is contained in:
muddv
2022-09-28 20:38:51 +03:00
committed by GitHub
parent 52b21a7dbc
commit b839f2cbca
+12 -13
View File
@@ -1,5 +1,17 @@
# How to Write Custom Syntax
PostCSS can transform styles in any syntax, and is not limited to just CSS.
By writing a custom syntax, you can transform styles in any desired format.
Writing a custom syntax is much harder than writing a PostCSS plugin, but
it is an awesome adventure.
There are 3 types of PostCSS syntax packages:
* **Parser** to parse input string to node’s tree.
* **Stringifier** to generate output string by node’s tree.
* **Syntax** contains both parser and stringifier.
**Table of Contents**
* [How to Write Custom Syntax](#how-to-write-custom-syntax)
@@ -16,19 +28,6 @@
* [Raw Values](#raw-values-1)
* [Tests](#tests-1)
PostCSS can transform styles in any syntax, and is not limited to just CSS.
By writing a custom syntax, you can transform styles in any desired format.
Writing a custom syntax is much harder than writing a PostCSS plugin, but
it is an awesome adventure.
There are 3 types of PostCSS syntax packages:
* **Parser** to parse input string to node’s tree.
* **Stringifier** to generate output string by node’s tree.
* **Syntax** contains both parser and stringifier.
## Syntax
A good example of a custom syntax is [SCSS]. Some users may want to transform