Revamp of "Next steps" section at the bottom of each Quickstart/Getting Started guide #3003
Conversation
…-guides-consistent
…-guides-consistent
…-guides-consistent
…-guides-consistent
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
SarahSoutoul
changed the title
SarahSoutoul
changed the title
| - [Prebuilt components](/docs/reference/components/overview) | ||
| - Learn how to quickly add authentication to your app using Clerk's suite of components. |
There was a problem hiding this comment.
clerk expo doesn't support prebuilt components, unless they're using web (but it's more likely clerk user's using the expo sdk are using it for native development). i'd link to the custom flows instead! this means that the next card, customization & localization, probably isn't necessary as well.
There was a problem hiding this comment.
Done here: Remove prebuilt components. @alexisintech
| <Cards> | ||
| - [Protect API routes using clerkMiddleware()](/docs/reference/nuxt/clerk-middleware) | ||
| - Learn how to protect specific API routes from unauthenticated users. | ||
| - [Prebuilt components](/docs/reference/components/overview) |
There was a problem hiding this comment.
for vue and nuxt, they're called composables!
There was a problem hiding this comment.
@alexisintech Aren't composables the hooks?
|
|
||
| - [Client-side helpers](/docs/reference/nuxt/overview#client-side-helpers) | ||
| - Learn more about Nuxt client-side helpers and how to use them. | ||
| - [Client-side helpers (composables)](/docs/reference/nuxt/overview#client-side-helpers) |
There was a problem hiding this comment.
this is a duplicate of the first card (prebuilt components)
There was a problem hiding this comment.
It's not tho? They're linking to two diff things? @alexisintech
There was a problem hiding this comment.
yeah i was confused btwn composables and components :P
| @@ -112,7 +112,7 @@ Learn more about Clerk components, how to customize them, and how to use Clerk's | |||
|
|
|||
| <Cards> | |||
| - [Prebuilt components](/docs/reference/components/overview) | |||
There was a problem hiding this comment.
same comments that i left for nuxt! swap components for composables
There was a problem hiding this comment.
Co-authored-by: Alexis Aguilar <98043211+alexisintech@users.noreply.github.com>
alexisintech
left a comment
alexisintech
left a comment
There was a problem hiding this comment.
great work here friend 👏 🐐
🔎 Previews:
What does this solve?
This PR is part of the wider Docs IA V2 project aiming at making our docs more consistent and offering a better UX experience for our users. This particular PR revisits what belongs under the Next steps sections across our Getting started guides. The goal was to have a cleaner/clearer Next steps section at the bottom of each Quickstart/Getting Started guide that calls out the main things you'd likely want to do next.
While the focus was on Getting Started guides, I looked at the Next steps sections across our docs to make it all consistent, including guides under the
Organizationtab or the Custom sign-in-or-up guides. See details below.What changed?
OrganizationstabThe thought process that went into choosing what goes in each Next steps section
For most SDKs (frontend), my choices were the following:
For native SDKs like Android and iOS, the Next steps follows this thread:
For Backend SDKs like Fastify, Express, etc, the Next steps consists of links to resources to protect routes, and a link to the SDK reference.
The Chrome Extension SDK is prob the most different one out of all of them given its very specific guides.
Deadline
When do you need this PR reviewed/shipped by?
Optional - uncomment if needed. If not provided, we will prioritize it ourselves.
-->