Make the guided installer route prominent in README and GitHub Pages - #9
Conversation
Both README.md and docs/index.html led with "clone the repo and ask Claude Code" as the first, primary route, with the guided installer mentioned second -- backwards from what v0.1.0-beta.4 actually offers most people. Reorder both so downloading Socials Studio is the primary route and the repository/clone route is clearly secondary, matching the button hierarchy and wording already approved on https://solvx.uk/socials-studio. README.md: - New "Download Socials Studio" section right after the intro, linking solvx.uk/socials-studio prominently plus direct v0.1.0-beta.4 asset links for Windows/macOS/Linux. - "Get started" reordered: guided installer first, "Already use Claude Code" second, with the literal clone/cd/claude three-line route. - Testing status corrected: the beta.3 Windows installer was actually human-tested successfully (existing Claude Code detection and launch confirmed) -- the freshly built beta.4 binary hasn't had its own separate hardware retest yet. Noted Linux's real-Chrome (not Chromium) requirement inline. - All beta.2/beta.3 version references updated to beta.4 where they describe the current download. docs/index.html: - Hero button row restructured: "Download for Windows" primary, macOS/ Linux downloads and a solvx.uk link secondary, GitHub-related buttons demoted further. - "Get started" section reordered to match (installer first, clone route second, with the same three-line code block), added an anchor id for the new "Install with Claude Code" button, and the same Windows/Linux testing-status and Chrome-requirement corrections as the README. - All beta.2 references (meta tags, JSON-LD, beta pill, section heading) updated to beta.4. No application code touched. All 107 tests still pass, compileall is clean, git diff --check is clean, and every download/release link in both files (including solvx.uk and all three beta.4 assets) returns HTTP 200.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 88cd225969
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Or grab **v0.1.0-beta.4** directly from GitHub Releases: | ||
|
|
||
| - **Windows (recommended):** [`Socials-Studio-Setup.exe`](https://github.com/tradewithmeai/socials-studio/releases/download/v0.1.0-beta.4/Socials-Studio-Setup.exe) |
There was a problem hiding this comment.
When a Windows user follows this new beta.4 link, the release workflow builds the executable by invoking iscc installer\windows\setup.iss, but that script still defines MyAppVersion as 0.1.0-beta.3 and uses it for AppVersion. The advertised beta.4 download will therefore install and register itself as beta.3, making version reporting and upgrade diagnosis misleading; update the installer metadata before presenting this as the beta.4 binary.
AGENTS.md reference: AGENTS.md:L27-L30
Useful? React with 👍 / 👎.
1 participant
Summary
Both
README.mdanddocs/index.html(the GitHub Pages site) led with "clone the repo and askClaude Code" as the first, primary route to get started, with the guided installer mentioned
second -- the opposite of what most people should reach for now that
v0.1.0-beta.4's guidedinstallers exist. This makes downloading Socials Studio the primary route in both places, matching
the wording and button hierarchy already approved on
solvx.uk/socials-studio.
No application code was touched -- documentation only.
What changed
README.md:solvx.uk/socials-studio prominently plus direct
v0.1.0-beta.4asset links for Windows/macOS/Linux.(secondary, technical route) -- including the literal
git clone/cd/claudethree-lineroute.
v0.1.0-beta.3Windows installer was actually human-testedsuccessfully (existing Claude Code detection and launch into Socials Studio confirmed) -- the
freshly built
v0.1.0-beta.4binary hasn't had its own separate hardware retest yet. NotedLinux's real-Chrome (not Chromium) requirement inline.
beta.2/beta.3version references updated tobeta.4where they describe the currentdownload (a
v0.1.0-beta.3mention describing the historical hardware test is deliberately keptas-is).
docs/index.html:solvx.uk link secondary, GitHub-related buttons demoted further -- same hierarchy as solvx.uk.
three-line code block), added an anchor
idfor the new "Install with Claude Code" button, andthe same Windows/Linux testing-status and Chrome-requirement corrections as the README.
beta.2references (meta tags, JSON-LD, beta pill, section heading) updated tobeta.4.Not touched
authcode, no other documentation files (installer/README.mddoesn't presentcloning as an install route and has no stale version references;
CONTRIBUTING.md's cloneinstructions are correctly contributor-only and out of scope).
Validation
pytest-- 107 passed (unchanged; no code touched)python -m compileall -q auth installer doctor.py tests-- cleangit diff --check-- cleansolvx.uk/socials-studioand all threev0.1.0-beta.4assets, verified live withcurl.#download-socials-studio,#get-started,#testing-status,#reporting-problems--requesting-features) all point at real headings/ids.