Fixed links for blc test

danjoa · danjoa · commit 8facd5e73e1c · 2025-12-22T17:49:40.000+01:00
diff --git a/cds/_menu.md b/cds/_menu.md
@@ -18,6 +18,6 @@
 # [Core / Built-in Types](types)
 # [Common Reuse Types](common)
 # [Common Annotations](annotations)
-# [Compiler Messages](../compiler/messages)
+# [Compiler Messages](/cds/compiler/messages)
 # [Aspect-oriented Modelling](aspects)
 # [The Nature of CDS Models](models)
diff --git a/cds/cdl.md b/cds/cdl.md
@@ -1575,8 +1575,7 @@ rewritten to `@Common.Text: (descr)`.
 
 ::: info
 
-There may be situations where automatic rewriting doesn't work, resulting in the compiler error
-[`anno-missing-rewrite`](https://cap.cloud.sap/docs/cds/compiler/messages#anno-missing-rewrite).
+There may be situations where automatic rewriting doesn't work, resulting in a compiler error, with message ID `anno-missing-rewrite`.
 In these cases you can overwrite the annotation with the correct expression in the new location.
 
 :::
diff --git a/get-started/best-practices.md b/get-started/best-practices.md
@@ -22,15 +22,15 @@ The CAP framework features a mix of proven and broadly adopted open-source and S
 
 The major building blocks are as follows:
 
-- [**Core Data Services** (CDS)](../cds/index.md) — CAP's universal modeling language, and the very backbone of everything; used to capture domain knowledge, generating database schemas, translating to and from various API languages, and most important: fueling generic runtimes to automatically serve request out of the box.
+- [**Core Data Services** (CDS)](../cds/) — CAP's universal modeling language, and the very backbone of everything; used to capture domain knowledge, generating database schemas, translating to and from various API languages, and most important: fueling generic runtimes to automatically serve request out of the box.
 
-- [**Service Runtimes**](../guides/services/providing-services.md) for [Node.js](../node.js) and [Java](../java/index.md) — providing the core frameworks for services, generic providers to serve requests automatically, database support for SAP HANA, SQLite, and PostgreSQL, and protocol adaptors for REST, OData, GraphQL, ...
+- [**Service Runtimes**](../guides/services/providing-services.md) for [Node.js](../node.js/) and [Java](../java/) — providing the core frameworks for services, generic providers to serve requests automatically, database support for SAP HANA, SQLite, and PostgreSQL, and protocol adaptors for REST, OData, GraphQL, ...
 
-- [**Platform Integrations**](../plugins/index.md) — providing CAP-level service interfaces (*'[Calesi](#the-calesi-pattern)'*) to cloud platform services in platform-agnostic ways, as much as possible. Some of these are provided out of the box, others as plugins.
+- [**Platform Integrations**](../plugins/) — providing CAP-level service interfaces (*'[Calesi](#the-calesi-pattern)'*) to cloud platform services in platform-agnostic ways, as much as possible. Some of these are provided out of the box, others as plugins.
 
-- [**Command-Line Interface** (CLI)](../tools/index.md) — the Swiss army knife on the tools and development kit front, complemented by integrations and support in [*SAP Build Code*](https://www.sap.com/germany/products/technology-platform/developer-tools.html), *Visual Studio Code*, *IntelliJ*, and *Eclipse*.
+- [**Command-Line Interface** (CLI)](../tools/) — the Swiss army knife on the tools and development kit front, complemented by integrations and support in [*SAP Build Code*](https://www.sap.com/germany/products/technology-platform/developer-tools.html), *Visual Studio Code*, *IntelliJ*, and *Eclipse*.
 
-In addition, there's a fast-growing number of [plugins](../plugins/index.md) contributed by open-source and inner-source [communities](/resources/index#public-resources) that enhance CAP in various ways, and integrate with additional tools and environments; the [*Calesi* plugins](about.md#the-calesi-effect) are among them.
+In addition, there's a fast-growing number of [plugins](../plugins/) contributed by open-source and inner-source [communities](/resources/index#public-resources) that enhance CAP in various ways, and integrate with additional tools and environments; the [*Calesi* plugins](about.md#the-calesi-effect) are among them.
 
 
 
diff --git a/get-started/troubleshooting.md b/get-started/troubleshooting.md
@@ -276,7 +276,7 @@ To fix this, either switch the Node.js version using a Node version manager, or
 
 ```
 
-[Learn more about the install-node goal.](../java/assets/cds-maven-plugin-site/install-node-mojo.html){.learn-more target="_blank"}
+[Learn more about the install-node goal.](/java/assets/cds-maven-plugin-site/install-node-mojo.html){.learn-more target="_blank"}
 
 ### How can I expose custom REST APIs with CAP?
 
diff --git a/guides/databases/hana.md b/guides/databases/hana.md
@@ -202,7 +202,7 @@ cds deploy --to hana
 Behind the scenes, `cds deploy` does the following:
 
 * Compiles the CDS model to SAP HANA files (usually in _gen/db_, or _db/src/gen_)
-* Generates _[.hdbtabledata](https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-deployment-infrastructure-hdi-reference/table-data-hdbtabledata)_ files for the [CSV files](#providing-initial-data) in the project. If a _[.hdbtabledata](https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-deployment-infrastructure-hdi-reference/table-data-hdbtabledata)_ file is already present next to the CSV files, no new file is generated.
+* Generates _[.hdbtabledata](https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-deployment-infrastructure-hdi-reference/table-data-hdbtabledata)_ files for the CSV files in the project. If a _[.hdbtabledata](https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-deployment-infrastructure-hdi-reference/table-data-hdbtabledata)_ file is already present next to the CSV files, no new file is generated.
 * Creates a Cloud Foundry service of type `hdi-shared`, which creates an HDI container. Also, you can explicitly specify the name like so: `cds deploy --to hana:<myService>`.
 * Starts `@sap/hdi-deploy` locally. If you need a tunnel to access the database, you can specify its address with `--tunnel-address <host:port>`.
 * Stores the binding information with profile `hybrid` in the _.cdsrc-private.json_ file of your project. You can use a different profile with parameter `--for`. With this information, `cds watch`/`run` can fetch the SAP HANA credentials at runtime, so that the server can connect to it.
@@ -557,7 +557,7 @@ CDS build performs rudimentary checks on generated _.hdmigrationtable_ files:
 - CDS build fails if manual resolution comments starting with `>>>>>` exist in one of the generated _.hdbmigrationtable_ files. This ensures that manual resolution is performed before deployment.
 
 ### Native Database Clauses {#schema-evolution-native-db-clauses}
-Not all clauses supported by SQL can directly be written in CDL syntax. To use native database clauses also in a CAP CDS model, you can provide arbitrary SQL snippets with the annotations [`@sql.prepend` and `@sql.append`](#sql-prepend-append). In this section, we're focusing on schema evolution specific details.
+Not all clauses supported by SQL can directly be written in CDL syntax. To use native database clauses also in a CAP CDS model, you can provide arbitrary SQL snippets with the annotations [`@sql.prepend` and `@sql.append`](index#sql-prepend-append). In this section, we're focusing on schema evolution specific details.
 
 Schema evolution requires that any changes are applied by corresponding ALTER statements. See [ALTER TABLE statement reference](https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-sql-reference-guide/alter-table-statement-data-definition?version=2024_1_QRC) for more information. A new migration version is generated whenever an `@sql.append` or `@sql.prepend` annotation is added, changed, or removed. ALTER statements define the individual changes that create the final database schema. This schema has to match the schema defined by the TABLE statement in the _.hdbmigrationtable_ artifact.
 Please note that the compiler doesn't evaluate or process these SQL snippets. Any snippet is taken as is and inserted into the TABLE statement and the corresponding ALTER statement. The deployment fails in case of syntax errors.
diff --git a/guides/databases/postgres.md b/guides/databases/postgres.md
@@ -618,7 +618,7 @@ If the changes in the model could lead to data loss, an error is raised.
 
 ## Migration { .node }
 
-Thanks to CAP's database-agnostic cds.ql API, we're confident that the new PostgreSQL service comes without breaking changes. Nevertheless, please check the instructions in the [SQLite Migration guide](sqlite#migrationion), with by and large applies also to the new PostgreSQL service.
+Thanks to CAP's database-agnostic cds.ql API, we're confident that the new PostgreSQL service comes without breaking changes. Nevertheless, please check the instructions in the [SQLite Migration guide](sqlite#migration), with by and large applies also to the new PostgreSQL service.
 
 ### `cds deploy --model-only`
 
diff --git a/guides/deploy/build.md b/guides/deploy/build.md
@@ -48,7 +48,7 @@ You can use them as a blue print – copy & paste them into your CDS configurati
 
 
 
-## Custom Build Tasks {#build-config}
+## Custom Build Tasks
 
 If custom build tasks are configured, those properties have precedence
 For example, you want to configure the _src_ folder and add the default models. To achieve this, do not define the _model_ option in your build task:
diff --git a/guides/events/core-concepts.md b/guides/events/core-concepts.md
@@ -183,7 +183,7 @@ As emitting and handling events is an intrinsic feature of the CAP core runtimes
 
 Let's see that in action...
 
-### 1. Run CAP Server
+### 1. Run CAP Server {#start-server}
 
 Run the following command to start a reviews-enhanced bookshop as an all-in-one server process:
 
diff --git a/guides/events/event-mesh.md b/guides/events/event-mesh.md
@@ -119,7 +119,7 @@ Before [deploying to the cloud](#deploy-to-the-cloud-with-mta), you may want to
 
     [Learn more about `cds.env` profiles.](../../node.js/cds-env#profiles){.learn-more}
 
-6. Test your app [as described in the messaging guide](./#add-or-update-reviews).
+6. Test your app [as described in the messaging guide](messaging#add-or-update-reviews).
 
 
 ### CAP Automatically Creates Queues and Subscriptions
diff --git a/guides/events/messaging.md b/guides/events/messaging.md
@@ -61,7 +61,7 @@ For quick tests during development, CAP provides a simple file-based messaging s
 In our samples, you find that in [@capire/reviews/package.json](https://github.com/capire/reviews/blob/main/package.json) as well as [@capire/bookstore/package.json](https://github.com/capire/bookstore/blob/main/package.json), which you'll run in the next step as separate processes.
 
 
-### 2. Start the `reviews` Service and `bookstore` Separately
+### 2. Start the `reviews` Service and `bookstore` Separately 
 
 First start the `reviews` service separately:
 
@@ -85,7 +85,7 @@ Then, in a separate terminal start the `bookstore` server as before:
 cds watch bookstore
 ```
 
-This time the trace output is different to [when you started all in a single server](#start-single-server). The output confirms that you're using `file-based-messaging`, and that you now *connected* to the separately started `ReviewsService` at port 4005:
+This time the trace output is different to [when you started all in a single server](./core-concepts#start-server). The output confirms that you're using `file-based-messaging`, and that you now *connected* to the separately started `ReviewsService` at port 4005:
 
 ```log
 [cds] - connect to messaging > file-based-messaging { file: '~/.cds-msg-box' }
@@ -98,7 +98,7 @@ This time the trace output is different to [when you started all in a single ser
 [cds] - launched at 5/25/2023, 4:55:46 PM, version: 7.0.0, in: 1.053s
 ```
 
-### 3. Add or Update Reviews {#add-or-update-reviews-2}
+### 3. Add or Update Reviews {#add-or-update-reviews}
 
 Similar to before, open [http://localhost:4005/vue/index.html](http://localhost:4005/vue/index.html) to add or update reviews.
 
diff --git a/guides/events/s4.md b/guides/events/s4.md
@@ -68,7 +68,7 @@ extend service S4 with {
 ```
 
 ::: tip
-If using SAP Event Mesh, please see [CloudEvents Standard](./index.md#cloudevents) and [Node - Messaging - CloudEvents Protocol](../../node.js/messaging.md#cloudevents-protocol) to learn about `format: 'cloudevents'`, `publishPrefix` and `subscribePrefix`.
+If using SAP Event Mesh, please see [CloudEvents Standard](messaging#cloudevents) and [Node - Messaging - CloudEvents Protocol](../../node.js/messaging#cloudevents-protocol) to learn about `format: 'cloudevents'`, `publishPrefix` and `subscribePrefix`.
 :::
 
 <div id="events-policy-sap" />
diff --git a/guides/extensibility/customization.md b/guides/extensibility/customization.md
@@ -285,19 +285,19 @@ Here's a rough checklist what this guide should cover:
 
 ### 5. Deploy Application
 
-Before deploying your SaaS application to the cloud, you can [test-drive it locally](../multitenancy/#test-locally).
+Before deploying your SaaS application to the cloud, you can [test-drive it locally](../multitenancy/index#test-drive-locally).
 Prepare this by going back to your app with `cd orders`.
 
 With your application enabled and prepared for extensibility, you are ready to deploy the application as described in the  [Deployment Guide](../deploy/).
 
 ## As a SaaS Customer {#prep-as-operator}
 
 The following sections provide step-by-step instructions on adding extensions.
-All steps are based on our Orders Management sample which can be [started locally for testing](../multitenancy/#test-locally).
+All steps are based on our Orders Management sample which can be [started locally for testing](../multitenancy/index#test-drive-locally).
 
 ::: details On BTP…
 
-To extend a SaaS app deployed to BTP, you'll need to subscribe to it [through the BTP cockpit](../multitenancy/#subscribe).
+To extend a SaaS app deployed to BTP, you'll need to subscribe to it [through the BTP cockpit](../multitenancy/index#subscribe-via-btp-cockpit).
 
 Refer to the [Deployment Guide](../deploy/to-cf) for more details on remote deployments.
 
@@ -456,7 +456,7 @@ annotate OrdersService.Orders with @UI.LineItem: [
 Make sure **no syntax errors** are shown in the [CDS editor](../../tools/cds-editors#vscode) before going on to the next steps.
 :::
 
-### 7. Test-Drive Locally {#test-locally }
+### 7. Test-Drive Locally {#test-locally}
 
 To conduct an initial test of your extension, run it locally with `cds watch`:
 
diff --git a/guides/multitenancy/index.md b/guides/multitenancy/index.md
@@ -245,7 +245,7 @@ In case of **CAP Java** projects, the `cds add multitenancy` command...
   You can always inspect the _effective_ configuration with `cds env`.
   :::
 
-## Test-Drive Locally {#test-locally}
+## Test-Drive Locally
 
 
 Before deploying to the cloud, you can test-drive common SaaS operations with your app locally, including SaaS startup, subscribing tenants, and upgrading tenants.
@@ -565,7 +565,7 @@ In order to get your multitenant application deployed, follow this excerpt from
 
 :::tip For manual setups, ensure the metadata container (`t0`) is unique
 
-If you’re not running `cds-mtx upgrade *` as a [Cloud Foundry hook](#run-as-cloud-foundry-hook) (as set up by `cds add multitenancy`) and instead use a custom setup, deploy the MTX sidecar with a single instance for the initial rollout. This avoids conflicts when `t0` is created.
+If you’re not running [`cds-mtx upgrade *`](#update-database-schema) as a Cloud Foundry hook (as set up by `cds add multitenancy`) and instead use a custom setup, deploy the MTX sidecar with a single instance for the initial rollout. This avoids conflicts when `t0` is created.
 
 :::
 
@@ -735,7 +735,7 @@ Each time you update your model or any SAP HANA source file, you need repeat the
 
 > Make sure to stop any running CAP servers left over from local testing.
 
-By passing `--profile hybrid` you can now run the app with cloud bindings and interact with it as you would while [testing your app locally](#test-locally). Run this in your project root:
+By passing `--profile hybrid` you can now run the app with cloud bindings and interact with it as you would while [testing your app locally](#test-drive-locally). Run this in your project root:
 
 ```sh
 cds watch mtx/sidecar --profile hybrid
diff --git a/guides/multitenancy/mtxs.md b/guides/multitenancy/mtxs.md
@@ -151,7 +151,7 @@ cds watch --profile local-multitenancy
 
 ### Testing With Minimal Setup
 
-When designing test suites that run frequently in CI/CD pipelines, you can shorten runtimes and reduce costs. First run a set of functional tests which use MTX in minimized setups – that is, with local servers and in-memory databases as introduced in the [_Multitenancy_ guide](../multitenancy/#test-locally).
+When designing test suites that run frequently in CI/CD pipelines, you can shorten runtimes and reduce costs. First run a set of functional tests which use MTX in minimized setups – that is, with local servers and in-memory databases as introduced in the [_Multitenancy_ guide](../multitenancy/index#test-drive-locally).
 
 Only in the second and third phases, you would then run the more advanced hybrid tests. These hybrid tests could include testing tenant subscriptions with SAP HANA, or integration tests with the full set of required cloud services.
 
diff --git a/guides/uis/fiori.md b/guides/uis/fiori.md
@@ -480,7 +480,7 @@ CAP generates side-effect annotations in the EDMX to instruct UI5 to fetch state
   annotate MyService.MyEntity with @Common.SideEffects #alwaysFetchMessages: null;
   ```
 
-For this feature to work correctly, CAP adds additional elements to your draft-enabled entities and [`DraftAdministrativeData`](/@external/guides/security/data-privacy#personal-data-stored-by-cap) to store and serve the state messages. CAP runtimes persist (error) messages for draft-enabled entities.
+For this feature to work correctly, CAP adds additional elements to your draft-enabled entities and [`DraftAdministrativeData`](../security/data-privacy#personal-data-stored-by-cap) to store and serve the state messages. CAP runtimes persist (error) messages for draft-enabled entities.
 
 ::: warning Requires Schema Update
 This feature initiates a database schema update, as it adds an additional element to `DraftAdministrativeData`.
diff --git a/java/cqn-services/persistence-services.md b/java/cqn-services/persistence-services.md
@@ -408,7 +408,7 @@ At runtime you need to ensure to access the tenant-dependent entities through th
 
 #### Local Development and Testing with MTX
 
-In case you are testing your multitenant application locally with the setup described in [Local Development and Testing](../../guides/multitenancy/#test-locally), you need to perform additional steps to create an in-memory tenant-independent datasource.
+In case you are testing your multitenant application locally with the setup described in [Local Development and Testing](../../guides/multitenancy/index#test-drive-locally), you need to perform additional steps to create an in-memory tenant-independent datasource.
 
 To create an in-memory datasource, initialized with the SQL schema, add the following configuration to your Spring Boot application:
 
diff --git a/java/developing-applications/running.md b/java/developing-applications/running.md
@@ -105,7 +105,7 @@ Spring Boot Devtools only detects changes to .class files. You need to enable th
 ## Multitenant Applications
 
 With the streamlined MTX, you can run your multitenant application locally along with the MTX sidecar and use SQLite as the database.
-See [the _Multitenancy_ guide](../../guides/multitenancy/#test-locally) for more information.
+See [the _Multitenancy_ guide](../../guides/multitenancy/index#test-drive-locally) for more information.
 
 ## Debugging
 
@@ -126,4 +126,3 @@ Once this is added, you can use the restart capabilities of the Spring Boot Devt
     * Configuration files (for example, _application.yaml_)
     * Artifacts generated from CDS (schema.sql, CSN, EDMX)
     * Any other static resource
-
diff --git a/java/messaging.md b/java/messaging.md
@@ -88,7 +88,7 @@ In section [CDS-Declared Events](#cds-declared-events), we show how to declare e
 The messages are sent once the transaction is successful. Per default, an in-memory outbox is used, but there's also support for a [persistent outbox](./outbox#persistent).
 
 You can configure a [custom outbox](./outbox#custom-outboxes) for a messaging service by setting the property
-`cds.messaging.services.<key>.outbox.name` to the name of the custom outbox. This specifically makes sense when [using multiple channels](../guides/events/#using-multiple-channels).
+`cds.messaging.services.<key>.outbox.name` to the name of the custom outbox. This specifically makes sense when [using multiple channels](../guides/events/messaging#using-multiple-channels).
 :::
 
 
@@ -877,6 +877,6 @@ private void ratingChanged(ReviewedContext context) {
 }
 ```
 
-[Learn more about **CloudEvents**.](../guides/events/#cloudevents){.learn-more}
+[Learn more about **CloudEvents**.](../guides/events/messaging#cloudevents){.learn-more}
 
 <span id="aftercloudevents" />
diff --git a/node.js/index.md b/node.js/index.md
diff --git a/node.js/messaging.md b/node.js/messaging.md
diff --git a/plugins/index.md b/plugins/index.md
