This commit refactors the CMS to handle two platforms: ContentLayer and WordPress. The CMS layer is abstracted into a core package, and separate implementations for each platform are created. This change allows the app to switch the CMS type based on environment variable, which can improve the flexibility of content management. It also updates several functions in the `server-sitemap.xml` route to accommodate these changes and generate sitemaps based on the CMS client. Further, documentation content and posts have been relocated to align with the new structure. Notably, this refactor is a comprehensive update to the way the CMS is structured and managed.
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.