Skip to content

Commit a555971

Browse files
authored
move table of contents further down
1 parent 7934341 commit a555971

1 file changed

Lines changed: 12 additions & 13 deletions

File tree

docs/syntax.md

Lines changed: 12 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,17 @@
11
# How to Write Custom Syntax
22

3+
PostCSS can transform styles in any syntax, and is not limited to just CSS.
4+
By writing a custom syntax, you can transform styles in any desired format.
5+
6+
Writing a custom syntax is much harder than writing a PostCSS plugin, but
7+
it is an awesome adventure.
8+
9+
There are 3 types of PostCSS syntax packages:
10+
11+
* **Parser** to parse input string to node’s tree.
12+
* **Stringifier** to generate output string by node’s tree.
13+
* **Syntax** contains both parser and stringifier.
14+
315
**Table of Contents**
416

517
* [How to Write Custom Syntax](#how-to-write-custom-syntax)
@@ -16,19 +28,6 @@
1628
* [Raw Values](#raw-values-1)
1729
* [Tests](#tests-1)
1830

19-
PostCSS can transform styles in any syntax, and is not limited to just CSS.
20-
By writing a custom syntax, you can transform styles in any desired format.
21-
22-
Writing a custom syntax is much harder than writing a PostCSS plugin, but
23-
it is an awesome adventure.
24-
25-
There are 3 types of PostCSS syntax packages:
26-
27-
* **Parser** to parse input string to node’s tree.
28-
* **Stringifier** to generate output string by node’s tree.
29-
* **Syntax** contains both parser and stringifier.
30-
31-
3231
## Syntax
3332

3433
A good example of a custom syntax is [SCSS]. Some users may want to transform

0 commit comments

Comments
 (0)