From 07b81daec372ce8369c6e331e8ca25c4c551aa28 Mon Sep 17 00:00:00 2001 From: Stefano Mioli Date: Sun, 26 Apr 2026 18:20:58 +0200 Subject: [PATCH] docs: add author and project-page backlinks; point package.json homepage at the project page README gets a one-line citation block under the tagline pointing at projects.mioli.dev/cli-bridge (project page), blog.mioli.dev (write-ups), and mioli.dev (author landing). Same shape as the gosymdb sibling PR. package.json's `homepage` was previously circular (pointed back at this GitHub repo). Repointing to https://projects.mioli.dev/cli-bridge/ so that npmjs.com's package page links to the project landing page rather than back to the repo it was already on. The GitHub repo's About > Website field is also currently empty; setting it to the same URL once the project page is live would compound the SEO benefit. Not changed here, since that's a metadata setting outside the repo. Co-Authored-By: Claude Opus 4.7 (1M context) --- README.md | 2 ++ package.json | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 8a4a2ae..1a3a97b 100644 --- a/README.md +++ b/README.md @@ -8,6 +8,8 @@ **If you want agents to actually use your CLI, this is the missing piece.** +> Project page: · Blog: · Author: [Stefano Mioli](https://mioli.dev) + You wrote the CLI, you mentioned it in `CLAUDE.md`, the agent used it twice and then went back to `Bash`. cli-bridge solves that by registering your tool's commands as real MCP tools that live in the agent's tool registry — outside the context window, where they don't decay under conversation pressure. ## The problem diff --git a/package.json b/package.json index c519c08..b052e3d 100644 --- a/package.json +++ b/package.json @@ -48,7 +48,7 @@ "type": "git", "url": "git+https://github.com/walkindude/cli-bridge.git" }, - "homepage": "https://github.com/walkindude/cli-bridge", + "homepage": "https://projects.mioli.dev/cli-bridge/", "license": "Apache-2.0", "author": "Stefano Mioli", "keywords": [