-
Notifications
You must be signed in to change notification settings - Fork 809
Added Prisma Postgres guide to docs/integrations/databases/
#2465
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
base: main
Are you sure you want to change the base?
Added Prisma Postgres guide to docs/integrations/databases/
#2465
Conversation
@aidankmcalister is attempting to deploy a commit to the Clerk Production Team on Vercel. A member of the Team first needs to authorize it. |
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Thank you Aidan for writing this guide, I'll run through it now! I've added a preview link if you'd like to see how it looks on the docs site. |
I'll have a final review here once Aidan addresses Nick's comments :) |
Thank you for taking a look at this! @alexisintech, I've implemented the changes requested by @NWylynko and made additional updates to align with the latest version of Prisma ORM (v6.16). One of the changes I made was:
I'm not sure about the proper title for it, but is there a flag that can indicate to remove this line and add this one? Similar to how other docs and GitHub use red for removal and green for addition. |
yes! see this section in our contributing guide: https://github.com/clerk/clerk-docs/blob/main/CONTRIBUTING.md#highlighting you can write something like
using |
## Create a new Next.js project | ||
|
||
Create a new Next.js project using the following command: | ||
|
||
```sh {{ filename: 'terminal' }} | ||
npx create-next-app clerk-prisma-example --typescript --eslint --tailwind --use-npm --no-src-dir --app --import-alias "@/*" | ||
``` |
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 like to have users start from the nextjs quickstart, and then hit this guide. so this part shouldn't be necessary.
the guide should be written as if the user just came from the quickstart - the next step would be what do they need to install for the guide.
with this in mind, i think these first two sections ("create a new nextjs project" and "integrate the nextjs clerk sdk") need a bit of restructuring
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.
Got it. I should be able do that tomorrow then.
🔎 Previews:
What does this solve?
What changed?
docs/integrations/databases/prisma-postgres.mdx
as a complete new guideChecklist