From dedf7fa3a9635b030d8bdeb63497e114e518f83e Mon Sep 17 00:00:00 2001 From: shankar0123 Date: Sun, 5 Apr 2026 21:38:34 -0400 Subject: [PATCH] docs: add quick-start jump link near top of README MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Adds a one-line "Ready to try it?" link right after the maintainer callout, before the longer prose sections. Gives scanners an immediate exit to install instructions without rearranging the README's explain → show → install flow. Co-Authored-By: Claude Opus 4.6 --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 57cb844..c6ae453 100644 --- a/README.md +++ b/README.md @@ -38,6 +38,8 @@ gantt > **Actively maintained — shipping weekly.** Found something? [Open a GitHub issue](https://github.com/shankar0123/certctl/issues) — issues get triaged same-day. CI runs the full test suite with race detection, static analysis, and vulnerability scanning on every commit. +**Ready to try it?** Jump to the [Quick Start](#quick-start) — you'll have a running dashboard in under 5 minutes. + ## Why certctl Exists Certificate lifecycle tooling today falls into two camps: expensive enterprise platforms (Venafi, Keyfactor, Sectigo) that cost six figures and take months to deploy, or single-purpose tools (cert-manager, certbot) that handle one slice of the problem. If you run a mixed infrastructure — some NGINX, some Apache, a few HAProxy nodes, IIS on Windows, maybe an F5 — and you need to manage certificates from multiple CAs, there's nothing self-hosted that covers the full lifecycle without vendor lock-in.