fix: Update remaining legacy links and home page theming

docs/examples/git-triggered.md

@@ -27,7 +27,7 @@ The [`git` resource](https://github.com/concourse/git-resource) can be used to t
 
 ## References
 
-* [Resources](https://concourse-ci.org/resources.html)
-* [Jobs](https://concourse-ci.org/jobs.html)
-* [Steps](https://concourse-ci.org/steps.html)
-* [Tasks](https://concourse-ci.org/tasks.html)
+* [Resources](../docs/resources/index.md)
+* [Jobs](../docs/jobs.md)
+* [Steps](../docs/steps/index.md)
+* [Tasks](../docs/tasks.md)

docs/examples/golang-lib.md

@@ -16,14 +16,13 @@ You can run the tests for a Golang library across any specified versions.
 </div>
 
 This example shows how to have multiple versions of a language, environment, or dependency fetched and integrated in to
-a [Pipeline](https://concourse-ci.org/pipelines.html).
+a [Pipeline](../docs/pipelines/index.md).
 
-For these Docker images, defining them as [Resources](https://concourse-ci.org/resources.html) has two advantages for
+For these Docker images, defining them as [Resources](../docs/resources/index.md) has two advantages for
 this use case. First, this enables the pipeline to be triggered when there are new versions of those images available.
-Second, referencing them in the task's [`task` step **`image`
-**](https://concourse-ci.org/task-step.html#schema.task.image) param is helpful as it will ensure consistency between
-the image versions fetched by the [Resource](https://concourse-ci.org/resources.html) and the image version running in
-the job.
+Second, referencing them in the task's [`task` step **`image`**](../docs/steps/task.md) param is helpful as it will 
+ensure consistency between the image versions fetched by the [Resource](../docs/resources/index.md) and the image 
+version running in the job.
 
 ## Pipeline Configuration
 
@@ -33,6 +32,6 @@ the job.
 
 ## References
 
-* [Jobs](https://concourse-ci.org/jobs.html)
-* [Steps](https://concourse-ci.org/steps.html)
-* [Tasks](https://concourse-ci.org/tasks.html)
+* [Jobs](../docs/jobs.md)
+* [Steps](../docs/steps/index.md)
+* [Tasks](../docs/tasks.md)

docs/examples/hello-world.md

@@ -17,7 +17,7 @@ A single job is the simplest form of pipeline.
 
 While this is less of an example pipeline, this is a simple introduction to a critical primitive to form pipelines.
 
-Also, due to the fact that there are minimal external factors ([Resources](https://concourse-ci.org/resources.html)) for
+Also, due to the fact that there are minimal external factors ([Resources](../docs/resources/index.md)) for
 the system to check and resolve, this is often used to test overall system health.
 
 ## Pipeline Configuration
@@ -28,6 +28,6 @@ the system to check and resolve, this is often used to test overall system healt
 
 ## References
 
-* [Jobs](https://concourse-ci.org/jobs.html)
-* [Steps](https://concourse-ci.org/steps.html)
-* [Tasks](https://concourse-ci.org/tasks.html)
+* [Jobs](../docs/jobs.md)
+* [Steps](../docs/steps/index.md)
+* [Tasks](../docs/tasks.md)

docs/examples/index.md

@@ -6,11 +6,11 @@ hide:
   - toc
 ---
 
-Setting up self-contained Concourse [pipelines](https://concourse-ci.org/pipelines.html) is an excellent way to
+Setting up self-contained Concourse [pipelines](../docs/pipelines/index.md) is an excellent way to
 experiment before exploring the more comprehensive documentation.
 
 Each example presents a pipeline YAML snippet which can be copied to a local file and deployed to your instance via [
-`fly set-pipeline`](https://concourse-ci.org/setting-pipelines.html#fly-set-pipeline). From there you can experiment and
+`fly set-pipeline`](../docs/pipelines/setting-pipelines.md#fly-set-pipeline). From there you can experiment and
 modify parts of the configuration to better understand how everything works. All configuration options are detailed in
 the [Docs](../docs/index.md).
 

docs/examples/inputs-outputs.md

@@ -22,8 +22,8 @@ While you are free to create as many jobs as you'd like for your pipeline, you h
 inbetween them.
 
 These constructs give you the ability to design a pipeline that can process artifacts in many different ways
-via [Tasks](https://concourse-ci.org/tasks.html), and then store those processed artifacts externally
-via [Resources](https://concourse-ci.org/resources.html).
+via [Tasks](../docs/tasks.md), and then store those processed artifacts externally
+via [Resources](../docs/resources/index.md).
 
 ## Pipeline Configuration
 
@@ -33,7 +33,7 @@ via [Resources](https://concourse-ci.org/resources.html).
 
 ## References
 
-* [`task-config.outputs`](https://concourse-ci.org/tasks.html#schema.task-config.outputs)
-* [Jobs](https://concourse-ci.org/jobs.html)
-* [Steps](https://concourse-ci.org/steps.html)
-* [Tasks](https://concourse-ci.org/tasks.html)
+* [`task-config.outputs`](../docs/tasks.md#output)
+* [Jobs](../docs/jobs.md)
+* [Steps](../docs/steps/index.md)
+* [Tasks](../docs/tasks.md)

docs/examples/java-app.md

@@ -23,6 +23,6 @@ You can run the tests for a Java application.
 
 ## References
 
-* [Jobs](https://concourse-ci.org/jobs.html)
-* [Steps](https://concourse-ci.org/steps.html)
-* [Tasks](https://concourse-ci.org/tasks.html)
+* [Jobs](../docs/jobs.md)
+* [Steps](../docs/steps/index.md)
+* [Tasks](../docs/tasks.md)

docs/examples/job-and-task-hooks.md

@@ -6,8 +6,8 @@ hide:
   - toc
 ---
 
-Job hooks like [`job.on_success`](https://concourse-ci.org/jobs.html#schema.job.on_success) and Step hooks like [
-`on_success`](https://concourse-ci.org/on-success-step.html#schema.on_success) are available to perform actions based on
+Job hooks like [`job.on_success`](../docs/jobs.md#job-schema) and Step hooks like [
+`on_success`](../docs/steps/modifier-and-hooks/on-success.md) are available to perform actions based on
 the success, failure, or abortion of a job.
 
 <div>
@@ -25,12 +25,12 @@ the success, failure, or abortion of a job.
 
 ## References
 
-* [`job.on_success`](https://concourse-ci.org/jobs.html#schema.job.on_success)
-* [`job.on_failure`](https://concourse-ci.org/jobs.html#schema.job.on_failure)
-* [`job.on_abort`](https://concourse-ci.org/jobs.html#schema.job.on_abort)
-* [`on_success`](https://concourse-ci.org/on-success-step.html#schema.on_success)
-* [`on_failure`](https://concourse-ci.org/on-failure-hook.html#schema.on_failure)
-* [`on_abort`](https://concourse-ci.org/on-abort-hook.html#schema.on_abort)
-* [Jobs](https://concourse-ci.org/jobs.html)
-* [Steps](https://concourse-ci.org/steps.html)
-* [Tasks](https://concourse-ci.org/tasks.html)
+* [`job.on_success`](../docs/jobs.md#job-schema)
+* [`job.on_failure`](../docs/jobs.md#job-schema)
+* [`job.on_abort`](../docs/jobs.md#job-schema)
+* [`on_success`](../docs/steps/modifier-and-hooks/on-success.md)
+* [`on_failure`](../docs/steps/modifier-and-hooks/on-failure.md)
+* [`on_abort`](../docs/steps/modifier-and-hooks/on-abort.md)
+* [Jobs](../docs/jobs.md)
+* [Steps](../docs/steps/index.md)
+* [Tasks](../docs/tasks.md)

docs/examples/manually-triggered.md

@@ -23,7 +23,7 @@ A job can be triggered by a resource. After it's complete, the next job can run
 
 ## References
 
-* [Resources](https://concourse-ci.org/resources.html)
-* [Jobs](https://concourse-ci.org/jobs.html)
-* [Steps](https://concourse-ci.org/steps.html)
-* [Tasks](https://concourse-ci.org/tasks.html)
+* [Resources](../docs/resources/index.md)
+* [Jobs](../docs/jobs.md)
+* [Steps](../docs/steps/index.md)
+* [Tasks](../docs/tasks.md)

docs/examples/nodejs-app.md

@@ -23,6 +23,6 @@ You can run the tests for a Nodejs application.
 
 ## References
 
-* [Jobs](https://concourse-ci.org/jobs.html)
-* [Steps](https://concourse-ci.org/steps.html)
-* [Tasks](https://concourse-ci.org/tasks.html)
+* [Jobs](../docs/jobs.md)
+* [Steps](../docs/steps/index.md)
+* [Tasks](../docs/tasks.md)

docs/examples/php-app.md

@@ -23,6 +23,6 @@ You can run the tests for a PHP application.
 
 ## References
 
-* [Jobs](https://concourse-ci.org/jobs.html)
-* [Steps](https://concourse-ci.org/steps.html)
-* [Tasks](https://concourse-ci.org/tasks.html)
+* [Jobs](../docs/jobs.md)
+* [Steps](../docs/steps/index.md)
+* [Tasks](../docs/tasks.md)

docs/examples/pipeline-vars.md

@@ -31,6 +31,6 @@ You can use params in a pipelines configuration file.
 
 ## References
 
-* [Jobs](https://concourse-ci.org/jobs.html)
-* [Steps](https://concourse-ci.org/steps.html)
-* [Tasks](https://concourse-ci.org/tasks.html)
+* [Jobs](../docs/jobs.md)
+* [Steps](../docs/steps/index.md)
+* [Tasks](../docs/tasks.md)

docs/examples/rails-app.md

@@ -23,6 +23,6 @@ You can run the tests for a Rails that requires a specific version of ruby and r
 
 ## References
 
-* [Jobs](https://concourse-ci.org/jobs.html)
-* [Steps](https://concourse-ci.org/steps.html)
-* [Tasks](https://concourse-ci.org/tasks.html)
+* [Jobs](../docs/jobs.md)
+* [Steps](../docs/steps/index.md)
+* [Tasks](../docs/tasks.md)

docs/examples/serial-job.md

@@ -6,7 +6,7 @@ hide:
   - toc
 ---
 
-Setting the [`job.serial`](https://concourse-ci.org/jobs.html#schema.job.serial) flag restricts a job to run one build
+Setting the [`job.serial`](../docs/jobs.md#job-schema) flag restricts a job to run one build
 at a time.
 
 <div>
@@ -19,7 +19,7 @@ at a time.
 By default, jobs are run in parallel. For some use cases this might be ideal (ex. testing all incoming commits from a
 repository). For other use cases this might be less ideal (ex. deploying an application).
 
-You can also set the [`job.max_in_flight`](https://concourse-ci.org/jobs.html#schema.job.max_in_flight) value to 1 to
+You can also set the [`job.max_in_flight`](../docs/jobs.md#job-schema) value to 1 to
 disable parallel job runs.
 
 ## Pipeline Configuration
@@ -30,6 +30,6 @@ disable parallel job runs.
 
 ## References
 
-* [Jobs](https://concourse-ci.org/jobs.html)
-* [Steps](https://concourse-ci.org/steps.html)
-* [Tasks](https://concourse-ci.org/tasks.html)
+* [Jobs](../docs/jobs.md)
+* [Steps](../docs/steps/index.md)
+* [Tasks](../docs/tasks.md)

docs/examples/set-pipeline.md

@@ -23,6 +23,6 @@ You can set a static set of pipelines from another pipeline on the same team.
 
 ## References
 
-* [Jobs](https://concourse-ci.org/jobs.html)
-* [Steps](https://concourse-ci.org/steps.html)
-* [`set-pipeline` step](https://concourse-ci.org/set-pipeline-step.html)
+* [Jobs](../docs/jobs.md)
+* [Steps](../docs/steps/index.md)
+* [`set-pipeline` step](../docs/steps/set-pipeline.md)

docs/examples/time-triggered.md

@@ -25,7 +25,7 @@ The [`time` resource](https://github.com/concourse/time-resource) can be used to
 
 ## References
 
-* [Resources](https://concourse-ci.org/resources.html)
-* [Jobs](https://concourse-ci.org/jobs.html)
-* [Steps](https://concourse-ci.org/steps.html)
-* [Tasks](https://concourse-ci.org/tasks.html)
+* [Resources](../docs/resources/index.md)
+* [Jobs](../docs/jobs.md)
+* [Steps](../docs/steps/index.md)
+* [Tasks](../docs/tasks.md)

overrides/assets/stylesheets/home.css

@@ -19,7 +19,7 @@ body {
 }
 
 .feature-box {
-  background-color: white;
+  background-color: var(--md-default-bg-color);
   border-radius: 8px;
   box-shadow: 0 4px 16px rgba(0, 0, 0, 0.2);
   padding: 2em;
@@ -30,13 +30,11 @@ body {
 .feature-box h2 {
   margin-top: 0em;
   margin-bottom: 0.5em;
-  color: #333;
   font-size: 1.5rem;
   font-weight: bold;
 }
 
 .feature-box h3 {
-  color: #333;
   font-size: 1.25rem;
   font-weight: bold;
   margin-top: 1.5em;
@@ -45,7 +43,6 @@ body {
 
 .feature-box p {
   flex: 1;
-  color: #333;
   margin-top: 0em;
   margin-bottom: 1em;
 }
@@ -66,7 +63,6 @@ body {
 
 .feature-content .feature-description {
   flex: 1;
-  color: #333;
   margin-top: 1em;
   margin-bottom: 1em;
 }
@@ -90,7 +86,6 @@ body {
 }
 
 .feature-column h3 {
-  color: #333;
   font-size: 1.25rem;
   font-weight: bold;
   margin-top: 0;
@@ -128,10 +123,6 @@ body {
   min-height: 249px;
 }
 
-.feature-text {
-  color: #333;
-}
-
 .feature-text p {
   margin: 0 0 1em 0;
   line-height: 1.6;