(docs: nextjs QS) fix incorrect title; update convexclientprovider explanation

[alexisintech]

Clerk employee here 👋 While checking out the Convex docs to see how to integrate Convex into a Clerk + Next.js app, I noticed the Next.js QS could use some love. From the Clerk Docs team to yours 💜

Notes about the changes:

• This all actually started as just a title change, I saw "Create a React app" and I was like, well actually you're creating a Next.js app. So I went to open a PR, and was like, well while I'm here, I'll just update a few more things...
• Organize order of events sequentially, for better UX. E.g. "in the convex/ folder" should be the lead of a sentence, because its the first in a sequence of events. A user will first need to go to their convex/ folder to then create a new file; it's the first step so it should be the first direction given in the sentence.
• The colon change in and the export name: `api.tasks.get`.. It originally read as the export name, `api.tasks.get`. which grammatically was telling me that the export name was api.tasks.get which I was really confused by. When I finally got to the end of the QS, I learned that the API function itself is what's called api.tasks.get and then I understood what the doc was trying to convey. So I've made a small change to help understandability.
• Updated the explanation of creating a provider wrapper. I feel the copy was telling me what the code was doing syntactically, but the code speaks for itself. That's why there's an example paired with the copy! So instead, the copy here should be explaining what the code is doing. I updated the explanation to the best of my ability, and to how it made sense to me, but if the explanation is incorrect then of course, feel free to update.

Also, I'm surprised you don't abstract the ConvexClientProvider part away for users so they can skip the step of creating it themselves and simply import it from Convex itself and then wrap their app (similar to how we do ClerkProvider). 👀

Cheers 😸💖

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[thomasballinger]

Thank you! I'll land this, expect to see it out later today

[thomasballinger]

Suggested change

	For `<ConvexProvider>` to work on the client, `<ConvexReactClient>` must be passed to it.
	For `<ConvexProvider>` to work on the client, `ConvexReactClient` must be passed to it.

[thomasballinger]

Suggested change

	package, which provides a convenient interface for working
	with Convex.
	package.

agree "from a React app" wasn't very useful, and now the rest doesn't seem useful either IMO

[thomasballinger]

Suggested change

	In the `app/` folder, add a new file <JSDialectFileName name="ConvexClientProvider.tsx" /> with the following code. This creates a component that wraps `<ConvexProvider>` and passes it the `<ConvexReactClient>`.
	In the `app/` folder, add a new file <JSDialectFileName name="ConvexClientProvider.tsx" /> with the following code. This creates a client component that wraps `<ConvexProvider>` and passes it the `<ConvexReactClient>`.

[thomasballinger]

since "development server" is an overloaded term in convex I'll add "Next.js" or "frontend" here

[thomasballinger]

So instead, the copy here should be explaining what the code is doing

love it

[thomasballinger]

Also, I'm surprised you don't abstract the ConvexClientProvider part away for users so they can skip the step of creating it themselves and simply import it from Convex itself and then wrap their app (similar to how we do ClerkProvider).

Yeah good point, we held off to avoid needing to create Next.js-specific code using the (at the time only used by) Next.js "use client" directives with the goal of keeping the convex package very general; but now that we have some Next.js-specific code in convex/nextjs it seems like time to do this! The Clerk nextjs package has been helpful to look at for how to build great libraries that work well with Next.js.

Maybe soon! This isn't the only way to set this up Convex providers with Clerk but it seems reasonable to make the common path easier.

[thomasballinger]

Landed in 85fe152

Thanks @alexisintech!

[alexisintech]

Landed in 85fe152

Thanks @alexisintech!

woah what did you do to get it into that commit??

also, love all the helpful communication and openness to accepting these updates ❤️ thanks so much :)

[thomasballinger]

thanks for sharing the motivation behind these changes, gives us some positive second order effects from teaching in addition to the specific improvements!

we're using copybara to get code between our open source repo and the closed-source one, which unfortunately means the PR shows as Closed instead of Merged here but at least does preserve authorship via Co-authored-by:

[alexisintech]

awesome! i've never seen that, its so cool