We launch a feature here on Thursday, and the landing page section for it is the one new users keep bringing up on calls and in replies, more than the hero, more than pricing.
It is a simple block. One sentence: see the change before it ships. One picture of a working copy of your site with the change on it, and two buttons: approve, or send it back.
I think it works because it answers the question people actually have about any tool that writes code for them: what if it gets it wrong? The answer is not trust us , it is look at it first . The other sections explain what it does. This one removes the fear.
Curious what the equivalent section is on your landing page: the one that answers the fear rather than describing the feature. And for those who have run the test, did it convert better than the feature description?
seeing the section on our real page before anyone merges is realy what our marketing side keeps asking for
if the change touches something shared like the header, does the preview show it across all pages or only the one you described??? and what about pages behind a login???
@thamibenjelloun Good questions, both of them.
Shared header: the preview shows the page where the change was made, so you see the new header there, in context, before anyone merges. It does not walk through every other page that uses the same header. For a shared component like that, your developer checks the rest in the pull request, where the change to the header is a single file anyway.
Pages behind a login: the preview runs on sample data rather than your real backend, so it does not depend on a real signed-in session. How well a page behind login renders depends on how your app handles sign-in. What do you use for it? I can tell you what to expect.
@thamibenjelloun Thanks, that's exactly who we built it for.
Two great questions. What I can say for sure: the preview opens on the page your change affects, and it runs on generated sample data, not your real accounts. How far you can click from there, to other pages or into logged-in areas, is a question for @mikita_aliaksandrovich, and I'd rather he gives you the exact answer than I guess.
What's the first thing your marketing side would want to see in a preview?