feat: whyrating - initial project from turbostarter boilerplate

.context/turbostarter-framework-context/sections/web/troubleshooting/billing.md

@@ -0,0 +1,25 @@
+---
+title: Billing
+description: Find answers to common billing issues.
+url: /docs/web/troubleshooting/billing
+---
+
+# Billing
+
+## Checkout can't be created
+
+This happen in the following cases:
+
+1. The environment variables are not set correctly. Please make sure you have set the environment variables corresponding to your billing provider in `.env.local` if locally - or in your hosting provider's dashboard if in production
+2. The price IDs used are incorrect. Make sure to use the exact price IDs as they are in the payment provider's dashboard.
+
+[Read more about billing configuration](/docs/web/billing/configuration)
+
+## Database is not updated after subscribing to a plan
+
+This may happen if the webhook is not set up correctly. Please make sure you have set up the webhook in the payment provider's dashboard and that the URL is correct.
+
+If working locally, make sure that:
+
+1. If using Stripe, that the Stripe CLI or configured proxy is up and running ([see the Stripe documentation for more information](/docs/web/billing/stripe#create-a-webhook))
+2. If using Lemon Squeezy, that the webhook set in Lemon Squeezy is correct and that the server is running. Additionally, make sure the proxy is set up correctly if you are testing locally ([see the Lemon Squeezy documentation for more information](/docs/web/billing/lemon-squeezy#create-a-webhook)).

.context/turbostarter-framework-context/sections/web/troubleshooting/deployment.md

@@ -0,0 +1,45 @@
+---
+title: Deployment
+description: Find answers to common web deployment issues.
+url: /docs/web/troubleshooting/deployment
+---
+
+# Deployment
+
+## Deployment build fails
+
+This is most likely an issue related to the environment variables not being set correctly in the deployment environment. Please analyse the logs of the deployment provider to see what is the issue.
+
+The kit is very defensive about incorrect environment variables, and will throw an error if any of the required environment variables are not set. In this way - the build will fail if the environment variables are not set correctly - instead of deploying a broken application.
+
+Check our guides for the most popular hosting providers for more information on how to deploy your TurboStarter project correctly:
+
+<Cards>
+  <Card title="Vercel" description="Deploy your TurboStarter web app to Vercel platform." href="/docs/web/deployment/vercel" />
+
+  <Card title="Netlify" description="Deploy your TurboStarter web app to Netlify platform." href="/docs/web/deployment/netlify" />
+
+  <Card title="Render" description="Deploy your TurboStarter web app to Render platform." href="/docs/web/deployment/render" />
+
+  <Card title="Railway" description="Deploy your TurboStarter web app to Railway platform." href="/docs/web/deployment/railway" />
+
+  <Card title="AWS Amplify" description="Deploy your TurboStarter web app to AWS Amplify platform." href="/docs/web/deployment/amplify" />
+
+  <Card title="Docker" description="Containerize your TurboStarter web app using Docker." href="/docs/web/deployment/docker" />
+
+  <Card title="Fly.io" description="Deploy your TurboStarter web app to Fly.io platform." href="/docs/web/deployment/fly" />
+</Cards>
+
+## What should I set as a URL before my first deployment?
+
+That's very good question! For the first deployment you can set any URL, and then, after you (or your provider) assign a domain name, you can change it to the correct one. There's nothing wrong with redeploying your project multiple times.
+
+## Sign in with OAuth provider doesn't work
+
+This is most likely a settings issues in the provider's settings. To troubleshoot this issue, follow these steps:
+
+1. **Verify provider settings**: Ensure that the OAuth provider's settings are correctly configured. Check that the client ID, client secret, and redirect URI are accurate and match the values in your application.
+2. **Check environment variables**: Confirm that the environment variables for the OAuth provider are set correctly in your application production environment.
+3. **Validate callback URLs**: Ensure that the callback URLs for each provider are set correctly and match the URLs in your application. This is crucial for the OAuth flow to work correctly.
+
+Please read [Better Auth documentation](https://www.better-auth.com/docs/concepts/oauth) for more information on how to set up third-party providers.

.context/turbostarter-framework-context/sections/web/troubleshooting/emails.md

@@ -0,0 +1,44 @@
+---
+title: Emails
+description: Find answers to common emails issues.
+url: /docs/web/troubleshooting/emails
+---
+
+# Emails
+
+## I want to use a different email provider
+
+Of course! You can use any email provider that you want. All you need to do is to implement the `EmailProviderStrategy` and export it in your `index.ts` file.
+
+[Read more about sending emails](/docs/web/emails/sending)
+
+## My emails are landing in the spam folder
+
+Emails landing in spam folders is a common issue. Here are key steps to improve deliverability:
+
+1. **Configure proper domain setup**:
+   * Use a dedicated subdomain for sending emails (e.g., mail.yourdomain.com)
+   * Ensure [reverse DNS (PTR) records](https://www.cloudflare.com/learning/dns/dns-records/dns-ptr-record/) are properly configured
+   * Warm up your sending domain gradually
+
+2. **Implement authentication protocols**:
+   * Set up [SPF records](https://www.cloudflare.com/learning/dns/dns-records/dns-spf-record/) to specify authorized sending servers
+   * Enable [DKIM signing](https://www.cloudflare.com/learning/dns/dns-records/dns-dkim-record/) to verify email authenticity
+   * Configure [DMARC policies](https://www.cloudflare.com/learning/dns/dns-records/dns-dmarc-record/) to prevent spoofing
+
+3. **Follow deliverability best practices**:
+   * Include clear unsubscribe mechanisms in all marketing communications
+   * Personalize content appropriately
+   * Avoid excessive promotional language and spam triggers
+   * Maintain consistent HTML formatting and styling
+   * Only include links to verified domains
+   * Keep a regular sending schedule
+   * Clean your email lists regularly
+   * Use double opt-in for new subscribers
+
+4. **Monitor and optimize**:
+   * Track key metrics like delivery rates, opens, and bounces
+   * Monitor spam complaint rates
+   * Review email authentication reports
+   * Test emails across different clients and devices
+   * Adjust sending practices based on performance data

.context/turbostarter-framework-context/sections/web/troubleshooting/installation.md

@@ -0,0 +1,99 @@
+---
+title: Installation
+description: Find answers to common web installation issues.
+url: /docs/web/troubleshooting/installation
+---
+
+# Installation
+
+## Cannot clone the repository
+
+Issues related to cloning the repository are usually related to a Git misconfiguration in your local machine. The commands displayed in this guide using SSH: these will work only if you have setup your SSH keys in Github.
+
+If you run into issues, [please make sure you follow this guide to set up your SSH key in Github.](https://docs.github.com/en/authentication/connecting-to-github-with-ssh)
+
+If this also fails, please use HTTPS instead. You will be able to see the commands in the repository's Github page under the "Clone" dropdown.
+
+Please also make sure that the account that accepted the invite to TurboStarter, and the locally connected account are the same.
+
+## My environment variables from `.env.local` file are not being loaded
+
+Make sure you are running the `pnpm dev` command from the root directory of your project (where the `pnpm-workspace.yaml` file is located)
+
+Also, ensure that the `.env.local` files are present in the apps that need them. For example, the `.env` file should be present in the `apps/web` directory for the web app.
+
+<Callout>
+  TurboStarter uses the `dotenv-cli` to load environment variables from a `.env` files. The `dotenv-cli` is automatically used when running the `pnpm dev` command from the root directory.
+</Callout>
+
+## Next.js server doesn't start
+
+This may happen due to some issues in the packages. Try to clean the workspace using the following command:
+
+```bash
+pnpm clean
+```
+
+Then, reinstall the dependencies:
+
+```bash
+pnpm i
+```
+
+You can now retry running the dev server.
+
+## Local database doesn't start
+
+If you cannot run the local database container, it's likely you have not started [Docker](https://docs.docker.com/get-docker/) locally. Our local database requires Docker to be installed and running.
+
+Please make sure you have installed Docker (or compatible software such as [Colima](https://github.com/abiosoft/colima), [Orbstack](https://github.com/orbstack/orbstack)) and that is running on your local machine.
+
+Also, make sure that you have enough [memory and CPU allocated](https://docs.docker.com/engine/containers/resource_constraints/) to your Docker instance.
+
+## I don't see my translations
+
+If you don't see your translations appearing in the application, there are a few common causes:
+
+1. Check that your translation `.json` files are properly formatted and located in the correct directory
+2. Verify that the language codes in your configuration match your translation files
+3. Enable debug mode (`debug: true`) in your i18next configuration to see detailed logs
+
+[Read more about configuration for translations](/docs/web/internationalization/configuration)
+
+## "Module not found" error
+
+This issue is mostly related to either dependency installed in the wrong package or issues with the file system.
+
+The most common cause is incorrect dependency installation. Here's how to fix it:
+
+1. Clean the workspace:
+
+   ```bash
+   pnpm clean
+   ```
+
+2. Reinstall the dependencies:
+   ```bash
+   pnpm i
+   ```
+
+If you're adding new dependencies, make sure to install them in the correct package:
+
+```bash
+# For main app dependencies
+pnpm install --filter web my-package
+
+# For a specific package
+pnpm install --filter @turbostarter/ui my-package
+```
+
+If the issue persists, please check the file system for any issues.
+
+### Windows OneDrive
+
+OneDrive can cause file system issues with Node.js projects due to its file syncing behavior. If you're using Windows with OneDrive, you have two options to resolve this:
+
+1. Move your project to a location outside of OneDrive-synced folders (recommended)
+2. Disable OneDrive sync specifically for your development folder
+
+This prevents file watching and symlink issues that can occur when OneDrive tries to sync Node.js project files.