Fix Try page accuracy and shorten the path to the trial - #19
Conversation
The Try page advertised requirements that no longer exist. It asked for an OpenAI or Claude API token in five places and told visitors to sign in with GitHub to activate the AI module. Neither has been true since jelastic-jps/constructor-fabric#8: the coding agent is chosen at sign-up and authenticated with the visitor's own Claude, ChatGPT or GitHub account inside the IDE, and no API key is requested at any point. A visitor without a token had no reason to read further. The copy is now accurate throughout. The prerequisites are an account with your coding agent and a password you choose; the trainer is described as the twelve steps it actually has; the three metadata descriptions match the page. The trial form also moved. It sat in a side column below the hero, so the single action the page exists for was not visible on arrival. The form now sits directly under the hero lead, and a full-width "Deploy your environment" section repeats it after "What you get" for readers who scroll. On success the button settles on "Email sent" instead of reverting to its initial label, so an accepted request reads as accepted. Supporting changes: the hero screenshot is replaced, as the old one showed the retired eight-step trainer under its former .cf-constructor naming; the home page hero leads with "Try now" rather than GitHub; and Try moves to second position in the main navigation, next to Home. Done with the help of: Claude Opus 5 Signed-off-by: sstimsu <timsus@gmail.com>
|
Important Review available on request
Reviews should be triggered manually for repositories with fewer than 10 stars. Select Trigger review above or comment ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Preview deployment is ready: https://constructorfabric.github.io/website-previews/pr-19/ This preview is built from the latest commit on this PR. It is regenerated automatically on every push. Old previews are cleaned up after 30 days. |
|
After this change, top navigation menu looks like: I think it should be reworked but probably as a separate task. |
4 participants
Why
The Try page described a product we no longer ship. It required an OpenAI
or Claude API token in five separate places and stated that the AI module
would not activate without a GitHub sign-in. Since
jelastic-jps/constructor-fabric#8 the agent is selected during sign-up and
authenticated with the visitor's own account inside the IDE — no API key is
ever requested. Every visitor who did not have a token was being told,
incorrectly, that they were not eligible.
The second problem was placement. The email form lived in a side column of
the section below the hero, so the only conversion action on the page was
not on screen when the page loaded.
What changed
Accuracy
ChatGPT, or GitHub for Copilot; (2) a password you choose at sign-up,
stored only as a hash and not recoverable.
specs → code and tests), each gated before the next unlocks.
description,og:descriptionandtwitter:descriptionupdated to match.Placement and flow
and in a new full-width "Deploy your environment" section placed after
"What you get".
useId()keeps the two input ids unique."Start your trial" as though nothing had happened.
After confirmation → Start now.
there is one form implementation rather than two.
Supporting
JPEG showed the retired eight-step trainer with
.cf-constructornaming.Added
height:autoso the intrinsic-size attributes do not stretch it.traffic-light dots. They belonged to a window mock-up; the panel is a
titled card, not a window.
unchanged beside it.
.containermissingposition:relative— the absolutelypositioned
.hero-bgwas covering the page and swallowing clicks on thenew form. try.html was the only one of seven pages missing it.
Testing
Verified locally at mobile, tablet and desktop widths: both forms accept
input, validate, and reach the success and error states; the two inputs
carry distinct ids; no console errors beyond the pre-existing CookieYes
domain warning, which only appears on localhost.
Created with the help of Claude Code