A/B test for AI Site Generation

[officiallygod]

Proposed changes

Shows a Random different Fork Page to the user for A/B Testing

Type of Change

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

• I have read the CONTRIBUTING doc
• Linting and tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

New Look

Note: Please check the earlier events if they are working as expected.

[arunshenoy99]

@officiallygod Quick question: How does this work if we want to do A/B testing with other steps? Is it a good idea to use some kind of state handler that determines what needs to be rendered that we reuse?

[officiallygod]

@officiallygod Quick question: How does this work if we want to do A/B testing with other steps? Is it a good idea to use some kind of state handler that determines what needs to be rendered that we reuse?

The requirements are very specific to a section of the page and doing that would make us send all that data to the parent and again have a lot of dup code as we would then need to build 4 completely independent components which do the same thing (StartOptions in this case).

[officiallygod]

Onboarding Data: newfold-labs/wp-module-onboarding-data#68