The code changes involve a significant update to the configuration of our CMS client. The nature of retrieving content items has been refactored to be more granular, allowing for the identification and fetching of content from specified collections rather than general categories. These modifications improve the efficiency and specificity of content queries. Furthermore, other changes were made to provide a better alignment of our content structure, including the reorganization of content files and renaming of image paths in various components for consistency.
Your Application
Write here everything about your application.
Setup
For working locally, please add a file named .env.local where we can place our environment variables. This file is not committed to Git, therefore it is safe to store sensitive information in it.
After starting Supabase, copy the service role key from the Supabase project settings and add it to the .env.local file.
SUPABASE_SERVICE_ROLE_KEY=your-service-role-key
Stripe
For the Stripe integration, first we need to start the Stripe CLI:
pnpm run stripe:listen
Then, update the .env.local file with the following variables:
STRIPE_WEBHOOK_SECRET=
STRIPE_SECRET_KEY=
NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY=
Supabase
Please follow the instructions in the Supabase README to setup your Supabase project.