Enable anchor links in ECS section

content/learn/book/ecs/_index.md

@@ -4,6 +4,7 @@ weight = 2
 sort_by = "weight"
 template = "book-section.html"
 page_template = "book-section.html"
+insert_anchor_links = "right"
 +++
 
 Bevy is fundamentally powered by its ECS (a central [paradigm](https://ajmmertens.medium.com/ecs-from-tool-to-paradigm-350587cdf216) for organizing and operating on data which stands Entity-Component-System): almost all data is stored as components which belong to entities, and all logic is executed by its systems.

content/learn/book/ecs/commands/_index.md

@@ -3,6 +3,7 @@ title = "Commands queue up work"
 weight = 5
 template = "book-section.html"
 page_template = "book-section.html"
+insert_anchor_links = "right"
 +++
 
 **Commands** are powerful, unrestricted tools for deferring complex or heavily-blocking work.

content/learn/book/ecs/detecting-changes/_index.md

@@ -3,6 +3,7 @@ title = "Detecting changes"
 weight = 6
 template = "book-section.html"
 page_template = "book-section.html"
+insert_anchor_links = "right"
 +++
 
 Bevy allows you to respond to the addition of or changes to specific component types using the [`Added`] and [`Changed`] query filters.

content/learn/book/ecs/ecs-magic/_index.md

@@ -3,6 +3,7 @@ title = "Understanding the magic"
 weight = 8
 template = "book-section.html"
 page_template = "book-section.html"
+insert_anchor_links = "right"
 +++
 
 By this point, it's common for new Bevy users to have a few questions about how the high-level tools you've been introduced to actually perform their feats of cunning ergonomics.
@@ -118,4 +119,4 @@ Check out the source code (and the [section on system ordering](../../game-logic
 
 [`FunctionSystem::run_unsafe`]: https://docs.rs/bevy/latest/bevy/ecs/system/struct.FunctionSystem.html#method.run_unsafe
 [`SystemParamFetch::get_param`]: https://docs.rs/bevy/latest/bevy/ecs/system/trait.SystemParamFetch.html#tymethod.get_param
-[`ParallelExecutor`]: https://docs.rs/bevy/latest/bevy/ecs/schedule/struct.ParallelExecutor.html
+[`ParallelExecutor`]: https://docs.rs/bevy/latest/bevy/ecs/schedule/struct.ParallelExecutor.html

content/learn/book/ecs/entities-components/_index.md

@@ -3,6 +3,7 @@ title = "Entities have components"
 weight = 1
 template = "book-section.html"
 page_template = "book-section.html"
+insert_anchor_links = "right"
 +++
 
 As we discussed in the introduction to this chapter, **entities** represent objects in your game world, whose data is stored in the form of components.

content/learn/book/ecs/exclusive-world-access/_index.md

@@ -3,6 +3,7 @@ title = "Exclusive world access"
 weight = 7
 template = "book-section.html"
 page_template = "book-section.html"
+insert_anchor_links = "right"
 +++
 
 In various places, Bevy code works directly with the [`World`]'s data, gaining exclusive, blocking access to it and allowing for arbitrary mutations.

content/learn/book/ecs/queries/_index.md

@@ -3,6 +3,7 @@ title = "Fetching data with queries"
 weight = 2
 template = "book-section.html"
 page_template = "book-section.html"
+insert_anchor_links = "right"
 +++
 
 Once we have data stored on our entities in the form of components, we need to be able to get the data back out in a principled way.
@@ -281,4 +282,4 @@ As a result, we can use the same query filtering techniques described  to allow
 In addition to improving parallelism, this also reduces the false positives when checking for [system execution order ambiguities](https://docs.rs/bevy/latest/bevy/ecs/schedule/struct.ReportExecutionOrderAmbiguities.html), as we can guarantee that the relative order of two systems that do not share data never changes the final outcome.
 
 [`Transform`]: https://docs.rs/bevy/latest/bevy/transform/components/struct.Transform.html
-[`QuerySet`]: https://docs.rs/bevy/latest/bevy/ecs/system/struct.QuerySet.html
+[`QuerySet`]: https://docs.rs/bevy/latest/bevy/ecs/system/struct.QuerySet.html

content/learn/book/ecs/resources/_index.md

@@ -3,6 +3,7 @@ title = "Resources are global singletons"
 weight = 3
 template = "book-section.html"
 page_template = "book-section.html"
+insert_anchor_links = "right"
 +++
 
 Not all data is stored in the entity-component data storage.

content/learn/book/ecs/rust-tips/_index.md

@@ -3,6 +3,7 @@ title = "Rust tips and tricks"
 weight = 7
 template = "book-section.html"
 page_template = "book-section.html"
+insert_anchor_links = "right"
 +++
 
 There are a few standard Rust patterns and pitfalls that are particularly relevant to Bevy's ECS.

content/learn/book/ecs/systems/_index.md

@@ -3,6 +3,7 @@ title = "Systems do work"
 weight = 4
 template = "book-section.html"
 page_template = "book-section.html"
+insert_anchor_links = "right"
 +++
 
 In order to make useful, fun or interesting games or apps, you'll need to manipulate the data that you store in components and resources in some way.