From c5a9033403b15c24e739433ff56c1c19a7619dd8 Mon Sep 17 00:00:00 2001 From: Masatake Iwasaki Date: Thu, 28 Mar 2024 22:27:29 +0900 Subject: [PATCH] fix: fix dead links to documentation of Samples Signed-off-by: Masatake Iwasaki --- developer/handbook.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/developer/handbook.md b/developer/handbook.md index b8500b171..d24d7536b 100644 --- a/developer/handbook.md +++ b/developer/handbook.md @@ -54,8 +54,8 @@ collection of libraries and modules, that are published as Maven artifacts, and Therefore, if you are a solution architect looking for a high-level description on how to integrate EDC, or a developer wanting to contribute to the project itself, this guide is not for you. More suitable resources can be -found [here](../docs/documentation/) -and [here](../docs/documentation/CONTRIBUTING.md) respectively. +found [here](/documentation/) +and [here](/documentation/CONTRIBUTING.md) respectively. However, if you are a developer who is familiar with Java (17+) and the Gradle build system in general, and concepts like extensibility, dependency injection and modularity, then this guide is for you. @@ -98,15 +98,15 @@ Typically, distributions consist of a [control plane](#the-control-plane) and on more [data planes](#the-data-plane). The former takes care of data manipulation, contract negotiation and transfer setup, and is geared toward reliability, whereas the job of the latter is to actually shovel bits from A to B. -The EDC project provides a comprehensive collection of [samples](../docs/samples/), including one +The EDC project provides a comprehensive collection of [samples](/samples/), including one that demonstrates -the [assembly of a very simplistic distribution](../docs/samples/basic/basic-01-basic-connector/). +the [assembly of a very simplistic distribution](/samples/basic/basic-01-basic-connector/). This simplest of distributions doesn't do much yet, it cannot even be configured properly, but it serves as starting point for more complex distributions and launchers. Subsequent chapters of this document will assume a full understanding of the concepts and terms presented in -the [basic samples](../docs/samples/basic/), so please make sure you go through them +the [basic samples](/samples/basic/), so please make sure you go through them carefully. ### Perform a simple data transfer @@ -129,7 +129,7 @@ could install the same Linux distro on multiple computers, for demonstration pur distributions, but located in different directories and pre-loaded with different config values. Please work through -the [complete sample](../docs/samples/transfer/transfer-01-file-transfer/), look +the [complete sample](/samples/transfer/), look at the enclosed source code and try to modify some values and see how they affect the data transfer. > Be advised that some of the concepts presented there are only suitable in a sample/demo environment and are not @@ -148,7 +148,7 @@ to it through a proxy, and can obtain the data. We call this a "consumer-pull" t Please be advised that the sample will use some concepts and terms we haven't discussed yet, such as [policies](#policy-scopes-and-evaluation) and [data plane registration](#data-plane-selectors). Bear with us, we will explain them later. For now, please just make sure you follow -the [http-pull sample guide](../docs/samples/transfer/transfer-06-consumer-pull-http/README.md). +the [http-pull sample guide](/samples/transfer/transfer-02-consumer-pull/). We encourage you to play around with this sample a bit, try to add a new asset and see if you can work out what else you need in order to be able to transfer it to the consumer.