docs: add navigation back-links to all leaf pages (#1701)

kmcginnes · web-flow · commit e6fe10870662 · 2026-04-22T17:45:38.000-05:00
diff --git a/docs/guides/connecting-to-blazegraph.md b/docs/guides/connecting-to-blazegraph.md
@@ -1,3 +1,5 @@
+[← Guides](./)
+
 # Connecting to BlazeGraph
 
 - Build and run the Docker container as normal and connect Graph Explorer to BlazeGraph through the proxy server.
diff --git a/docs/guides/connecting-to-gremlin-server.md b/docs/guides/connecting-to-gremlin-server.md
@@ -1,3 +1,5 @@
+[← Guides](./)
+
 # Connecting to Gremlin-Server
 
 If you are using the default Gremlin Server docker image, you can get the server running with the following commands:
diff --git a/docs/guides/connecting-to-neptune.md b/docs/guides/connecting-to-neptune.md
@@ -1,3 +1,5 @@
+[← Guides](./)
+
 # Connecting to Neptune
 
 - Ensure that Graph Explorer has access to the Neptune instance by being in the same VPC or VPC peering.
diff --git a/docs/guides/deploy-to-ec2.md b/docs/guides/deploy-to-ec2.md
@@ -1,3 +1,5 @@
+[← Guides](./)
+
 # Deploy to Amazon EC2
 
 Deploy Graph Explorer onto an Amazon EC2 instance and use it as a proxy server with SSH tunneling to connect to Amazon Neptune.
diff --git a/docs/guides/deploy-to-ecs-fargate.md b/docs/guides/deploy-to-ecs-fargate.md
@@ -1,3 +1,5 @@
+[← Guides](./)
+
 # Running Graph Explorer on AWS Fargate + Amazon ECS
 
 The following steps will allow you set up Graph Explorer on AWS Fargate in Amazon ECS, and connect to a running Neptune database.
diff --git a/docs/guides/deploy-to-sagemaker.md b/docs/guides/deploy-to-sagemaker.md
@@ -1,3 +1,5 @@
+[← Guides](./)
+
 # Launching Graph Explorer using Amazon SageMaker
 
 Graph Explorer can be hosted and launched on Amazon SageMaker Notebooks via a lifecycle configuration script. To learn more about lifecycle configurations and how to create one, see the [documentation](https://docs.aws.amazon.com/sagemaker/latest/dg/notebook-lifecycle-config.html).
diff --git a/docs/guides/troubleshooting.md b/docs/guides/troubleshooting.md
@@ -1,3 +1,5 @@
+[← Guides](./)
+
 # Troubleshooting
 
 This page contains workarounds for common issues and information on how to diagnose other issues.
diff --git a/docs/references/default-connection.md b/docs/references/default-connection.md
@@ -1,3 +1,5 @@
+[← References](./)
+
 # Providing a Default Connection
 
 To provide a default connection such that initial loads of Graph Explorer always result with the same starting connection, modify the `docker run ...` command to either take in a JSON configuration or runtime environment variables. If you provide both a JSON configuration and environmental variables, the JSON will be prioritized.
diff --git a/docs/references/health-check.md b/docs/references/health-check.md
@@ -1,3 +1,5 @@
+[← References](./)
+
 # Health Check Status
 
 The `graph-explorer-proxy-server` provides a `/status` endpoint for monitoring its health and readiness. This endpoint is crucial for ensuring reliable service operation and can be utilized in various deployment scenarios.
diff --git a/docs/references/logging.md b/docs/references/logging.md
@@ -1,3 +1,5 @@
+[← References](./)
+
 # Logging
 
 Logs are, by default, sent to the console and will be visible as output to the docker logs. If you want to access the full set of logs, you can run `docker logs {container name or id}`.
diff --git a/docs/references/minimum-requirements.md b/docs/references/minimum-requirements.md
@@ -1,3 +1,5 @@
+[← References](./)
+
 # Minimum Requirements
 
 Graph Explorer does not block any particular versions of graph databases, but the queries used may or may not succeed based on the version of the query engine.
diff --git a/docs/references/security.md b/docs/references/security.md
@@ -1,3 +1,5 @@
+[← References](./)
+
 # Security
 
 You can use Graph Explorer to connect to a publicly accessible graph database endpoint, or connect to a proxy endpoint that redirects to a private graph database endpoint.

Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,5 @@`
	`1`	`+[← Guides](./)`
	`2`	`+`
`1`	`3`	`# Connecting to BlazeGraph`
`2`	`4`
`3`	`5`	`- Build and run the Docker container as normal and connect Graph Explorer to BlazeGraph through the proxy server.`
Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,5 @@`
	`1`	`+[← Guides](./)`
	`2`	`+`
`1`	`3`	`# Connecting to Gremlin-Server`
`2`	`4`
`3`	`5`	`If you are using the default Gremlin Server docker image, you can get the server running with the following commands:`
Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,5 @@`
	`1`	`+[← Guides](./)`
	`2`	`+`
`1`	`3`	`# Connecting to Neptune`
`2`	`4`
`3`	`5`	`- Ensure that Graph Explorer has access to the Neptune instance by being in the same VPC or VPC peering.`
Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,5 @@`
	`1`	`+[← Guides](./)`
	`2`	`+`
`1`	`3`	`# Deploy to Amazon EC2`
`2`	`4`
`3`	`5`	`Deploy Graph Explorer onto an Amazon EC2 instance and use it as a proxy server with SSH tunneling to connect to Amazon Neptune.`
Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,5 @@`
	`1`	`+[← Guides](./)`
	`2`	`+`
`1`	`3`	`# Running Graph Explorer on AWS Fargate + Amazon ECS`
`2`	`4`
`3`	`5`	`The following steps will allow you set up Graph Explorer on AWS Fargate in Amazon ECS, and connect to a running Neptune database.`
Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,5 @@`
	`1`	`+[← Guides](./)`
	`2`	`+`
`1`	`3`	`# Launching Graph Explorer using Amazon SageMaker`
`2`	`4`
`3`	`5`	`Graph Explorer can be hosted and launched on Amazon SageMaker Notebooks via a lifecycle configuration script. To learn more about lifecycle configurations and how to create one, see the [documentation](https://docs.aws.amazon.com/sagemaker/latest/dg/notebook-lifecycle-config.html).`
Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,5 @@`
	`1`	`+[← Guides](./)`
	`2`	`+`
`1`	`3`	`# Troubleshooting`
`2`	`4`
`3`	`5`	`This page contains workarounds for common issues and information on how to diagnose other issues.`
Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,5 @@`
	`1`	`+[← References](./)`
	`2`	`+`
`1`	`3`	`# Providing a Default Connection`
`2`	`4`
`3`	`5`	To provide a default connection such that initial loads of Graph Explorer always result with the same starting connection, modify the `docker run ...` command to either take in a JSON configuration or runtime environment variables. If you provide both a JSON configuration and environmental variables, the JSON will be prioritized.
Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,5 @@`
	`1`	`+[← References](./)`
	`2`	`+`
`1`	`3`	`# Health Check Status`
`2`	`4`
`3`	`5`	The `graph-explorer-proxy-server` provides a `/status` endpoint for monitoring its health and readiness. This endpoint is crucial for ensuring reliable service operation and can be utilized in various deployment scenarios.
Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,5 @@`
	`1`	`+[← References](./)`
	`2`	`+`
`1`	`3`	`# Logging`
`2`	`4`
`3`	`5`	Logs are, by default, sent to the console and will be visible as output to the docker logs. If you want to access the full set of logs, you can run `docker logs {container name or id}`.