wip

Author: dg

latte/en/@left-menu.texy

@@ -16,7 +16,6 @@
 - For Developers 🧮
 	- [Practices for Developers |develop]
 	- [Extending Latte]
-	- [Creating an Extension |creating-extension]
 
 - [Cookbook 💡|cookbook/@home]
 	- [Migration from Twig |cookbook/migration-from-twig]

latte/en/compiler-passes.texy

@@ -22,7 +22,7 @@ API Changes
 
 The API changes only apply to adding custom tags. The rest of the API remains the same as version 2, i.e. the same way to render templates, pass parameters, register filters.
 
-The exception is the replacement of the so-called dynamic filter `Engine::addFilter(null, ...)` with [filter loader |/extending-latte#Filter Loader], which differs in that it always returns callable and is registered with the `Engine::addFilterLoader()` method.
+The exception is the replacement of the so-called dynamic filter `Engine::addFilter(null, ...)` with [filter loader |/custom-filters#Filter Loader], which differs in that it always returns callable and is registered with the `Engine::addFilterLoader()` method.
 
 The API for adding custom tags is completely different, so add-ons designed for Latte 2 won't work with it. See also [#Updates to add-ons].
 
@@ -53,7 +53,7 @@ And more edge cases:
 Updates to Add-Ons
 ==================
 
-With the complete rewrite of the parser, the way to write custom tags has completely changed. If you have custom tags created for Latte, you will need to re-write them for version 3, see [documentation|/creating-extension].
+With the complete rewrite of the parser, the way to write custom tags has completely changed. If you have custom tags created for Latte, you will need to re-write them for version 3, see [documentation|/custom-tags].
 
 If you are using a foreign add-on that adds tags, you will need to wait until the author releases a version for Latte 3. The `nette/application`, `nette/caching` and `nette/forms` libraries in version 3.1, as well as Texy, have already been updated and work with both Latte 2 and 3.
 
@@ -208,7 +208,7 @@ $this->latte->onCompile[] = function (Latte\Engine $latte) {
 };
 ```
 
-Latte 3 is extended using [extensions|/creating-extension]. A trivial extension adding the `foo` tag would look like this:
+Latte 3 is extended using [extensions|/extending-latte]. A trivial extension adding the `foo` tag would look like this:
 
 ```php
 // new code for Latte 3
@@ -254,7 +254,7 @@ class FooNode extends Latte\Compiler\Nodes\StatementNode
 }
 ```
 
-Furthermore, the mask in `$context->format()` no longer has `%node.***` abbreviations, it is assumed that you [parse the tag content |/creating-extension#Tag Parsing Function] first. So we use the parser to parse the content into variables (subnodes), and then we write it out:
+Furthermore, the mask in `$context->format()` no longer has `%node.***` abbreviations, it is assumed that you [parse the tag content |/custom-tags#Tag Parsing Function] first. So we use the parser to parse the content into variables (subnodes), and then we write it out:
 
 ```php
 use Latte\Compiler\Nodes\Php\Expression\ArrayNode;
@@ -286,7 +286,7 @@ class FooNode extends Latte\Compiler\Nodes\StatementNode
 }
 ```
 
-Finally, we will add the `getIterator()` method to allow subnodes to be traversed when [traversing |/creating-extension#Node Traverser]:
+Finally, we will add the `getIterator()` method to allow subnodes to be traversed when [traversing |/custom-tags#Node Traverser]:
 
 ```php
 class FooNode extends Latte\Compiler\Nodes\StatementNode