From 6ddfc2eedfe35358d9d476d3b21dfe5586fc9a27 Mon Sep 17 00:00:00 2001 From: Himanshu Dongre Date: Thu, 21 May 2026 01:43:52 +0530 Subject: [PATCH] Apply the same two-terminal split to the landing page install block MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The previous commit (Codex's README activation-path fix) split the README's step-1 code block to make it clear that `make dev-local` is a long-running foreground process that must stay in one terminal while `source backend/.venv/bin/activate` runs in another. The landing page at `website/index.html` had the same paste-and-get-stuck shape in its "Try it in 5 minutes" install block. Apply the parallel split with the exact same wording so the website and README give the same first-run guidance — install in one block, then "Start the backend in one terminal and keep it running", then "In a second terminal, activate the CLI before running smriti commands". Verified locally: page renders the split cleanly at 1280x800, no console errors. --- website/index.html | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/website/index.html b/website/index.html index 730b0eb..3e8339d 100644 --- a/website/index.html +++ b/website/index.html @@ -177,8 +177,11 @@ smriti metrics # project coordination KPIs

1. Install

git clone https://github.com/himanshudongre/smriti
 cd smriti
-make setup-local              # backend venv + CLI + frontend, no Docker
-make dev-local                # backend on http://localhost:8000
+make setup-local              # backend venv + CLI + frontend, no Docker
+

Start the backend in one terminal and keep it running:

+
make dev-local                # backend on http://localhost:8000
+

In a second terminal, activate the CLI before running smriti commands:

+
cd smriti
 source backend/.venv/bin/activate