-
Notifications
You must be signed in to change notification settings - Fork 487
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
feat: Introduce Waitlist component docs #1696
feat: Introduce Waitlist component docs #1696
Conversation
Hey, here’s your docs preview: https://clerk.com/docs/pr/1696 |
dfe4573
to
f12fde7
Compare
> [!NOTE] | ||
> The `<Waitlist />` component is only available in Core 2. If you are using Next.js is available after <code>@clerk/nextjs\@6.2.0</code> |
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.
We don't need to mention the Core 2 part, because the users are in the Core 2 docs. Core 1 users would be in the Core 1 docs, where none of this would exist because these features don't exist in Core 1.
Do you mean to mention that the Waitlist component will only work with Next.js versions 6.2.0 and above?
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.
We don't need to mention the Core 2 part, because the users are in the Core 2 docs. Core 1 users would be in the Core 1 docs, where none of this would exist because these features don't exist in Core 1.
Do you mean to mention that the Waitlist component will only work with Next.js versions 6.2.0 and above?
@alexisintech sure I'll remove the reference for Core 2
about nextjs package yes it's available from 6.2.0 and above. The reason is because Waitlist
is a totally new component and we can't export in the previous nextjs versions
We are removing all JavaScript |
adf34a7
to
8787324
Compare
docs/manifest.json
Outdated
{ | ||
"title": "Waitlist Components", | ||
"items": [ | ||
[ | ||
{ | ||
"title": "`<Waitlist />`", | ||
"wrap": false, | ||
"href": "/docs/components/waitlist/overview" | ||
} | ||
] | ||
] | ||
}, |
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.
what do you think about putting this under the "Authentication components" aka /components/authentication
?
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 don't think that it's the correct section because waitlist as a term is before authentication :) open to discuss it if you have time
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.
will there ever be other sign-up mode components? maybe we can rename the section to "Sign-up mode components"
If not, then I suppose we should change to "Waitlist component". Not plural components, because there's only one component.
4bfd6a9
to
6d18038
Compare
docs/manifest.json
Outdated
{ | ||
"title": "Waitlist Components", | ||
"items": [ | ||
[ | ||
{ | ||
"title": "`<Waitlist />`", | ||
"wrap": false, | ||
"href": "/docs/components/waitlist/overview" | ||
} | ||
] | ||
] | ||
}, |
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.
will there ever be other sign-up mode components? maybe we can rename the section to "Sign-up mode components"
If not, then I suppose we should change to "Waitlist component". Not plural components, because there's only one component.
e54fca5
to
320a42a
Compare
I think its all good! I just wanna get Victoria's review, and then we can approve :) |
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.
minor changes
you can merge whenever :) |
Co-authored-by: victoria <[email protected]>
Co-authored-by: victoria <[email protected]>
Co-authored-by: victoria <[email protected]>
Co-authored-by: victoria <[email protected]>
Co-authored-by: victoria <[email protected]>
2cc400a
to
1d12c85
Compare
Important
🔎 Previews:
Explanation:
This PR: