diff --git a/docs/configuration.md b/docs/configuration.md
index fb3de48e2..caeabaf0c 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -1,13 +1,8 @@
-
+---
+title: "Configuring a registry"
+description: "Explains how to configure a registry"
+keywords: ["registry, on-prem, images, tags, repository, distribution, configuration"]
+---
# Registry Configuration Reference
diff --git a/docs/spec/api.md b/docs/spec/api.md
index c4517c0b4..2f8e7a899 100644
--- a/docs/spec/api.md
+++ b/docs/spec/api.md
@@ -1,12 +1,8 @@
-
+---
+title: "HTTP API V2"
+description: "Specification for the Registry API."
+keywords: ["registry, on-prem, images, tags, repository, distribution, api, advanced"]
+---
# Docker Registry HTTP API V2
diff --git a/docs/spec/api.md.tmpl b/docs/spec/api.md.tmpl
index eeafec1ea..e13d1513b 100644
--- a/docs/spec/api.md.tmpl
+++ b/docs/spec/api.md.tmpl
@@ -1,12 +1,8 @@
-
+---
+title: "HTTP API V2"
+description: "Specification for the Registry API."
+keywords: ["registry, on-prem, images, tags, repository, distribution, api, advanced"]
+---
# Docker Registry HTTP API V2
diff --git a/docs/spec/auth/index.md b/docs/spec/auth/index.md
index f6ee8e1fa..d1aa94225 100644
--- a/docs/spec/auth/index.md
+++ b/docs/spec/auth/index.md
@@ -1,13 +1,8 @@
-
+---
+title: "Docker Registry Token Authentication"
+description: "Docker Registry v2 authentication schema"
+keywords: ["registry, on-prem, images, tags, repository, distribution, authentication, advanced"]
+---
# Docker Registry v2 authentication
diff --git a/docs/spec/auth/jwt.md b/docs/spec/auth/jwt.md
index c90bd6e86..aa9941b0b 100644
--- a/docs/spec/auth/jwt.md
+++ b/docs/spec/auth/jwt.md
@@ -1,13 +1,8 @@
-
+---
+title: "Token Authentication Implementation"
+description: "Describe the reference implementation of the Docker Registry v2 authentication schema"
+keywords: ["registry, on-prem, images, tags, repository, distribution, JWT authentication, advanced"]
+---
# Docker Registry v2 Bearer token specification
diff --git a/docs/spec/auth/oauth.md b/docs/spec/auth/oauth.md
index 0f8d35dbb..d946da8a2 100644
--- a/docs/spec/auth/oauth.md
+++ b/docs/spec/auth/oauth.md
@@ -1,13 +1,8 @@
-
+---
+title: "Oauth2 Token Authentication"
+description: "Specifies the Docker Registry v2 authentication"
+keywords: ["registry, on-prem, images, tags, repository, distribution, oauth2, advanced"]
+---
# Docker Registry v2 authentication using OAuth2
@@ -193,4 +188,3 @@ Content-Type: application/json
{"refresh_token":"kas9Da81Dfa8","access_token":"eyJhbGciOiJFUzI1NiIsInR5":"expires_in":900,"scope":"repository:samalba/my-app:pull,repository:samalba/my-app:push"}
```
-
diff --git a/docs/spec/auth/scope.md b/docs/spec/auth/scope.md
index a8f6c0628..eecb8f6f1 100644
--- a/docs/spec/auth/scope.md
+++ b/docs/spec/auth/scope.md
@@ -1,13 +1,8 @@
-
+---
+title: "Token Scope Documentation"
+description: "Describes the scope and access fields used for registry authorization tokens"
+keywords: ["registry, on-prem, images, tags, repository, distribution, advanced, access, scope"]
+---
# Docker Registry Token Scope and Access
@@ -140,4 +135,3 @@ done by fetching an access token using the refresh token. Since the refresh
token is not scoped to specific resources for an audience, extra care should
be taken to only use the refresh token to negotiate new access tokens directly
with the authorization server, and never with a resource provider.
-
diff --git a/docs/spec/auth/token.md b/docs/spec/auth/token.md
index 81af53b2e..f8391bd5a 100644
--- a/docs/spec/auth/token.md
+++ b/docs/spec/auth/token.md
@@ -1,13 +1,8 @@
-
+---
+title: "Token Authentication Specification"
+description: "Specifies the Docker Registry v2 authentication"
+keywords: ["registry, on-prem, images, tags, repository, distribution, Bearer authentication, advanced"]
+---
# Docker Registry v2 authentication via central service
@@ -25,7 +20,7 @@ This document outlines the v2 Docker registry authentication scheme:
5. The client retries the original request with the Bearer token embedded in
the request's Authorization header.
6. The Registry authorizes the client by validating the Bearer token and the
- claim set embedded within it and begins the push/pull session as usual.
+ claim set embedded within it and begins the push/pull session as usual.
## Requirements
@@ -161,7 +156,7 @@ Defines getting a bearer and refresh token using the token endpoint.
expires_in