Fix FF! Reference URLs for components listing page (#4)

Co-authored-by: philipsens <12416423+philipsens@users.noreply.github.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>

Author: Copilot

docs/get-started/index.md

@@ -31,7 +31,7 @@ You define your integrations in XML configuration files. The framework loads the
 </Adapter>
 ```
 
-This creates an HTTP endpoint at `/api/hello` that responds with "Hello, World!".
+This creates an HTTP endpoint at `/api/hello` that responds with "Hello, World!". See the [`FixedResultPipe` reference](https://reference.frankframework.org/#/Components/Pipes/FixedResultPipe) for all available attributes.
 
 ## Choose Your Setup
 

docs/manual/configuration/basics.md

@@ -75,11 +75,11 @@ Each exit has a `name`, a `state` (SUCCESS or ERROR), and an HTTP response `code
 
 ## Pipes
 
-Pipes are the processing units inside a pipeline. Each pipe has a `name` attribute and one or more `<Forward>` elements controlling flow.
+Pipes are the processing units inside a pipeline. Each pipe has a `name` attribute and one or more `<Forward>` elements controlling flow. For a complete and up-to-date list of all available pipes and their attributes, see the [FF! Reference](https://reference.frankframework.org/#/components).
 
 ### EchoPipe
 
-Returns its input unchanged, or a fixed value if `getInputFromFixedValue` is set.
+Returns its input unchanged, or a fixed value if `getInputFromFixedValue` is set. See the [EchoPipe reference](https://reference.frankframework.org/#/Components/Pipes/EchoPipe) for all available attributes.
 
 ```xml
 <EchoPipe
@@ -91,7 +91,7 @@ Returns its input unchanged, or a fixed value if `getInputFromFixedValue` is set
 
 ### XmlValidatorPipe
 
-Validates the incoming XML message against an XSD schema.
+Validates the incoming XML message against an XSD schema. See the [XmlValidatorPipe reference](https://reference.frankframework.org/#/Components/Pipes/XmlValidatorPipe) for all available attributes.
 
 ```xml
 <XmlValidatorPipe
@@ -109,7 +109,7 @@ Validates the incoming XML message against an XSD schema.
 
 ### SenderPipe
 
-Wraps a sender to communicate with external systems (databases, services, etc.).
+Wraps a sender to communicate with external systems (databases, services, etc.). See the [SenderPipe reference](https://reference.frankframework.org/#/Components/Pipes/SenderPipe) for all available attributes.
 
 ```xml
 <SenderPipe name="insertBooking">
@@ -128,7 +128,7 @@ Wraps a sender to communicate with external systems (databases, services, etc.).
 
 ### XsltPipe
 
-Applies an XSLT stylesheet to transform XML.
+Applies an XSLT stylesheet to transform XML. See the [XsltPipe reference](https://reference.frankframework.org/#/Components/Pipes/XsltPipe) for all available attributes.
 
 ```xml
 <XsltPipe
@@ -144,7 +144,7 @@ Applies an XSLT stylesheet to transform XML.
 
 ### ForEachChildElementPipe
 
-Iterates over XML elements matching an XPath expression, applying a sender to each.
+Iterates over XML elements matching an XPath expression, applying a sender to each. See the [ForEachChildElementPipe reference](https://reference.frankframework.org/#/Components/Pipes/ForEachChildElementPipe) for all available attributes.
 
 ```xml
 <ForEachChildElementPipe

docs/manual/configuration/custom-code.md

@@ -6,7 +6,7 @@ Custom Java code can extend the Frank!Framework when standard building blocks ar
 
 ## Extending FixedForwardPipe
 
-Derive custom pipes from `org.frankframework.pipes.FixedForwardPipe` and implement:
+Derive custom pipes from [`org.frankframework.pipes.FixedForwardPipe`](https://reference.frankframework.org/#/Components/Pipes/FixedForwardPipe) and implement:
 
 ```java
 public PipeRunResult doPipe(Message message, PipeLineSession session) throws PipeRunException

docs/manual/configuration/integration-patterns.md

@@ -2,6 +2,8 @@
 
 The Frank!Framework connects applications from different vendors, transforming requests and responses between otherwise incompatible systems. This document covers patterns and features for protecting data integrity during integration.
 
+For details on the pipes and senders used in these examples, see the [FF! Reference](https://reference.frankframework.org/#/components).
+
 ## Request/Reply
 
 System A sends a request to system B. System B processes the request immediately and returns a response indicating success or failure. The sender waits for the response before proceeding.

docs/manual/configuration/large-messages.md

@@ -40,7 +40,7 @@ This limitation applies equally to XPath expressions, which use XSLT processing
 
 ## ForEachChildElementPipe Streaming
 
-`ForEachChildElementPipe` defaults to Xalan (`xsltVersion=1`) rather than Saxon. This exception exists because `ForEachChildElementPipe` is designed to iterate over large messages and requires streaming support.
+[`ForEachChildElementPipe`](https://reference.frankframework.org/#/Components/Pipes/ForEachChildElementPipe) defaults to Xalan (`xsltVersion=1`) rather than Saxon. This exception exists because `ForEachChildElementPipe` is designed to iterate over large messages and requires streaming support.
 
 Most other pipes and senders default to Saxon (XSLT 2.0+).
 

docs/manual/configuration/properties.md

@@ -1,6 +1,6 @@
 # Properties
 
-Properties are name/value pairs that configure Frank!Framework behavior and allow Frank configurations to adapt to different deployment environments.
+Properties are name/value pairs that configure Frank!Framework behavior and allow Frank configurations to adapt to different deployment environments. For a complete and up-to-date list of all available properties, see the [FF! Reference](https://reference.frankframework.org/#/properties).
 
 ## Property Syntax and Referencing
 

docs/manual/configuration/values.md

@@ -11,7 +11,7 @@ Session keys act as variables that hold the same kind of data as the message flo
 - `originalMessage` — the pipeline's input message
 - `httpMethod` — the HTTP method (when using an `ApiListener`)
 
-Custom session keys can be written with `PutInSessionPipe`:
+Custom session keys can be written with [`PutInSessionPipe`](https://reference.frankframework.org/#/Components/Pipes/PutInSessionPipe):
 
 ```xml
 <PutInSessionPipe name="save" sessionKey="saved"/>
@@ -84,7 +84,7 @@ Only the `<Param>` element can obtain context key values. The parameter must the
 
 ## ReplacerPipe Pattern Substitution
 
-`ReplacerPipe` substitutes both property references (`${...}`) and parameter references (`?{...}`) in its input. When the `find` attribute is omitted, no text replacement occurs — only property and parameter substitution.
+[`ReplacerPipe`](https://reference.frankframework.org/#/Components/Pipes/ReplacerPipe) substitutes both property references (`${...}`) and parameter references (`?{...}`) in its input. When the `find` attribute is omitted, no text replacement occurs — only property and parameter substitution.
 
 ```xml
 <ReplacerPipe name="replace" getInputFromFixedValue="Property value ${my.property} and parameter value ?{my.param}">
@@ -96,7 +96,7 @@ Output: `Property value My property value and parameter value My parameter value
 
 ## EchoPipe Property Substitution
 
-`EchoPipe` substitutes **properties only** (`${...}`). It does not substitute parameters (`?{...}`).
+[`EchoPipe`](https://reference.frankframework.org/#/Components/Pipes/EchoPipe) substitutes **properties only** (`${...}`). It does not substitute parameters (`?{...}`).
 
 ## Complete Example
 

docs/manual/deployment/authorization.md

@@ -32,6 +32,8 @@ Authentication is configured via properties prefixed with:
 - `application.security.console.authentication.` — for the Frank!Console and Ladybug.
 - `application.security.http.authenticators.<name>.` — for HTTP interfaces.
 
+For a complete and up-to-date list of all available servlet authenticators and their configuration options, see the [FF! Reference for servlet authenticators](https://reference.frankframework.org/#/servlet-authenticators).
+
 | Type | Description | Properties |
 |---|---|---|
 | `NONE` | No authorization required | — |
@@ -134,7 +136,7 @@ Console and Ladybug authentication properties use the prefix `application.securi
 
 ## Credentials Management
 
-Credentials keep secrets (usernames, passwords) out of Frank configurations and log files.
+Credentials keep secrets (usernames, passwords) out of Frank configurations and log files. For a complete list of all available credential providers and their configuration options, see the [FF! Reference for credential providers](https://reference.frankframework.org/#/credential-providers).
 
 ### Credential Factories
 

docs/manual/deployment/credentials.md

@@ -1,6 +1,6 @@
 # Credentials Management
 
-Credentials keep secrets (usernames, passwords) out of Frank configurations and log files. They are managed by credential factories and referenced by alias names.
+Credentials keep secrets (usernames, passwords) out of Frank configurations and log files. They are managed by credential factories and referenced by alias names. For a complete list of all available credential providers and their configuration options, see the [FF! Reference for credential providers](https://reference.frankframework.org/#/credential-providers).
 
 ## Credential Factories
 
@@ -12,7 +12,7 @@ Credentials keep secrets (usernames, passwords) out of Frank configurations and
 
 ### PropertyFileCredentialFactory
 
-Set in environment properties:
+Set in environment properties. See the [PropertyFileCredentialFactory reference](https://reference.frankframework.org/#/credential-providers/PropertyFileCredentialFactory) for all configuration options:
 
 ```properties
 credentialFactory.class=org.frankframework.credentialprovider.PropertyFileCredentialFactory
@@ -32,11 +32,11 @@ Each alias is a named set of credentials. The alias name prefixes the `username`
 
 ### FileSystemCredentialFactory
 
-Stores each username and password in a dedicated file. Default file paths per alias: `<alias>/username` and `<alias>/password`, relative to `credentialFactory.filesystem.root`.
+Stores each username and password in a dedicated file. Default file paths per alias: `<alias>/username` and `<alias>/password`, relative to `credentialFactory.filesystem.root`. See the [FileSystemCredentialFactory reference](https://reference.frankframework.org/#/credential-providers/FileSystemCredentialFactory) for all configuration options.
 
 ### Ansible Vault
 
-Credentials are stored in an Ansible Vault encrypted file. The vault password is read from a separate file specified by `credentialFactory.keyFile`.
+Credentials are stored in an Ansible Vault encrypted file. The vault password is read from a separate file specified by `credentialFactory.keyFile`. See the [AnsibleVaultCredentialFactory reference](https://reference.frankframework.org/#/credential-providers/AnsibleVaultCredentialFactory) for all configuration options.
 
 ## Using Credentials in Configurations
 

docs/manual/operations/monitoring.md

@@ -53,7 +53,7 @@ The sender receives a message when the monitor is raised. This can trigger anoth
 
 Monitors defined in the UI must be exported and added to `Configuration.xml` to persist across restarts. Use the "XML" button in the UI to export.
 
-Full configuration example:
+Full configuration example (see the [FF! Reference](https://reference.frankframework.org/#/components) for pipe details):
 
 ```xml
 <Configuration