@@ -68,15 +68,14 @@ For documentation build tests:
68
68
Where possible try to port directly from that.
69
69
It is usually better to modify existing code, instead of writing all from scratch.
70
70
2 . Try to find the right place for your plugin rule:
71
-
72
- - Will it conflict with existing markup (by priority)?
73
- - If yes - you need to write an inline or block rule.
74
- - If no - you can morph tokens within core chains.
75
- - Remember that token morphing in core chains is always more simple than writing
76
- block or inline rules, if you don't copy existing ones. However,
77
- block and inline rules are usually faster.
78
- - Sometimes, it's enough to only modify the renderer, for example, to add
79
- header IDs or ` target="_blank" ` for the links.
71
+ - Will it conflict with existing markup (by priority)?
72
+ - If yes - you need to write an inline or block rule.
73
+ - If no - you can morph tokens within core chains.
74
+ - Remember that token morphing in core chains is always more simple than writing
75
+ block or inline rules, if you don't copy existing ones. However,
76
+ block and inline rules are usually faster.
77
+ - Sometimes, it's enough to only modify the renderer, for example, to add
78
+ header IDs or ` target="_blank" ` for the links.
80
79
81
80
## FAQ
82
81
0 commit comments