Oct 22, 2022
Oct 22, 2022
Add OAuth connections after Sign Up, revamped Next.js documentation, and a Product Hunt relaunch
In the past, when an OAuth connection was turned on, it was required to be available as a sign-up option.
Now, developers can choose whether each OAuth provider is available during sign-up and sign-in, or if the connection should be made later.
This is especially useful for applications that prefer to connect third-parties after the fact. For example, a Github connection can be made after sign-up if an application wants to read repository data.
After sign-up, Connections can be made through our <UserProfile/> component, or with a custom flow.
We're reorganizing our documentation to have Frameworks at the top-level, and Concepts at the second-level, instead of vice-versa.
We've found that different frameworks uses slightly different concepts (for example,
getServerSideProps in Next.js vs
loaders in Remix), and that has made it challenging to organize our documentation with Concepts at the top level.
Over the coming weeks, we'll be inverting the documentation to help developers answer their questions faster. The first to get this treatment was Next.js, which is now available here.
Yesterday, we relaunched on Product Hunt to share our progress over the last year. We wanted to add a special thank you in our changelog to our existing customers, who showed up with kind words in the comments and plenty of upvotes. Thank you!
Start completely free for up to 5,000 monthly active users and up to 10 monthly active orgs. No credit card required.
Learn more about our transparent per-user costs to estimate how much your company could save by implementing Clerk.
The latest news and updates from Clerk, sent to your inbox.