Fixing links

Author: daviddenton

htmltest.yml

@@ -1,4 +1,8 @@
-IgnoreURLs: ["^.*js$", ".*.png$", ".*.svg$"]
 IgnoreAltMissing: true
 IgnoreAltEmpty: true
-IgnoreDirectoryMissingTrailingSlash: true
+IgnoreDirectoryMissingTrailingSlash: true
+IgnoreURLs:
+  - "favicon.svg"
+  - "^.*js$"
+  - ".*.png$"
+  - ".*.svg$"

src/website/content/ecosystem/connect.md

@@ -53,7 +53,7 @@ The main documentation has moved to the http4k Connect [site](https://connect.ht
 
 ## Supported APIs and Fakes:
 
-See the [Module Reference](https://connect.http4k.org/ecosystem/http4k/module/) for the complete list of supported services.
+See the [Module Reference](/ecosystem/http4k/module/) for the complete list of supported services.
 
 <div class="github">
 - [Example Template](./example) -> `"org.http4k:http4k-connect-example"` / `"org.http4k:http4k-connect-example-fake"`

src/website/content/ecosystem/http4k/concepts/http/index.md

@@ -15,7 +15,7 @@ In http4k, an HttpMessage is an immutable entity representing either a `Request`
 
 This immutability is a powerful alternative to the mutable versions found in other web libraries, as it provides a exact record of the state of the messages as they travel through an HTTP application, so for debugging purposes you can time-travel through an application inspecting the exact state at any point in the stack. 
 
-Data class semantics for comparison also make HttpMessages incredibly simple to assert against in testing scenarios, and this ease of testing is one of the most important parts of the [http4k ethos](/guide/concepts/rationale).
+Data class semantics for comparison also make HttpMessages incredibly simple to assert against in testing scenarios, and this ease of testing is one of the most important parts of the [http4k ethos](/rationale).
 
 ### HttpHandler
 

src/website/content/ecosystem/http4k/module/_index.md

@@ -1,105 +1,7 @@
 ---
----
 layout: module
 type: module
 ecosystem: http4k Core
 title: extension modules and integrations
 description: Details about the various http4k integration libraries
 ---
-
----
-
-# http4k Modules overview
-
-### Core functionality
-<a href="/ecosystem/http4k/module/core"><span class="pill">Core</span></a>
-<a href="/ecosystem/http4k/module/multipart"><span class="pill">Multipart Forms</span></a>
-<a href="/ecosystem/http4k/module/config"><span class="pill">Typesafe Configuration</span></a>
-
-### API styles
-<a href="/ecosystem/http4k/module/contracts"><span class="pill">OpenAPI Contracts</span></a>
-<a href="/ecosystem/http4k/module/graphql"><span class="pill">GraphQL</span></a>
-
-### HTTP Server Backends
-<a href="/ecosystem/http4k/module/servers"><span class="pill">Apache 4 & 5</span></a>
-<a href="/ecosystem/http4k/module/servers"><span class="pill">Java-WebSocket</span></a>
-<a href="/ecosystem/http4k/module/servers"><span class="pill">Jetty & JettyLoom</span></a>
-<a href="/ecosystem/http4k/module/servers"><span class="pill">Helidon (Loom)</span></a>
-<a href="/ecosystem/http4k/module/servers"><span class="pill">Ktor CIO & Netty</span></a>
-<a href="/ecosystem/http4k/module/servers"><span class="pill">Netty</span></a>
-<a href="/ecosystem/http4k/module/servers"><span class="pill">Ratpack</span></a>
-<a href="/ecosystem/http4k/module/servers"><span class="pill">SunHttp & SunHttpLoom</span></a>
-<a href="/ecosystem/http4k/module/servers"><span class="pill">Undertow</span></a>
-
-### HTTP Serverless Backends
-<a href="/ecosystem/http4k/module/serverless"><span class="pill">Alibaba Function Compute</span></a>
-<a href="/ecosystem/http4k/module/serverless"><span class="pill">Apache OpenWhisk</span></a>
-<a href="/ecosystem/http4k/module/serverless"><span class="pill">AWS Lambda</span></a>
-<a href="/ecosystem/http4k/module/serverless"><span class="pill">Azure Functions</span></a>
-<a href="/ecosystem/http4k/module/serverless"><span class="pill">Google Cloud Functions</span></a>
-<a href="/ecosystem/http4k/module/serverless"><span class="pill">Tencent Serverless Cloud Functions</span></a>
-
-### HTTP Clients
-<a href="/ecosystem/http4k/module/clients"><span class="pill">Apache4 Sync & Async</span></a>
-<a href="/ecosystem/http4k/module/clients"><span class="pill">Apache5 Sync & Async</span></a>
-<a href="/ecosystem/http4k/module/clients"><span class="pill">Java</span></a>
-<a href="/ecosystem/http4k/module/clients"><span class="pill">Fuel</span></a>
-<a href="/ecosystem/http4k/module/clients"><span class="pill">Helidon</span></a>
-<a href="/ecosystem/http4k/module/clients"><span class="pill">Jetty</span></a>
-<a href="/ecosystem/http4k/module/clients"><span class="pill">OkHttp</span></a>
-<a href="/ecosystem/http4k/module/clients"><span class="pill">Websocket</span></a>
-
-### Messaging formats
-<a href="/ecosystem/http4k/module/json"><span class="pill">Argo</span></a>
-<a href="/ecosystem/http4k/module/dataframe"><span class="pill">DataFrame</span></a>
-<a href="/ecosystem/http4k/module/json"><span class="pill">Gson</span></a>
-<a href="/ecosystem/http4k/module/xml"><span class="pill">Gson XML</span></a>
-<a href="/ecosystem/http4k/module/json"><span class="pill">Jackson</span></a>
-<a href="/ecosystem/http4k/module/xml"><span class="pill">Jackson XML</span></a>
-<a href="/ecosystem/http4k/module/yaml"><span class="pill">Jackson YAML</span></a>
-<a href="/ecosystem/http4k/module/jsonrpc"><span class="pill">JSON RPC</span></a>
-<a href="/ecosystem/http4k/module/json"><span class="pill">Klaxon</span></a>
-<a href="/ecosystem/http4k/module/json"><span class="pill">KondorJson</span></a>
-<a href="/ecosystem/http4k/module/json"><span class="pill">KotlinX Serialisation
-<a href="/ecosystem/http4k/module/json"><span class="pill">Moshi</span></a>
-
-### Templating libraries
-<a href="/ecosystem/http4k/module/templating"><span class="pill">Freemarker</span></a>
-<a href="/ecosystem/http4k/module/templating"><span class="pill">Handlebars</span></a>
-<a href="/ecosystem/http4k/module/templating"><span class="pill">Pug4j</span></a>
-<a href="/ecosystem/http4k/module/templating"><span class="pill">Rocker</span></a>
-<a href="/ecosystem/http4k/module/templating"><span class="pill">Pebble</span></a>
-<a href="/ecosystem/http4k/module/templating"><span class="pill">Thymeleaf</span></a>
-
-### SDK integrations
-<a href="/ecosystem/http4k/module/aws"><span class="pill">AWS</span></a>
-<a href="/ecosystem/http4k/module/azure"><span class="pill">Azure</span></a>
-
-### Security 
-<a href="/ecosystem/http4k/module/digest"><span class="pill">Digest Auth</span></a>
-<a href="/ecosystem/http4k/module/oauth"><span class="pill">OAuth</span></a>
-
-### Observability & Metrics
-<a href="/ecosystem/http4k/module/micrometer"><span class="pill">Micrometer</span></a>
-<a href="/ecosystem/http4k/module/opentelemetry"><span class="pill">OpenTelemetry</span></a>
-
-### Web Technologies
-<a href="/ecosystem/http4k/module/htmx"><span class="pill">htmx</span></a>
-
-### Cloud-Native/Misc
-<a href="/ecosystem/http4k/module/cloud_native"><span class="pill">Cloud Native extensions</span></a>
-<a href="/ecosystem/http4k/module/cloud_events"><span class="pill">Cloud Events</span></a>
-<a href="/ecosystem/http4k/module/resilience4j"><span class="pill">Resilience4J</span></a>
-<a href="/ecosystem/http4k/module/failsafe"><span class="pill">FailSafe</span></a>
-<a href="/ecosystem/http4k/module/webhooks"><span class="pill">Webhooks</span></a>
-
-### Testing
-<a href="/ecosystem/http4k/module/approvaltests"><span class="pill">Approval Testing</span></a>
-<a href="/ecosystem/http4k/module/chaos"><span class="pill">Chaos Testing</span></a>
-<a href="/ecosystem/http4k/module/hamkrest"><span class="pill">Hamkrest</span></a>
-<a href="/ecosystem/http4k/module/kotest"><span class="pill">Kotest</span></a>
-<a href="/ecosystem/http4k/module/playwright"><span class="pill">Playwright</span></a>
-<a href="/ecosystem/http4k/module/strikt"><span class="pill">Strikt</span></a>
-<a href="/ecosystem/http4k/module/servicevirtualisation"><span class="pill">Servirtium</span></a>
-<a href="/ecosystem/http4k/module/webdriver"><span class="pill">WebDriver</span></a>
-<a href="/ecosystem/http4k/module/tracerbullet"><span class="pill">Tracer Bullet</span></a>

src/website/content/ecosystem/http4k/module/graphql/index.md

@@ -23,7 +23,7 @@ dependencies {
 ### About
 This module provides http4k integration for the excellent [GraphQL-java](https://www.graphql-java.com/) library, allowing you to either serve or consume [GraphQL] services using a simple adapter API.
 
-As with the [ethos](/guide/concepts/rationale) of http4k, the uniform Server/Client GraphQLHandler model means that you can test applications entirely in-memory without binding to a port. Http4k also ships with a page serving the GraphQL playground which can be added as a simple route.
+As with the [ethos](/rationale) of http4k, the uniform Server/Client GraphQLHandler model means that you can test applications entirely in-memory without binding to a port. Http4k also ships with a page serving the GraphQL playground which can be added as a simple route.
 
 #### Code
 

src/website/content/howto/structure_your_logs_with_events/index.md

@@ -41,7 +41,7 @@ Attaching metadata to an `Event` results in (compactified) JSON similar to this:
 }
 ```
 
-In harmony with the [ethos](/guide/concepts/rationale) of **http4k** there is no need to bring in a custom logging library such as SL4J, although they would be very simple to integrate if required by implementing a custom `Events` instance.
+In harmony with the [ethos](/rationale) of **http4k** there is no need to bring in a custom logging library such as SL4J, although they would be very simple to integrate if required by implementing a custom `Events` instance.
 
 The example below shows a simple application that outputs structured logs to StdOut which can be analysed by an aggregator, along with the attachment of extra `Event` metadata via a custom `EventFilter`.
 

src/website/content/news/documenting_apis_with_openapi/index.md

@@ -18,7 +18,7 @@ There have been various efforts to standardise these aspects, and one of the mos
 ### Typesafe HTTP contracts with http4k-contract
 http4k has supported generating version 2 of **[OpenApi]** docs since all the way back in 2017 (v1.16) via it's `http4k-contract` module, and after a couple of releases ironing out the niggles (and some amazing help from the community), the team is now happy to announce OpenApi3 support with the release of http4k version 3.179.0.
 
-In line with the overall **[ethos of the project](/guide/concepts/rationale)**, http4k OpenApi support is done entirely through code and in a typesafe and refactorable way. This is somewhat of a departure from how most other libraries have implemented OpenApi (where often annotations and other compile-time magic are used) and means that in http4k the spec defined in code is the same one that is used to generate the API documentation and the same one used to validate incoming HTTP messages, meaning that it can never go stale. This focus on runtime code also allows for dynamic behaviours which would be very difficult to replicate at compile-time.
+In line with the overall **[ethos of the project](/rationale)**, http4k OpenApi support is done entirely through code and in a typesafe and refactorable way. This is somewhat of a departure from how most other libraries have implemented OpenApi (where often annotations and other compile-time magic are used) and means that in http4k the spec defined in code is the same one that is used to generate the API documentation and the same one used to validate incoming HTTP messages, meaning that it can never go stale. This focus on runtime code also allows for dynamic behaviours which would be very difficult to replicate at compile-time.
 
 Out of the box, `http4k-contract` the module now provides the following features when configured for OpenApi3:
 
@@ -105,4 +105,4 @@ The full source for this tutorial can be found **[here](https://github.com/http4
 [AWS API Gateway]: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-swagger-extensions.html
 [Google Cloud Endpoints]: https://cloud.google.com/endpoints/docs/openapi/
 [http4k-by-example]: https://github.com/http4k/http4k-by-example
-[http4k Lens API]:  https://www.http4k.org/ecosystem/http4k/module/core/#typesafe-parameter-destructuringconstruction-of-http-messages-with-lenses
+[http4k Lens API]:  /ecosystem/http4k/module/core/#typesafe-parameter-destructuringconstruction-of-http-messages-with-lenses

src/website/content/news/http4k_v4/index.md

@@ -99,7 +99,7 @@ Not wanting our users to miss out on anything, we've added support for simply in
 The [OpenTelemetry](https://opentelemetry.io/) project describes itself as...
 > **"... a collection of tools, APIs, and SDKs. You use it to instrument, generate, collect, and export telemetry data (metrics, logs, and traces) for analysis in order to understand your software's performance and behavior." - OpenTelemetry.io**
 
-It's a great project run by the CNCF and very well fits in with the [ethos](/guide/concepts/rationale) that the http4k team believes in. As with all http4k integration modules, we want to enable http4k developers to be able to plug in their apps as simply as possible - in this case, just configure the OpenTelemetry API or Java-agent, then just add some simple `Filters` to your code to start collecting Distributed Traces or Metrics. Several tracing schemes are supported, including Amazon XRay, Jaeger and Zipkin.
+It's a great project run by the CNCF and very well fits in with the [ethos](/rationale) that the http4k team believes in. As with all http4k integration modules, we want to enable http4k developers to be able to plug in their apps as simply as possible - in this case, just configure the OpenTelemetry API or Java-agent, then just add some simple `Filters` to your code to start collecting Distributed Traces or Metrics. Several tracing schemes are supported, including Amazon XRay, Jaeger and Zipkin.
 
 For more docs on how to get it all working, head over to the [docs](/ecosystem/http4k/module/opentelemetry).
 

src/website/content/performance.md

@@ -24,7 +24,7 @@ Command-line JVM options, however, were tuned for the test to take advantage of
 The full implementation of the benchmark can be found [here](https://github.com/TechEmpower/FrameworkBenchmarks/tree/master/frameworks/Kotlin/http4k).
 
 ### Results - Round 22
-Overall, http4k continues to do well in this round of benchmarking, placing 48/159 - especially considering that the [ethos](/guide/concepts/rationale) of the library is one of excellent Developer experience over and above high-end performance (which tends to result in less friendly APIs).
+Overall, http4k continues to do well in this round of benchmarking, placing 48/159 - especially considering that the [ethos](/rationale) of the library is one of excellent Developer experience over and above high-end performance (which tends to result in less friendly APIs).
 
 Rankings below are filtered for JVM libraries:
 

src/website/layouts/partials/shared/ecosystem-sidebar.html

@@ -21,7 +21,7 @@ <h4>Concepts</h4>
             <li>
                 <h4>Project</h4>
                 <ul class="list-unstyled ms-3">
-                    <li><a href="/ecosystem/{{ $data.ref }}/changelog">Changelog</a></li>
+                    <li><a href="/ecosystem/{{ $data.ref }}/changelog/">Changelog</a></li>
                     <li><a href="{{ $data.github }}">GitHub</a></li>
                     <li><a href="{{ $data.github }}/issues">Issue Tracker</a></li>
                 </ul>

testLinks.sh

@@ -1,5 +1,5 @@
 
 cd src/website/public
-cp -R ../../../htmltest.yml .
-docker run -v $(pwd):/test --rm wjdp/htmltest . -l 1 -s
+cp ../../../htmltest.yml $(pwd)
+docker run -v $(pwd):/test --rm wjdp/htmltest . -l 3 | grep -v svg | grep -v js | grep -v png
 cd -