-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement the dotlink version of Link in Bio flow on Stepper #71204
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pretty cool! I love this, much better than before. I suppose we can remove this logic now?
I'll do a more thorough review soon.
const logInUrl = | ||
locale && locale !== 'en' | ||
? `/start/account/user/${ locale }?variationName=${ flowName }&pageTitle=Link%20in%20Bio&redirect_to=/setup/${ flowName }/patterns` | ||
: `/start/account/user?variationName=${ flowName }&pageTitle=Link%20in%20Bio&redirect_to=/setup/${ flowName }/patterns`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to do this manually?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose we don't. This PR focuses on making the flow work first, so I simply refer to how link-in-bio.ts
does it for now. It can be improved as a separate PR for sure :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes @alshakero, this is how we are doing in the LiB flow as well, I think it can be good here for this PR :)
You are right. I plan to remove all the previous work as a follow-up PR, and it will be part of the tidying up :) |
dotlink Link in Bio flow.
This PR modifies the release build for happy-blocks To test your changes on WordPress.com, run To deploy your changes after merging, see the documentation: PCYsg-r7r-p2 |
This PR modifies the release build for editing-toolkit To test your changes on WordPress.com, run To deploy your changes after merging, see the documentation: PCYsg-mMA-p2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From a Stepper standpoint, this looks great. I haven't tested though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
? `/start/account/user/${ locale }?variationName=${ flowName }&pageTitle=Link%20in%20Bio&redirect_to=/setup/${ flowName }/patterns` | ||
: `/start/account/user?variationName=${ flowName }&pageTitle=Link%20in%20Bio&redirect_to=/setup/${ flowName }/patterns`; | ||
|
||
// for the standard Link in Bio flow |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only a minor thing, I think you can change/remove this comment here 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. The suggested fix has been taken :D
const logInUrl = | ||
locale && locale !== 'en' | ||
? `/start/account/user/${ locale }?variationName=${ flowName }&pageTitle=Link%20in%20Bio&redirect_to=/setup/${ flowName }/patterns` | ||
: `/start/account/user?variationName=${ flowName }&pageTitle=Link%20in%20Bio&redirect_to=/setup/${ flowName }/patterns`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes @alshakero, this is how we are doing in the LiB flow as well, I think it can be good here for this PR :)
Remove the non-necessary comment. Co-authored-by: Omar Alshaker <omar@omaralshaker.com>
@escapemanuele Thanks for taking a look :)
Yes, it's kept intentionally. When someone clicks "Decide Later", their site will be defaulted to a free |
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~229 bytes added 📈 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~3590 bytes added 📈 [gzipped])
Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. Async-loaded Components (~254 bytes removed 📉 [gzipped])
React components that are loaded lazily, when a certain part of UI is displayed for the first time. Legend What is parsed and gzip size?Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory. Generated by performance advisor bot at iscalypsofastyet.com. |
Proposed Changes
This PR implements the dotlink version of Link in Bio flow on Stepper, aiming at completly replacing the previous
/start/link-in-bio-tld
. The TLD suffix is kept, since my understanding is that the possibilities of partnership with different TLDs are still there. The current implmentation is strictly .link only, but it should be enough to provide clues for a more general solution in the future.Currently, the flow is implmeneted as interweaving of the signup framework and the Stepper framework, initiating from
/start/link-in-bio-tld?tld=link
. Unfortunately it has encountered an unsolvable issue given that approach(see p2-p4TIVU-akM). Overall the implementation is just:link
aspromoTlds
andmanagedSubdomains***
props.By doing so, it also means there are some janitorial tasks that has to be done, and they will be completed by follow-up PRs to keep the scope of this PR. See 1348-gh-Automattic/martech.
Among testing, I've also found a few back-navigation issues:
However, they are more of the general issues that need to happen at the framework level, so this PR won't address them.
Testing Instructions
/setup/link-in-bio-tld
link
domain to choose from. The freew.link
domain should have 2 options.w.link
or.link
successfully.Pre-merge Checklist
Related to #