Reorder menu item and improve slug names

Ndpnt · Ndpnt · commit b36d6a7487fb · 2025-04-09T17:24:26.000+02:00
diff --git a/content/collections/how-to/create-repositories.md b/content/collections/how-to/create-repositories.md
@@ -1,6 +1,6 @@
 ---
 title: Create repositories
-weight: 1
+weight: 2
 ---
 
 # How to create collection repositories
diff --git a/content/collections/how-to/create.md b/content/collections/how-to/create.md
@@ -1,6 +1,6 @@
 ---
 title: Create a collection
-weight: 3
+weight: 1
 ---
 
 # How to create a collection
diff --git a/content/collections/how-to/define-metadata.md b/content/collections/how-to/define-metadata.md
@@ -1,6 +1,6 @@
 ---
 title: Define metadata
-weight: 2
+weight: 3
 ---
 
 # How to define metadata
diff --git a/content/collections/how-to/take-over.md b/content/collections/how-to/take-over.md
@@ -1,6 +1,6 @@
 ---
 title: Take over a collection
-weight: 2
+weight: 4
 ---
 
 # How to take over a collection
diff --git a/content/collections/reference/configuration.md b/content/collections/reference/configuration.md
@@ -1,6 +1,6 @@
 ---
 title: Configuration
-weight: 2
+weight: 3
 ---
 
 # Configuration options
diff --git a/content/collections/reference/environment-variables.md b/content/collections/reference/environment-variables.md
@@ -1,6 +1,6 @@
 ---
 title: Environment variables
-weight: 3
+weight: 4
 ---
 
 ## Environment variables
diff --git a/content/collections/reference/governance.md b/content/collections/reference/governance.md
@@ -1,6 +1,6 @@
 ---
 title: Governance
-weight: 4
+weight: 1
 aliases: /collections/governance/
 ---
 
diff --git a/content/collections/reference/metadata.md b/content/collections/reference/metadata.md
@@ -1,6 +1,6 @@
 ---
 title: Metadata
-weight: 1
+weight: 2
 aliases: /collections/metadata/
 ---
 
diff --git a/content/terms/how-to/be-notified.md b/content/terms/how-to/be-notified.md
@@ -1,5 +1,7 @@
 ---
-title: Be notified of terms changes
+title: How to be notified of terms changes
+weight: 4
+linkTitle: Be notified of changes
 aliases:
   - /subscribe-rss/
   - /terms/how-to-be-notified-of-terms-changes/
diff --git a/content/terms/how-to/get-the-validUntil-date-from-an-issue.md b/content/terms/how-to/get-the-validUntil-date-from-an-issue.md
@@ -1,6 +1,7 @@
 ---
-title: How to get the `validUntil`
+title: How to get the `validUntil` date
 linkTitle: Get the `validUntil` date
+weight: 7   
 ---
 
 # How to get the `validUntil` date
diff --git a/content/terms/how-to/rename-a-service.md b/content/terms/how-to/rename-a-service.md
@@ -1,8 +1,9 @@
 ---
 title: How to rename a service
 linkTitle: Rename a service
+weight: 5
 ---
 
 # How to rename a service
 
-The consensus is to consider that a service provider renaming a service (for example, `Twitter` to `X`) is akin to terminating the previous service and opening a new one. Therefore, to apply a service renaming, open a pull request that both [terminates the previous service](#how-to-terminate-a-service) and adds a new [service declaration]({{< relref "terms/how-to/track-new-terms#declaring-a-new-service" >}}) with the new service name. You can reuse the `terms` part of the original declaration, but should double-check that the selectors and URLs still match, as a service rename is most often accompanied by a new page layout, a new domain name, and sometimes entirely new terms.
+The consensus is to consider that a service provider renaming a service (for example, `Twitter` to `X`) is akin to terminating the previous service and opening a new one. Therefore, to apply a service renaming, open a pull request that both [terminates the previous service](#how-to-terminate-a-service) and adds a new [service declaration]({{< relref "terms/how-to/track-terms#declaring-a-new-service" >}}) with the new service name. You can reuse the `terms` part of the original declaration, but should double-check that the selectors and URLs still match, as a service rename is most often accompanied by a new page layout, a new domain name, and sometimes entirely new terms.
diff --git a/content/terms/how-to/terminate-a-service.md b/content/terms/how-to/terminate-a-service.md
@@ -1,6 +1,7 @@
 ---
 title: How to terminate a service
 linkTitle: Terminate a service
+weight: 6
 ---
 
 # How to terminate a service
diff --git a/content/terms/how-to/test-declarations.md b/content/terms/how-to/test-declarations.md
@@ -1,9 +1,12 @@
 ---
-title: "Test your declarations"
-weight: 4
+title: How to test your declarations
+weight: 3
+linkTitle: Test declarations
+aliases:
+  - /terms/how-to/test-declaration/
 ---
 
-# Test your declarations
+# How to test your declarations
 
 When creating or modifying service declarations, it’s important to verify they work as expected before starting to track in production. The Open Terms Archive engine provides automated testing tools to that end.
 
diff --git a/content/terms/how-to/track-terms-using-UI.md b/content/terms/how-to/track-terms-using-UI.md
@@ -1,11 +1,13 @@
 ---
-title: Add terms with the graphical contribution interface
-linkTitle: Add terms with UI
+title: How to track terms using the graphical contribution interface
+weight: 2
+linkTitle: Track terms with UI
 aliases: 
   - /terms/how-to-add-terms-using-with-the-graphical-contribution-interface/
+  - /terms/how-to/add-terms-using-ui/
 ---
 
-# How to add terms with the graphical contribution interface
+# How to track terms using the graphical contribution interface
 
 ## Screencast
 
diff --git a/content/terms/how-to/track-terms.md b/content/terms/how-to/track-terms.md
@@ -1,8 +1,9 @@
 ---
 title: Track new terms
-weight: 2
+weight: 1
 aliases: 
   - /contributing-terms/
+  - /terms/how-to/track-new-terms/
 ---
 
 # How to track new terms
