diff --git a/src/docs/markdown/caddyfile/directives.md b/src/docs/markdown/caddyfile/directives.md
index 585e6d8..56c6af7 100644
--- a/src/docs/markdown/caddyfile/directives.md
+++ b/src/docs/markdown/caddyfile/directives.md
@@ -8,6 +8,7 @@ The following directives come standard with Caddy, and can be used in the HTTP C
 
 Directive | Description
 ----------|------------
+**[acme_server](/docs/caddyfile/directives/acme_server)** | An embedded ACME server
 **[basicauth](/docs/caddyfile/directives/basicauth)** | Enforces HTTP Basic Authentication
 **[bind](/docs/caddyfile/directives/bind)** | Customize the server's socket address
 **[encode](/docs/caddyfile/directives/encode)** | Encodes (usually compresses) responses
diff --git a/src/docs/markdown/caddyfile/directives/acme_server.md b/src/docs/markdown/caddyfile/directives/acme_server.md
new file mode 100644
index 0000000..7e5aaf1
--- /dev/null
+++ b/src/docs/markdown/caddyfile/directives/acme_server.md
@@ -0,0 +1,21 @@
+---
+title: acme_server (Caddyfile directive)
+---
+
+# acme_server
+
+An embedded [ACME protocol](https://tools.ietf.org/html/rfc8555) server handler. This allows a Caddy instance to issue certificates for any other ACME-compatible software (including other Caddy instances).
+
+When enabled, requests matching the path `/acme/*` will be handled by the ACME server.
+
+
+## Client configuration
+
+Using ACME server defaults, ACME clients should simply be configured to use `https://localhost/acme/directory` as their ACME endpoint.
+
+
+## Syntax
+
+```caddy-d
+acme_server [<matcher>]
+```