Docs: Update no code experiments #10377
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
||
| The **experiment type** setting enables you to choose how your experiment is implemented. Note that once the experiment type is selected and saved, it cannot be changed. | ||
| > **What about product experiments?** [Product experiments](/docs/experiments/creating-an-experiment) use custom code to manage how variants modify your product. This option is best if you need specific, code-based adjustments and configurations. |
There was a problem hiding this comment.
What do you think about moving this further up, and then including a similar mention at the top of "Creating an experiment"? I think I expected to see this much earlier. It would be helpful to clearly identify the two, and where they overlap vs. differ.
There was a problem hiding this comment.
I think this is fine for now because people who end up on this page are definitely looking for "no code experiments" (its in title/navbar).
We should rework this note and "creating an experiment" once no-code experiments releases from early access. Once everyone has the option to decide product vs no-code experiment, then it will be important to clarify this.
| - Add multiple element changes to a variant by clicking **+ Add element**. | ||
| - Remove an element from a variant by clicking the trash bin icon. | ||
| - Add variants by clicking **+ Add variant**. | ||
| - Change all elements, headers, buttons, and/or images by clicking the **Change element** dropdown. |
There was a problem hiding this comment.
@jurajmajerik I think this is a confusing feature. We might want to review usage / drop it entirely.
Co-authored-by: Daniel Bachhuber <[email protected]>
Changes
As part of PostHog/posthog#27361, update no-code experiments doc.
Mostly simplifying and streamlining things. I think there is a lot that is obvious from the UI and doesn't need to be written out.
Also a few fixes and a couple backlinks :)
Checklist
Article checklist