Edit packages/database/migrations/20240229062232_adds_styling_column_to_product_model/data-migration.ts

.devcontainer/devcontainer.json

@@ -12,8 +12,8 @@
     // Configure properties specific to VS Code.
     "vscode": {
       // Add the IDs of extensions you want installed when the container is created.
-      "extensions": ["dbaeumer.vscode-eslint"]
-    }
+      "extensions": ["dbaeumer.vscode-eslint"],
+    },
   },
 
   // Use 'forwardPorts' to make a list of ports inside the container available locally.
@@ -25,5 +25,5 @@
   "postAttachCommand": "pnpm dev --filter=web... --filter=demo...",
 
   // Comment out to connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
-  "remoteUser": "node"
+  "remoteUser": "node",
 }

.env.example

@@ -56,14 +56,11 @@ SMTP_PASSWORD=smtpPassword
 
 # Uncomment the variables you would like to use and customize the values.
 
-# Custom local storage path for file uploads
-#UPLOADS_DIR=
-
 ##############
 # S3 STORAGE #
 ##############
 
-# S3 Storage is required for the file upload in serverless environments like Vercel
+# S3 Storage is required for the file uplaod in serverless environments like Vercel
 S3_ACCESS_KEY=
 S3_SECRET_KEY=
 S3_REGION=
@@ -147,10 +144,6 @@ GOOGLE_SHEETS_REDIRECT_URL=
 # Oauth credentials for Airtable integration
 AIRTABLE_CLIENT_ID=
 
-# Oauth credentials for Slack integration
-SLACK_CLIENT_ID=
-SLACK_CLIENT_SECRET=
-
 # Enterprise License Key
 ENTERPRISE_LICENSE_KEY=
 
@@ -169,12 +162,3 @@ ENTERPRISE_LICENSE_KEY=
 
 # Ignore Rate Limiting across the Formbricks app
 # RATE_LIMITING_DISABLED=1
-
-# OpenTelemetry URL for tracing
-# OPENTELEMETRY_LISTENER_URL=http://localhost:4318/v1/traces
-
-# The below is used for Next Caching (uses In-Memory from Next Cache if not provided)
-# REDIS_URL:
-
-# The below is used for Rate Limiting (uses In-Memory LRU Cache if not provided) (You can use a service like Webdis for this)
-# REDIS_HTTP_URL:

.github/PULL_REQUEST_TEMPLATE.md

@@ -32,7 +32,6 @@ Fixes # (issue)
 - [ ] Removed all `console.logs`
 - [ ] Merged the latest changes from main onto my branch with `git pull origin main`
 - [ ] My changes don't cause any responsiveness issues
-- [ ] First PR at Formbricks? [Please sign the CLA!](https://cla-assistant.io/formbricks/formbricks) Without it we wont be able to merge it 🙏
 
 ### Appreciated
 

.github/actions/cache-build-web/action.yml

@@ -6,8 +6,6 @@ runs:
     - name: Checkout repo
       uses: actions/checkout@v3
 
-    - uses: ./.github/actions/dangerous-git-checkout
-
     - name: Cache Build
       uses: actions/cache@v3
       id: cache-build
@@ -15,12 +13,13 @@ runs:
         cache-name: prod-build
         key-1: ${{ hashFiles('pnpm-lock.yaml') }}
         key-2: ${{ hashFiles('apps/**/**.[jt]s', 'apps/**/**.[jt]sx', 'packages/**/**.[jt]s', 'packages/**/**.[jt]sx', '!**/node_modules') }}
+        key-3: ${{ github.event.pull_request.number || github.ref }}
       with:
         path: |
           ${{ github.workspace }}/apps/web/.next
           **/.turbo/**
           **/dist/**
-        key: ${{ runner.os }}-${{ env.cache-name }}-${{ env.key-1 }}-${{ env.key-2 }}
+        key: ${{ runner.os }}-${{ env.cache-name }}-${{ env.key-1 }}-${{ env.key-2 }}-${{ env.key-3 }}
 
     - name: Setup Node.js 20.x
       uses: actions/setup-node@v3
@@ -45,7 +44,6 @@ runs:
       run: |
         SECRET=$(openssl rand -hex 32)
         echo "ENCRYPTION_KEY=$SECRET" >> $GITHUB_ENV
-        echo "ENTERPRISE_LICENSE_KEY=$SECRET" >> $GITHUB_ENV
       shell: bash
 
     - run: |

.github/workflows/cron-closeOnDate.yml

@@ -1,12 +1,11 @@
-name: Cron - Survey status update
+name: Cron - closeOnDate
 
 on:
-  workflow_dispatch:
   # "Scheduled workflows run on the latest commit on the default or base branch."
   # — https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows#schedule
-  # schedule:
-  # Runs “At 00:00.” (see https://crontab.guru)
-  # - cron: "0 0 * * *"
+  schedule:
+    # Runs “At 00:00.” (see https://crontab.guru)
+    - cron: "0 0 * * *"
 jobs:
   cron-weeklySummary:
     env:
@@ -17,7 +16,7 @@ jobs:
       - name: cURL request
         if: ${{ env.APP_URL && env.CRON_SECRET }}
         run: |
-          curl ${{ env.APP_URL }}/api/cron/survey-status \
+          curl ${{ env.APP_URL }}/api/cron/close_surveys \
             -X POST \
             -H 'content-type: application/json' \
             -H 'x-api-key: ${{ env.CRON_SECRET }}' \

.github/workflows/cron-reportUsageToStripe.yml

@@ -1,12 +1,11 @@
-name: Cron - Report usage to Stripe
+name: Cron - reportUsageToStripe
 
 on:
-  workflow_dispatch:
   # "Scheduled workflows run on the latest commit on the default or base branch."
   # — https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows#schedule
-  # schedule:
-  # This will run the job at 20:00 UTC every day of every month.
-  # - cron: "0 20 * * *"
+  schedule:
+    # This will run the job at 20:00 UTC every day of every month.
+    - cron: "0 20 * * *"
 jobs:
   cron-reportUsageToStripe:
     env:

.github/workflows/cron-weeklySummary.yml

@@ -1,12 +1,11 @@
-name: Cron - Weekly summary
+name: Cron - weeklySummary
 
 on:
-  workflow_dispatch:
   # "Scheduled workflows run on the latest commit on the default or base branch."
   # — https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows#schedule
-  # schedule:
-  # Runs “At 08:00 on Monday.” (see https://crontab.guru)
-  # - cron: "0 8 * * 1"
+  schedule:
+    # Runs “At 08:00 on Monday.” (see https://crontab.guru)
+    - cron: "0 8 * * 1"
 jobs:
   cron-weeklySummary:
     env:
@@ -17,7 +16,7 @@ jobs:
       - name: cURL request
         if: ${{ env.APP_URL && env.CRON_SECRET }}
         run: |
-          curl ${{ env.APP_URL }}/api/cron/weekly-summary \
+          curl ${{ env.APP_URL }}/api/cron/weekly_summary \
             -X POST \
             -H 'content-type: application/json' \
             -H 'x-api-key: ${{ env.CRON_SECRET }}' \

.github/workflows/ecs-deployment.yml

@@ -0,0 +1,129 @@
+name: ECS
+
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+on:
+  push:
+    branches: [main]
+  workflow_dispatch: # Add manual trigger support
+
+env:
+  REGISTRY: ghcr.io
+  IMAGE_NAME: formbricks/formbricks-experimental
+  DATABASE_URL: "postgresql://postgres:postgres@localhost:5432/formbricks?schema=public"
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write
+      id-token: write  # Only necessary for sigstore/fulcio outside PRs
+
+    steps:
+      - name: Generate Secrets
+        run: |
+          echo "NEXTAUTH_SECRET=$(openssl rand -hex 32)" >> $GITHUB_ENV
+          echo "ENCRYPTION_KEY=$(openssl rand -hex 32)" >> $GITHUB_ENV
+
+      - name: Checkout repository
+        uses: actions/checkout@v3
+
+      - name: Set up Depot CLI
+        uses: depot/setup-action@v1
+
+      # https://github.com/sigstore/cosign-installer
+      - name: Install cosign
+        uses: sigstore/cosign-installer@6e04d228eb30da1757ee4e1dd75a0ec73a653e06 #v3.1.1
+        with:
+          cosign-release: "v2.1.1"
+
+      # https://github.com/docker/login-action
+      - name: Log into registry
+        uses: docker/login-action@v3
+        with:
+          registry: ${{ env.REGISTRY }}
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      # Extract metadata (tags, labels) for Docker
+      # https://github.com/docker/metadata-action
+      - name: Extract Docker metadata
+        id: meta
+        uses: docker/metadata-action@v5 # v5.0.0
+        with:
+          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
+          tags: |
+            type=sha,format=long
+
+      # Build and push Docker image with Buildx
+      # https://github.com/docker/build-push-action
+      - name: Build and push Docker image
+        id: build-and-push
+        uses: depot/build-push-action@v1
+        env:
+          NEXT_PUBLIC_SENTRY_DSN: ${{ secrets.NEXT_PUBLIC_SENTRY_DSN }}
+        with:
+          project: tw0fqmsx3c
+          token: ${{ secrets.DEPOT_PROJECT_TOKEN }}
+          context: .
+          file: ./apps/web/Dockerfile
+          platforms: linux/amd64,linux/arm64
+          push: true
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
+          cache-from: type=gha
+          cache-to: type=gha,mode=max
+          build-args: |
+            NEXTAUTH_SECRET=${{ env.NEXTAUTH_SECRET }}
+            DATABASE_URL=${{ env.DATABASE_URL }}
+            ENCRYPTION_KEY=${{ env.ENCRYPTION_KEY }}
+            NEXT_PUBLIC_SENTRY_DSN=${{ env.NEXT_PUBLIC_SENTRY_DSN }}
+
+      - name: Sign the images with GitHub OIDC Token
+        env:
+          DIGEST: ${{ steps.build-and-push.outputs.digest }}
+          TAGS: ${{ steps.meta.outputs.tags }}
+        run: |
+          images=""
+          for tag in ${TAGS}; do
+            images+="${tag}@${DIGEST} "
+          done
+          cosign sign --yes ${images}
+    
+    outputs:
+      image_tag_sha: ${{ steps.meta.outputs.tags }}
+  
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - name: Configure AWS credentials
+        uses: aws-actions/configure-aws-credentials@v1
+        with:
+          aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
+          aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+          aws-region: ${{ secrets.AWS_REGION }}
+          
+      - name: Download task definition
+        run: |
+          aws ecs describe-task-definition --task-definition prod-webapp-ecs-service --query taskDefinition > task-definition.json
+
+      - name: Fill in the new image ID in the Amazon ECS task definition
+        id: task-def
+        uses: aws-actions/amazon-ecs-render-task-definition@v1
+        with:
+          task-definition: task-definition.json
+          container-name: prod-webapp-container
+          image: ${{ needs.build.outputs.image_tag_sha }}
+
+      - name: Deploy Amazon ECS task definition
+        uses: aws-actions/amazon-ecs-deploy-task-definition@v1
+        with:
+          task-definition: ${{ steps.task-def.outputs.task-definition }}
+          service: prod-webapp-ecs-service
+          cluster: prod-core-infra-ecs-cluster
+          wait-for-service-stability: true

.github/workflows/kamal-deploy.yml

@@ -1,131 +0,0 @@
-name: Kamal Deploy
-concurrency:
-  group: deploy-to-kamal
-  cancel-in-progress: false
-
-on:
-  workflow_dispatch:
-  push:
-    branches:
-      - main
-
-jobs:
-  Deploy:
-    runs-on: ubuntu-latest
-    environment: production
-    env:
-      DOCKER_BUILDKIT: 1
-      IS_FORMBRICKS_CLOUD: ${{ vars.IS_FORMBRICKS_CLOUD }}
-      WEBAPP_URL: ${{ vars.WEBAPP_URL }}
-      MIGRATE_DATABASE_URL: ${{ secrets.MIGRATE_DATABASE_URL }}
-      NEXTAUTH_URL: ${{ vars.NEXTAUTH_URL }}
-      DATABASE_URL: ${{ secrets.DATABASE_URL }}
-      NEXTAUTH_SECRET: ${{ secrets.NEXTAUTH_SECRET }}
-      ENCRYPTION_KEY: ${{ secrets.ENCRYPTION_KEY }}
-      SHORT_URL_BASE: ${{ vars.SHORT_URL_BASE }}
-      MAIL_FROM: ${{ secrets.MAIL_FROM }}
-      SMTP_HOST: ${{ secrets.SMTP_HOST }}
-      SMTP_PORT: ${{ secrets.SMTP_PORT }}
-      SMTP_USER: ${{ secrets.SMTP_USER }}
-      SMTP_PASSWORD: ${{ secrets.SMTP_PASSWORD }}
-      PRIVACY_URL: ${{ vars.PRIVACY_URL }}
-      TERMS_URL: ${{ vars.TERMS_URL }}
-      IMPRINT_URL: ${{ vars.IMPRINT_URL }}
-      GITHUB_ID: ${{ secrets.FB_GITHUB_ID }}
-      GITHUB_SECRET: ${{ secrets.FB_GITHUB_SECRET }}
-      GOOGLE_CLIENT_ID: ${{ secrets.GOOGLE_CLIENT_ID }}
-      GOOGLE_CLIENT_SECRET: ${{ secrets.GOOGLE_CLIENT_SECRET }}
-      AZUREAD_CLIENT_ID: ${{ secrets.AZUREAD_CLIENT_ID }}
-      AZUREAD_CLIENT_SECRET: ${{ secrets.AZUREAD_CLIENT_SECRET }}
-      AZUREAD_TENANT_ID: ${{ secrets.AZUREAD_TENANT_ID }}
-      OIDC_CLIENT_ID: ${{ secrets.OIDC_CLIENT_ID }}
-      OIDC_CLIENT_SECRET: ${{ secrets.OIDC_CLIENT_SECRET }}
-      OIDC_ISSUER: ${{ secrets.OIDC_ISSUER }}
-      OIDC_DISPLAY_NAME: ${{ secrets.OIDC_DISPLAY_NAME }}
-      OIDC_SIGNING_ALGORITHM: ${{ secrets.OIDC_SIGNING_ALGORITHM }}
-      CRON_SECRET: ${{ secrets.CRON_SECRET }}
-      ASSET_PREFIX_URL: ${{ vars.ASSET_PREFIX_URL }}
-      NOTION_OAUTH_CLIENT_ID: ${{ secrets.NOTION_OAUTH_CLIENT_ID }}
-      NOTION_OAUTH_CLIENT_SECRET: ${{ secrets.NOTION_OAUTH_CLIENT_SECRET }}
-      SLACK_CLIENT_ID: ${{ secrets.SLACK_CLIENT_ID }}
-      SLACK_CLIENT_SECRET: ${{ secrets.SLACK_CLIENT_SECRET }}
-      STRIPE_SECRET_KEY: ${{ secrets.STRIPE_SECRET_KEY }}
-      STRIPE_WEBHOOK_SECRET: ${{ secrets.STRIPE_WEBHOOK_SECRET }}
-      GOOGLE_SHEETS_CLIENT_ID: ${{ secrets.GOOGLE_SHEETS_CLIENT_ID }}
-      GOOGLE_SHEETS_CLIENT_SECRET: ${{ secrets.GOOGLE_SHEETS_CLIENT_SECRET }}
-      GOOGLE_SHEETS_REDIRECT_URL: ${{ secrets.GOOGLE_SHEETS_REDIRECT_URL }}
-      AIRTABLE_CLIENT_ID: ${{ secrets.AIRTABLE_CLIENT_ID }}
-      ENTERPRISE_LICENSE_KEY: ${{ secrets.ENTERPRISE_LICENSE_KEY }}
-      DEFAULT_TEAM_ID: ${{ vars.DEFAULT_TEAM_ID }}
-      ONBOARDING_DISABLED: ${{ vars.ONBOARDING_DISABLED }}
-      CUSTOMER_IO_API_KEY: ${{ secrets.CUSTOMER_IO_API_KEY }}
-      CUSTOMER_IO_SITE_ID: ${{ secrets.CUSTOMER_IO_SITE_ID }}
-      NEXT_PUBLIC_POSTHOG_API_KEY: ${{ vars.NEXT_PUBLIC_POSTHOG_API_KEY }}
-      NEXT_PUBLIC_POSTHOG_API_HOST: ${{ vars.NEXT_PUBLIC_POSTHOG_API_HOST }}
-      NEXT_PUBLIC_FORMBRICKS_API_HOST: ${{ vars.NEXT_PUBLIC_FORMBRICKS_API_HOST }}
-      NEXT_PUBLIC_FORMBRICKS_ENVIRONMENT_ID: ${{ vars.NEXT_PUBLIC_FORMBRICKS_ENVIRONMENT_ID }}
-      NEXT_PUBLIC_FORMBRICKS_ONBOARDING_SURVEY_ID: ${{ vars.NEXT_PUBLIC_FORMBRICKS_ONBOARDING_SURVEY_ID }}
-      NEXT_PUBLIC_SENTRY_DSN: ${{ vars.NEXT_PUBLIC_SENTRY_DSN }}
-      SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
-      NODE_ENV: production
-      CLOUDFLARE_EMAIL: ${{ secrets.CLOUDFLARE_EMAIL }}
-      CLOUDFLARE_DNS_API_TOKEN: ${{ secrets.CLOUDFLARE_DNS_API_TOKEN }}
-      S3_ACCESS_KEY: ${{ secrets.S3_ACCESS_KEY }}
-      S3_SECRET_KEY: ${{ secrets.S3_SECRET_KEY }}
-      S3_REGION: ${{ vars.S3_REGION }}
-      S3_BUCKET_NAME: ${{ vars.S3_BUCKET_NAME }}
-      OPENTELEMETRY_LISTENER_URL: ${{ vars.OPENTELEMETRY_LISTENER_URL }}
-      RATE_LIMITING_DISABLED: ${{ vars.RATE_LIMITING_DISABLED }}
-      KAMAL_REGISTRY_PASSWORD: ${{ secrets.KAMAL_REGISTRY_PASSWORD }}
-      DB_HOST: ${{ secrets.DB_HOST }}
-      DB_USER: ${{ secrets.DB_USER }}
-      DB_PASSWORD: ${{ secrets.DB_PASSWORD }}
-      DB_NAME: ${{ secrets.DB_NAME }}
-      REDIS_URL: ${{ secrets.REDIS_URL }}
-
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v3
-
-      - name: Set up Ruby
-        uses: ruby/setup-ruby@v1
-        with:
-          ruby-version: 3.3.0
-          bundler-cache: true
-
-      - name: Install dependencies
-        run: |
-          gem install kamal
-
-      - uses: webfactory/ssh-agent@v0.9.0
-        with:
-          ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY }}
-
-      - name: Set up Docker Buildx
-        id: buildx
-        uses: docker/setup-buildx-action@v2
-
-      - name: Create builder
-        run: docker buildx create --use --name formbricks-gh-actions-builder
-        if: steps.buildx.outputs.should_create_builder == 'true'
-
-      - name: Push env variables to Kamal
-        run: |
-          kamal() { command kamal "$@" -c kamal/deploy.yml; }
-          kamal env push
-
-      - name: Run deploy command
-        run: |
-          kamal() { command kamal "$@" -c kamal/deploy.yml; }
-          set +e
-          DEPLOY_OUTPUT=$(kamal deploy 2>&1)
-          DEPLOY_EXIT_CODE=$?
-          echo "$DEPLOY_OUTPUT"
-          if [[ "$DEPLOY_OUTPUT" == *"container not unhealthy (healthy)"* ]]; then
-            echo "Deployment reported healthy container. Considering as success."
-            kamal lock release
-            exit 0
-          else
-            exit $DEPLOY_EXIT_CODE
-          fi
-        shell: bash

.github/workflows/kamal-setup.yml

@@ -1,128 +0,0 @@
-name: Kamal Setup
-concurrency:
-  group: setup-kamal
-  cancel-in-progress: false
-
-on:
-  workflow_dispatch: # Only to be triggered when accessories are updated
-
-jobs:
-  Setup:
-    runs-on: ubuntu-latest
-    environment: production
-    env:
-      DOCKER_BUILDKIT: 1
-      IS_FORMBRICKS_CLOUD: ${{ vars.IS_FORMBRICKS_CLOUD }}
-      WEBAPP_URL: ${{ vars.WEBAPP_URL }}
-      NEXTAUTH_URL: ${{ vars.NEXTAUTH_URL }}
-      DATABASE_URL: ${{ secrets.DATABASE_URL }}
-      MIGRATE_DATABASE_URL: ${{ secrets.MIGRATE_DATABASE_URL }}
-      NEXTAUTH_SECRET: ${{ secrets.NEXTAUTH_SECRET }}
-      ENCRYPTION_KEY: ${{ secrets.ENCRYPTION_KEY }}
-      SHORT_URL_BASE: ${{ vars.SHORT_URL_BASE }}
-      MAIL_FROM: ${{ secrets.MAIL_FROM }}
-      SMTP_HOST: ${{ secrets.SMTP_HOST }}
-      SMTP_PORT: ${{ secrets.SMTP_PORT }}
-      SMTP_USER: ${{ secrets.SMTP_USER }}
-      SMTP_PASSWORD: ${{ secrets.SMTP_PASSWORD }}
-      PRIVACY_URL: ${{ vars.PRIVACY_URL }}
-      TERMS_URL: ${{ vars.TERMS_URL }}
-      IMPRINT_URL: ${{ vars.IMPRINT_URL }}
-      GITHUB_ID: ${{ secrets.FB_GITHUB_ID }}
-      GITHUB_SECRET: ${{ secrets.FB_GITHUB_SECRET }}
-      GOOGLE_CLIENT_ID: ${{ secrets.GOOGLE_CLIENT_ID }}
-      GOOGLE_CLIENT_SECRET: ${{ secrets.GOOGLE_CLIENT_SECRET }}
-      AZUREAD_CLIENT_ID: ${{ secrets.AZUREAD_CLIENT_ID }}
-      AZUREAD_CLIENT_SECRET: ${{ secrets.AZUREAD_CLIENT_SECRET }}
-      AZUREAD_TENANT_ID: ${{ secrets.AZUREAD_TENANT_ID }}
-      OIDC_CLIENT_ID: ${{ secrets.OIDC_CLIENT_ID }}
-      OIDC_CLIENT_SECRET: ${{ secrets.OIDC_CLIENT_SECRET }}
-      OIDC_ISSUER: ${{ secrets.OIDC_ISSUER }}
-      OIDC_DISPLAY_NAME: ${{ secrets.OIDC_DISPLAY_NAME }}
-      OIDC_SIGNING_ALGORITHM: ${{ secrets.OIDC_SIGNING_ALGORITHM }}
-      CRON_SECRET: ${{ secrets.CRON_SECRET }}
-      ASSET_PREFIX_URL: ${{ vars.ASSET_PREFIX_URL }}
-      NOTION_OAUTH_CLIENT_ID: ${{ secrets.NOTION_OAUTH_CLIENT_ID }}
-      NOTION_OAUTH_CLIENT_SECRET: ${{ secrets.NOTION_OAUTH_CLIENT_SECRET }}
-      SLACK_CLIENT_ID: ${{ secrets.SLACK_CLIENT_ID }}
-      SLACK_CLIENT_SECRET: ${{ secrets.SLACK_CLIENT_SECRET }}
-      STRIPE_SECRET_KEY: ${{ secrets.STRIPE_SECRET_KEY }}
-      STRIPE_WEBHOOK_SECRET: ${{ secrets.STRIPE_WEBHOOK_SECRET }}
-      GOOGLE_SHEETS_CLIENT_ID: ${{ secrets.GOOGLE_SHEETS_CLIENT_ID }}
-      GOOGLE_SHEETS_CLIENT_SECRET: ${{ secrets.GOOGLE_SHEETS_CLIENT_SECRET }}
-      GOOGLE_SHEETS_REDIRECT_URL: ${{ secrets.GOOGLE_SHEETS_REDIRECT_URL }}
-      AIRTABLE_CLIENT_ID: ${{ secrets.AIRTABLE_CLIENT_ID }}
-      ENTERPRISE_LICENSE_KEY: ${{ secrets.ENTERPRISE_LICENSE_KEY }}
-      DEFAULT_TEAM_ID: ${{ vars.DEFAULT_TEAM_ID }}
-      ONBOARDING_DISABLED: ${{ vars.ONBOARDING_DISABLED }}
-      CUSTOMER_IO_API_KEY: ${{ secrets.CUSTOMER_IO_API_KEY }}
-      CUSTOMER_IO_SITE_ID: ${{ secrets.CUSTOMER_IO_SITE_ID }}
-      NEXT_PUBLIC_POSTHOG_API_KEY: ${{ vars.NEXT_PUBLIC_POSTHOG_API_KEY }}
-      NEXT_PUBLIC_POSTHOG_API_HOST: ${{ vars.NEXT_PUBLIC_POSTHOG_API_HOST }}
-      NEXT_PUBLIC_FORMBRICKS_API_HOST: ${{ vars.NEXT_PUBLIC_FORMBRICKS_API_HOST }}
-      NEXT_PUBLIC_FORMBRICKS_ENVIRONMENT_ID: ${{ vars.NEXT_PUBLIC_FORMBRICKS_ENVIRONMENT_ID }}
-      NEXT_PUBLIC_FORMBRICKS_ONBOARDING_SURVEY_ID: ${{ vars.NEXT_PUBLIC_FORMBRICKS_ONBOARDING_SURVEY_ID }}
-      NEXT_PUBLIC_SENTRY_DSN: ${{ vars.NEXT_PUBLIC_SENTRY_DSN }}
-      SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
-      NODE_ENV: production
-      CLOUDFLARE_EMAIL: ${{ secrets.CLOUDFLARE_EMAIL }}
-      CLOUDFLARE_DNS_API_TOKEN: ${{ secrets.CLOUDFLARE_DNS_API_TOKEN }}
-      S3_ACCESS_KEY: ${{ secrets.S3_ACCESS_KEY }}
-      S3_SECRET_KEY: ${{ secrets.S3_SECRET_KEY }}
-      S3_REGION: ${{ vars.S3_REGION }}
-      S3_BUCKET_NAME: ${{ vars.S3_BUCKET_NAME }}
-      OPENTELEMETRY_LISTENER_URL: ${{ vars.OPENTELEMETRY_LISTENER_URL }}
-      RATE_LIMITING_DISABLED: ${{ vars.RATE_LIMITING_DISABLED }}
-      KAMAL_REGISTRY_PASSWORD: ${{ secrets.KAMAL_REGISTRY_PASSWORD }}
-      DB_HOST: ${{ secrets.DB_HOST }}
-      DB_USER: ${{ secrets.DB_USER }}
-      DB_PASSWORD: ${{ secrets.DB_PASSWORD }}
-      DB_NAME: ${{ secrets.DB_NAME }}
-      REDIS_URL: ${{ secrets.REDIS_URL }}
-
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v3
-
-      - name: Set up Ruby
-        uses: ruby/setup-ruby@v1
-        with:
-          ruby-version: 3.3.0
-          bundler-cache: true
-
-      - name: Install dependencies
-        run: |
-          gem install kamal
-
-      - uses: webfactory/ssh-agent@v0.9.0
-        with:
-          ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY }}
-
-      - name: Set up Docker Buildx
-        id: buildx
-        uses: docker/setup-buildx-action@v2
-
-      - name: Create builder
-        run: docker buildx create --use --name formbricks-gh-actions-builder
-        if: steps.buildx.outputs.should_create_builder == 'true'
-
-      - name: Push env variables to Kamal
-        run: |
-          kamal() { command kamal "$@" -c kamal/deploy.yml; }
-          kamal env push
-
-      - name: Run setup command
-        run: |
-          kamal() { command kamal "$@" -c kamal/deploy.yml; }
-          set +e
-          DEPLOY_OUTPUT=$(kamal setup 2>&1)
-          DEPLOY_EXIT_CODE=$?
-          echo "$DEPLOY_OUTPUT"
-          if [[ "$DEPLOY_OUTPUT" == *"container not unhealthy (healthy)"* ]]; then
-            echo "Deployment reported healthy container. Considering as success."
-            kamal lock release
-            exit 0
-          else
-            exit $DEPLOY_EXIT_CODE
-          fi
-        shell: bash

.github/workflows/pr.yml

@@ -1,7 +1,7 @@
 name: PR Update
 
 on:
-  pull_request:
+  pull_request_target:
     branches:
       - main
   merge_group:
@@ -30,7 +30,7 @@ jobs:
               - "!(**.md|.github/CODEOWNERS)"
 
   test:
-    name: Run Unit Tests
+    name: Run Tests
     needs: [changes]
     if: ${{ needs.changes.outputs.has-files-requiring-all-checks == 'true' }}
     uses: ./.github/workflows/test.yml
@@ -58,7 +58,6 @@ jobs:
     secrets: inherit
 
   required:
-    name: PR Check Summary
     needs: [lint, test, build, e2e-test]
     if: always()
     runs-on: ubuntu-latest

.github/workflows/release-docker-github.yml

@@ -31,6 +31,16 @@ jobs:
       id-token: write
 
     steps:
+      - name: Generate Random NEXTAUTH_SECRET
+        run: |
+          SECRET=$(openssl rand -hex 32)
+          echo "NEXTAUTH_SECRET=$SECRET" >> $GITHUB_ENV
+
+      - name: Generate Random ENCRYPTION_KEY
+        run: |
+          SECRET=$(openssl rand -hex 32)
+          echo "ENCRYPTION_KEY=$SECRET" >> $GITHUB_ENV
+
       - name: Checkout repository
         uses: actions/checkout@v3
 
@@ -79,6 +89,10 @@ jobs:
           labels: ${{ steps.meta.outputs.labels }}
           cache-from: type=gha
           cache-to: type=gha,mode=max
+          build-args: |
+            NEXTAUTH_SECRET=${{ env.NEXTAUTH_SECRET }}
+            DATABASE_URL=${{ env.DATABASE_URL }}
+            ENCRYPTION_KEY=${{ env.ENCRYPTION_KEY }}
 
       # Sign the resulting Docker image digest except on PRs.
       # This will only write to the public Rekor transparency log when the Docker

.github/workflows/release-docker.yml

@@ -14,6 +14,16 @@ jobs:
       TURBO_TEAM: ${{ secrets.TURBO_TEAM }}
       DATABASE_URL: "postgresql://postgres:postgres@localhost:5432/formbricks?schema=public"
     steps:
+      - name: Generate Random NEXTAUTH_SECRET
+        run: |
+          SECRET=$(openssl rand -hex 32)
+          echo "NEXTAUTH_SECRET=$SECRET" >> $GITHUB_ENV
+
+      - name: Generate Random ENCRYPTION_KEY
+        run: |
+          SECRET=$(openssl rand -hex 32)
+          echo "ENCRYPTION_KEY=$SECRET" >> $GITHUB_ENV
+
       - name: Checkout Repo
         uses: actions/checkout@v2
 
@@ -42,3 +52,7 @@ jobs:
           tags: |
             ${{ secrets.DOCKER_USERNAME }}/formbricks:${{ env.RELEASE_TAG }}
             ${{ secrets.DOCKER_USERNAME }}/formbricks:latest
+          build-args: |
+            NEXTAUTH_SECRET=${{ env.NEXTAUTH_SECRET }}
+            DATABASE_URL=${{ env.DATABASE_URL }}
+            ENCRYPTION_KEY=${{ env.ENCRYPTION_KEY }}

.github/workflows/test.yml

@@ -3,7 +3,7 @@ on:
   workflow_call:
 jobs:
   build:
-    name: Unit Tests
+    name: Tests
     runs-on: ubuntu-latest
     timeout-minutes: 15
 

.gitignore

@@ -54,7 +54,3 @@ Zone.Identifier
 
 # uploads
 packages/lib/uploads
-
-# Vite Timestamps
-vite.config.*.timestamp-*
-

.kamal/hooks/post-deploy.sample

@@ -1,14 +0,0 @@
-#!/bin/sh
-
-# A sample post-deploy hook
-#
-# These environment variables are available:
-# KAMAL_RECORDED_AT
-# KAMAL_PERFORMER
-# KAMAL_VERSION
-# KAMAL_HOSTS
-# KAMAL_ROLE (if set)
-# KAMAL_DESTINATION (if set)
-# KAMAL_RUNTIME
-
-echo "$KAMAL_PERFORMER deployed $KAMAL_VERSION to $KAMAL_DESTINATION in $KAMAL_RUNTIME seconds"

.kamal/hooks/post-traefik-reboot.sample

@@ -1,3 +0,0 @@
-#!/bin/sh
-
-echo "Rebooted Traefik on $KAMAL_HOSTS"

.kamal/hooks/pre-build.sample

@@ -1,51 +0,0 @@
-#!/bin/sh
-
-# A sample pre-build hook
-#
-# Checks:
-# 1. We have a clean checkout
-# 2. A remote is configured
-# 3. The branch has been pushed to the remote
-# 4. The version we are deploying matches the remote
-#
-# These environment variables are available:
-# KAMAL_RECORDED_AT
-# KAMAL_PERFORMER
-# KAMAL_VERSION
-# KAMAL_HOSTS
-# KAMAL_ROLE (if set)
-# KAMAL_DESTINATION (if set)
-
-if [ -n "$(git status --porcelain)" ]; then
-  echo "Git checkout is not clean, aborting..." >&2
-  git status --porcelain >&2
-  exit 1
-fi
-
-first_remote=$(git remote)
-
-if [ -z "$first_remote" ]; then
-  echo "No git remote set, aborting..." >&2
-  exit 1
-fi
-
-current_branch=$(git branch --show-current)
-
-if [ -z "$current_branch" ]; then
-  echo "Not on a git branch, aborting..." >&2
-  exit 1
-fi
-
-remote_head=$(git ls-remote $first_remote --tags $current_branch | cut -f1)
-
-if [ -z "$remote_head" ]; then
-  echo "Branch not pushed to remote, aborting..." >&2
-  exit 1
-fi
-
-if [ "$KAMAL_VERSION" != "$remote_head" ]; then
-  echo "Version ($KAMAL_VERSION) does not match remote HEAD ($remote_head), aborting..." >&2
-  exit 1
-fi
-
-exit 0

.kamal/hooks/pre-connect.sample

@@ -1,47 +0,0 @@
-#!/usr/bin/env ruby
-
-# A sample pre-connect check
-#
-# Warms DNS before connecting to hosts in parallel
-#
-# These environment variables are available:
-# KAMAL_RECORDED_AT
-# KAMAL_PERFORMER
-# KAMAL_VERSION
-# KAMAL_HOSTS
-# KAMAL_ROLE (if set)
-# KAMAL_DESTINATION (if set)
-# KAMAL_RUNTIME
-
-hosts = ENV["KAMAL_HOSTS"].split(",")
-results = nil
-max = 3
-
-elapsed = Benchmark.realtime do
-  results = hosts.map do |host|
-    Thread.new do
-      tries = 1
-
-      begin
-        Socket.getaddrinfo(host, 0, Socket::AF_UNSPEC, Socket::SOCK_STREAM, nil, Socket::AI_CANONNAME)
-      rescue SocketError
-        if tries < max
-          puts "Retrying DNS warmup: #{host}"
-          tries += 1
-          sleep rand
-          retry
-        else
-          puts "DNS warmup failed: #{host}"
-          host
-        end
-      end
-
-      tries
-    end
-  end.map(&:value)
-end
-
-retries = results.sum - hosts.size
-nopes = results.count { |r| r == max }
-
-puts "Prewarmed %d DNS lookups in %.2f sec: %d retries, %d failures" % [ hosts.size, elapsed, retries, nopes ]

.kamal/hooks/pre-deploy.sample

@@ -1,109 +0,0 @@
-#!/usr/bin/env ruby
-
-# A sample pre-deploy hook
-#
-# Checks the Github status of the build, waiting for a pending build to complete for up to 720 seconds.
-#
-# Fails unless the combined status is "success"
-#
-# These environment variables are available:
-# KAMAL_RECORDED_AT
-# KAMAL_PERFORMER
-# KAMAL_VERSION
-# KAMAL_HOSTS
-# KAMAL_COMMAND
-# KAMAL_SUBCOMMAND
-# KAMAL_ROLE (if set)
-# KAMAL_DESTINATION (if set)
-
-# Only check the build status for production deployments
-if ENV["KAMAL_COMMAND"] == "rollback" || ENV["KAMAL_DESTINATION"] != "production"
-  exit 0
-end
-
-require "bundler/inline"
-
-# true = install gems so this is fast on repeat invocations
-gemfile(true, quiet: true) do
-  source "https://rubygems.org"
-
-  gem "octokit"
-  gem "faraday-retry"
-end
-
-MAX_ATTEMPTS = 72
-ATTEMPTS_GAP = 10
-
-def exit_with_error(message)
-  $stderr.puts message
-  exit 1
-end
-
-class GithubStatusChecks
-  attr_reader :remote_url, :git_sha, :github_client, :combined_status
-
-  def initialize
-    @remote_url = `git config --get remote.origin.url`.strip.delete_prefix("https://github.com/")
-    @git_sha = `git rev-parse HEAD`.strip
-    @github_client = Octokit::Client.new(access_token: ENV["GITHUB_TOKEN"])
-    refresh!
-  end
-
-  def refresh!
-    @combined_status = github_client.combined_status(remote_url, git_sha)
-  end
-
-  def state
-    combined_status[:state]
-  end
-
-  def first_status_url
-    first_status = combined_status[:statuses].find { |status| status[:state] == state }
-    first_status && first_status[:target_url]
-  end
-
-  def complete_count
-    combined_status[:statuses].count { |status| status[:state] != "pending"}
-  end
-
-  def total_count
-    combined_status[:statuses].count
-  end
-
-  def current_status
-    if total_count > 0
-      "Completed #{complete_count}/#{total_count} checks, see #{first_status_url} ..."
-    else
-      "Build not started..."
-    end
-  end
-end
-
-
-$stdout.sync = true
-
-puts "Checking build status..."
-attempts = 0
-checks = GithubStatusChecks.new
-
-begin
-  loop do
-    case checks.state
-    when "success"
-      puts "Checks passed, see #{checks.first_status_url}"
-      exit 0
-    when "failure"
-      exit_with_error "Checks failed, see #{checks.first_status_url}"
-    when "pending"
-      attempts += 1
-    end
-
-    exit_with_error "Checks are still pending, gave up after #{MAX_ATTEMPTS * ATTEMPTS_GAP} seconds" if attempts == MAX_ATTEMPTS
-
-    puts checks.current_status
-    sleep(ATTEMPTS_GAP)
-    checks.refresh!
-  end
-rescue Octokit::NotFound
-  exit_with_error "Build status could not be found"
-end

.kamal/hooks/pre-traefik-reboot.sample

@@ -1,3 +0,0 @@
-#!/bin/sh
-
-echo "Rebooting Traefik on $KAMAL_HOSTS..."

README.md

@@ -138,12 +138,6 @@ You can deploy Formbricks on [Railway](https://railway.app) using the button bel
 
 [![Deploy on Railway](https://railway.app/button.svg)](https://railway.app/new/template/PPDzCd)
 
-##### RepoCloud
-
-Or you can also deploy Formbricks on [RepoCloud](https://repocloud.io) using the button below.
-
-[![Deploy on RepoCloud](https://d16t0pc4846x52.cloudfront.net/deploy.png)](https://repocloud.io/details/?app_id=254)
-
 <a id="development"></a>
 
 ## 👨‍💻 Development

apps/demo/components/Sidebar.tsx

@@ -1,28 +1,27 @@
+import { classNames } from "@/lib/utils";
 import {
   ClockIcon,
   CogIcon,
   CreditCardIcon,
-  FileBarChartIcon,
-  HelpCircleIcon,
+  DocumentChartBarIcon,
   HomeIcon,
+  QuestionMarkCircleIcon,
   ScaleIcon,
   ShieldCheckIcon,
-  UsersIcon,
-} from "lucide-react";
-
-import { classNames } from "../lib/utils";
+  UserGroupIcon,
+} from "@heroicons/react/24/outline";
 
 const navigation = [
   { name: "Home", href: "#", icon: HomeIcon, current: true },
   { name: "History", href: "#", icon: ClockIcon, current: false },
   { name: "Balances", href: "#", icon: ScaleIcon, current: false },
   { name: "Cards", href: "#", icon: CreditCardIcon, current: false },
-  { name: "Recipients", href: "#", icon: UsersIcon, current: false },
-  { name: "Reports", href: "#", icon: FileBarChartIcon, current: false },
+  { name: "Recipients", href: "#", icon: UserGroupIcon, current: false },
+  { name: "Reports", href: "#", icon: DocumentChartBarIcon, current: false },
 ];
 const secondaryNavigation = [
   { name: "Settings", href: "#", icon: CogIcon },
-  { name: "Help", href: "#", icon: HelpCircleIcon },
+  { name: "Help", href: "#", icon: QuestionMarkCircleIcon },
   { name: "Privacy", href: "#", icon: ShieldCheckIcon },
 ];
 

apps/demo/package.json

@@ -12,13 +12,12 @@
   },
   "dependencies": {
     "@formbricks/js": "workspace:*",
-    "lucide-react": "^0.368.0",
-    "next": "14.2.1",
+    "@heroicons/react": "^2.1.1",
+    "next": "14.1.1",
     "react": "18.2.0",
     "react-dom": "18.2.0"
   },
   "devDependencies": {
-    "eslint-config-formbricks": "workspace:*",
-    "@formbricks/tsconfig": "workspace:*"
+    "eslint-config-formbricks": "workspace:*"
   }
 }

apps/demo/pages/app/index.tsx

@@ -1,9 +1,8 @@
-import { EarthIcon } from "lucide-react";
 import Image from "next/image";
 import { useRouter } from "next/router";
 import { useEffect, useState } from "react";
 
-import formbricksApp from "@formbricks/js/app";
+import formbricks from "@formbricks/js";
 
 import fbsetup from "../../public/fb-setup.png";
 
@@ -22,33 +21,22 @@ export default function AppPage({}) {
   }, [darkMode]);
 
   useEffect(() => {
-    // enable Formbricks debug mode by adding formbricksDebug=true GET parameter
-    const addFormbricksDebugParam = () => {
-      const urlParams = new URLSearchParams(window.location.search);
-      if (!urlParams.has("formbricksDebug")) {
-        urlParams.set("formbricksDebug", "true");
-        const newUrl = `${window.location.pathname}?${urlParams.toString()}`;
-        window.history.replaceState({}, "", newUrl);
-      }
-    };
-
-    addFormbricksDebugParam();
-
     if (process.env.NEXT_PUBLIC_FORMBRICKS_ENVIRONMENT_ID && process.env.NEXT_PUBLIC_FORMBRICKS_API_HOST) {
-      const userId = "THIS-IS-A-VERY-LONG-USER-ID-FOR-TESTING";
-      const userInitAttributes = { language: "de", "Init Attribute 1": "eight", "Init Attribute 2": "two" };
-
-      formbricksApp.init({
+      const isUserId = window.location.href.includes("userId=true");
+      const attributes = isUserId ? { "Init Attribute 1": "eight", "Init Attribute 2": "two" } : undefined;
+      const userId = isUserId ? "THIS-IS-A-VERY-LONG-USER-ID-FOR-TESTING" : undefined;
+      formbricks.init({
         environmentId: process.env.NEXT_PUBLIC_FORMBRICKS_ENVIRONMENT_ID,
         apiHost: process.env.NEXT_PUBLIC_FORMBRICKS_API_HOST,
         userId,
-        attributes: userInitAttributes,
+        attributes,
       });
+      window.formbricks = formbricks;
     }
 
     // Connect next.js router to Formbricks
     if (process.env.NEXT_PUBLIC_FORMBRICKS_ENVIRONMENT_ID && process.env.NEXT_PUBLIC_FORMBRICKS_API_HOST) {
-      const handleRouteChange = formbricksApp?.registerRouteChange;
+      const handleRouteChange = formbricks?.registerRouteChange;
       router.events.on("routeChangeComplete", handleRouteChange);
 
       return () => {
@@ -57,38 +45,18 @@ export default function AppPage({}) {
     }
   });
 
-  const removeFormbricksContainer = () => {
-    document.getElementById("formbricks-modal-container")?.remove();
-    document.getElementById("formbricks-app-container")?.remove();
-    localStorage.removeItem("formbricks-js-app");
-  };
-
   return (
     <div className="h-screen bg-white px-12 py-6 dark:bg-slate-800">
       <div className="flex flex-col justify-between md:flex-row">
-        <div className="flex items-center gap-2">
-          <button
-            className="rounded-lg bg-[#038178] p-2 text-white focus:outline-none focus:ring-2 focus:ring-slate-900 focus:ring-offset-1"
-            onClick={() => {
-              removeFormbricksContainer();
-              window.location.href = "/website";
-            }}>
-            <div className="flex items-center gap-2">
-              <EarthIcon className="h-10 w-10" />
-              <span>Website Demo</span>
-            </div>
-          </button>
-          <div>
-            <h1 className="text-2xl font-bold text-slate-900 dark:text-white">
-              Formbricks In-product Survey Demo App
-            </h1>
-            <p className="text-slate-700 dark:text-slate-300">
-              This app helps you test your app surveys. You can create and test user actions, create and
-              update user attributes, etc.
-            </p>
-          </div>
+        <div>
+          <h1 className="text-2xl font-bold text-slate-900 dark:text-white">
+            Formbricks In-product Survey Demo App
+          </h1>
+          <p className="text-slate-700 dark:text-slate-300">
+            This app helps you test your in-app surveys. You can create and test user actions, create and
+            update user attributes, etc.
+          </p>
         </div>
-
         <button
           className="mt-2 rounded-lg bg-slate-200 px-6 py-1 dark:bg-slate-700 dark:text-slate-100"
           onClick={() => setDarkMode(!darkMode)}>
@@ -101,7 +69,7 @@ export default function AppPage({}) {
           <div className="rounded-lg border border-slate-300 bg-slate-100 p-6 dark:border-slate-600 dark:bg-slate-900">
             <h3 className="text-lg font-semibold text-slate-900 dark:text-white">1. Setup .env</h3>
             <p className="text-slate-700 dark:text-slate-300">
-              Copy the environment ID of your Formbricks app to the env variable in /apps/demo/.env
+              Copy the environment ID of your Formbricks app to the env variable in demo/.env
             </p>
             <Image src={fbsetup} alt="fb setup" className="mt-4 rounded" priority />
 
@@ -112,7 +80,7 @@ export default function AppPage({}) {
                   {process.env.NEXT_PUBLIC_FORMBRICKS_ENVIRONMENT_ID}
                 </strong>
                 <span className="relative ml-2 flex h-3 w-3">
-                  <span className="absolute inline-flex h-full w-full animate-ping rounded-full bg-green-500 opacity-75"></span>
+                  <span className="absolute inline-flex h-full w-full animate-ping rounded-full bg-green-400 opacity-75"></span>
                   <span className="relative inline-flex h-3 w-3 rounded-full bg-green-500"></span>
                 </span>
               </div>
@@ -142,7 +110,7 @@ export default function AppPage({}) {
             <button
               className="my-4 rounded-lg bg-slate-500 px-6 py-3 text-white hover:bg-slate-700 dark:bg-slate-700 dark:hover:bg-slate-600"
               onClick={() => {
-                formbricksApp.reset();
+                formbricks.reset();
               }}>
               Reset
             </button>
@@ -157,7 +125,7 @@ export default function AppPage({}) {
               <button
                 className="mb-4 rounded-lg bg-slate-800 px-6 py-3 text-white hover:bg-slate-700 dark:bg-slate-700 dark:hover:bg-slate-600"
                 onClick={() => {
-                  formbricksApp.track("Code Action");
+                  formbricks.track("Code Action");
                 }}>
                 Code Action
               </button>
@@ -201,7 +169,7 @@ export default function AppPage({}) {
             <div>
               <button
                 onClick={() => {
-                  formbricksApp.setAttribute("Plan", "Free");
+                  formbricks.setAttribute("Plan", "Free");
                 }}
                 className="mb-4 rounded-lg bg-slate-800 px-6 py-3 text-white hover:bg-slate-700  dark:bg-slate-700 dark:hover:bg-slate-600">
                 Set Plan to &apos;Free&apos;
@@ -224,7 +192,7 @@ export default function AppPage({}) {
             <div>
               <button
                 onClick={() => {
-                  formbricksApp.setAttribute("Plan", "Paid");
+                  formbricks.setAttribute("Plan", "Paid");
                 }}
                 className="mb-4 rounded-lg bg-slate-800 px-6 py-3 text-white hover:bg-slate-700  dark:bg-slate-700 dark:hover:bg-slate-600">
                 Set Plan to &apos;Paid&apos;
@@ -247,7 +215,7 @@ export default function AppPage({}) {
             <div>
               <button
                 onClick={() => {
-                  formbricksApp.setEmail("test@web.com");
+                  formbricks.setEmail("test@web.com");
                 }}
                 className="mb-4 rounded-lg bg-slate-800 px-6 py-3 text-white hover:bg-slate-700  dark:bg-slate-700 dark:hover:bg-slate-600">
                 Set Email
@@ -266,6 +234,41 @@ export default function AppPage({}) {
               </p>
             </div>
           </div>
+          <div className="p-6">
+            {router.query.userId === "true" ? (
+              <div>
+                <button
+                  onClick={() => {
+                    window.location.href = "/app";
+                  }}
+                  className="mb-4 rounded-lg bg-slate-800 px-6 py-3 text-white hover:bg-slate-700  dark:bg-slate-700 dark:hover:bg-slate-600">
+                  Deactivate User Identification
+                </button>
+              </div>
+            ) : (
+              <div>
+                <button
+                  onClick={() => {
+                    window.location.href = "/app?userId=true";
+                  }}
+                  className="mb-4 rounded-lg bg-slate-800 px-6 py-3 text-white hover:bg-slate-700  dark:bg-slate-700 dark:hover:bg-slate-600">
+                  Activate User Identification
+                </button>
+              </div>
+            )}
+            <div>
+              <p className="text-xs text-slate-700 dark:text-slate-300">
+                This button activates/deactivates{" "}
+                <a
+                  href="https://formbricks.com/docs/attributes/identify-users"
+                  target="_blank"
+                  className="underline dark:text-blue-500">
+                  user identification
+                </a>{" "}
+                with the userId &apos;THIS-IS-A-VERY-LONG-USER-ID-FOR-TESTING&apos;
+              </p>
+            </div>
+          </div>
         </div>
       </div>
     </div>

apps/demo/pages/website/index.tsx

@@ -1,212 +0,0 @@
-import { MonitorIcon } from "lucide-react";
-import Image from "next/image";
-import { useRouter } from "next/router";
-import { useEffect, useState } from "react";
-
-import formbricksWebsite from "@formbricks/js/website";
-
-import fbsetup from "../../public/fb-setup.png";
-
-declare const window: any;
-
-export default function AppPage({}) {
-  const [darkMode, setDarkMode] = useState(false);
-  const router = useRouter();
-
-  useEffect(() => {
-    if (darkMode) {
-      document.body.classList.add("dark");
-    } else {
-      document.body.classList.remove("dark");
-    }
-  }, [darkMode]);
-
-  useEffect(() => {
-    // enable Formbricks debug mode by adding formbricksDebug=true GET parameter
-    const addFormbricksDebugParam = () => {
-      const urlParams = new URLSearchParams(window.location.search);
-      if (!urlParams.has("formbricksDebug")) {
-        urlParams.set("formbricksDebug", "true");
-        const newUrl = `${window.location.pathname}?${urlParams.toString()}`;
-        window.history.replaceState({}, "", newUrl);
-      }
-    };
-
-    addFormbricksDebugParam();
-
-    if (process.env.NEXT_PUBLIC_FORMBRICKS_ENVIRONMENT_ID && process.env.NEXT_PUBLIC_FORMBRICKS_API_HOST) {
-      const defaultAttributes = {
-        language: "de",
-      };
-
-      formbricksWebsite.init({
-        environmentId: process.env.NEXT_PUBLIC_FORMBRICKS_ENVIRONMENT_ID,
-        apiHost: process.env.NEXT_PUBLIC_FORMBRICKS_API_HOST,
-        attributes: defaultAttributes,
-      });
-    }
-
-    // Connect next.js router to Formbricks
-    if (process.env.NEXT_PUBLIC_FORMBRICKS_ENVIRONMENT_ID && process.env.NEXT_PUBLIC_FORMBRICKS_API_HOST) {
-      const handleRouteChange = formbricksWebsite?.registerRouteChange;
-      router.events.on("routeChangeComplete", handleRouteChange);
-
-      return () => {
-        router.events.off("routeChangeComplete", handleRouteChange);
-      };
-    }
-  });
-
-  const removeFormbricksContainer = () => {
-    document.getElementById("formbricks-modal-container")?.remove();
-    document.getElementById("formbricks-website-container")?.remove();
-    localStorage.removeItem("formbricks-js-website");
-  };
-
-  return (
-    <div className="h-screen bg-white px-12 py-6 dark:bg-slate-800">
-      <div className="flex flex-col items-center justify-between md:flex-row">
-        <div className="flex items-center gap-2">
-          <button
-            className="rounded-lg bg-[#038178] p-2 text-white focus:outline-none focus:ring-2 focus:ring-slate-900 focus:ring-offset-1"
-            onClick={() => {
-              removeFormbricksContainer();
-              window.location.href = "/app";
-            }}>
-            <div className="flex items-center gap-2">
-              <MonitorIcon className="h-10 w-10" />
-              <span>App Demo</span>
-            </div>
-          </button>
-          <div>
-            <h1 className="text-2xl font-bold text-slate-900 dark:text-white">
-              Formbricks Website Survey Demo App
-            </h1>
-            <p className="text-slate-700 dark:text-slate-300">
-              This app helps you test your app surveys. You can create and test user actions, create and
-              update user attributes, etc.
-            </p>
-          </div>
-        </div>
-
-        <button
-          className="mt-2 rounded-lg bg-slate-200 px-6 py-1 dark:bg-slate-700 dark:text-slate-100"
-          onClick={() => setDarkMode(!darkMode)}>
-          {darkMode ? "Toggle Light Mode" : "Toggle Dark Mode"}
-        </button>
-      </div>
-
-      <div className="my-4 grid grid-cols-1 gap-6 md:grid-cols-2">
-        <div>
-          <div className="rounded-lg border border-slate-300 bg-slate-100 p-6 dark:border-slate-600 dark:bg-slate-900">
-            <h3 className="text-lg font-semibold text-slate-900 dark:text-white">1. Setup .env</h3>
-            <p className="text-slate-700 dark:text-slate-300">
-              Copy the environment ID of your Formbricks app to the env variable in /apps/demo/.env
-            </p>
-            <Image src={fbsetup} alt="fb setup" className="mt-4 rounded" priority />
-
-            <div className="mt-4 flex-col items-start text-sm text-slate-700 sm:flex sm:items-center sm:text-base dark:text-slate-300">
-              <p className="mb-1 sm:mb-0 sm:mr-2">You&apos;re connected with env:</p>
-              <div className="flex items-center">
-                <strong className="w-32 truncate sm:w-auto">
-                  {process.env.NEXT_PUBLIC_FORMBRICKS_ENVIRONMENT_ID}
-                </strong>
-                <span className="relative ml-2 flex h-3 w-3">
-                  <span className="absolute inline-flex h-full w-full animate-ping rounded-full bg-green-500 opacity-75"></span>
-                  <span className="relative inline-flex h-3 w-3 rounded-full bg-green-500"></span>
-                </span>
-              </div>
-            </div>
-          </div>
-          <div className="mt-4 rounded-lg border border-slate-300 bg-slate-100 p-6 dark:border-slate-600 dark:bg-slate-900">
-            <h3 className="text-lg font-semibold text-slate-900 dark:text-white">2. Widget Logs</h3>
-            <p className="text-slate-700 dark:text-slate-300">
-              Look at the logs to understand how the widget works.{" "}
-              <strong className="dark:text-white">Open your browser console</strong> to see the logs.
-            </p>
-            {/* <div className="max-h-[40vh] overflow-y-auto py-4">
-              <LogsContainer />
-            </div> */}
-          </div>
-        </div>
-
-        <div className="md:grid md:grid-cols-3">
-          <div className="col-span-3 rounded-lg border border-slate-300 bg-slate-100 p-6 dark:border-slate-600 dark:bg-slate-800">
-            <h3 className="text-lg font-semibold dark:text-white">
-              Reset person / pull data from Formbricks app
-            </h3>
-            <p className="text-slate-700 dark:text-slate-300">
-              On formbricks.reset() the local state will <strong>be deleted</strong> and formbricks gets{" "}
-              <strong>reinitialized</strong>.
-            </p>
-            <button
-              className="my-4 rounded-lg bg-slate-500 px-6 py-3 text-white hover:bg-slate-700 dark:bg-slate-700 dark:hover:bg-slate-600"
-              onClick={() => {
-                formbricksWebsite.reset();
-              }}>
-              Reset
-            </button>
-            <p className="text-xs text-slate-700 dark:text-slate-300">
-              If you made a change in Formbricks app and it does not seem to work, hit &apos;Reset&apos; and
-              try again.
-            </p>
-          </div>
-
-          <div className="pt-6">
-            <div>
-              <button
-                className="mb-4 rounded-lg bg-slate-800 px-6 py-3 text-white hover:bg-slate-700 dark:bg-slate-700 dark:hover:bg-slate-600"
-                onClick={() => {
-                  formbricksWebsite.track("New Session");
-                }}>
-                Track New Session
-              </button>
-            </div>
-            <div>
-              <p className="text-xs text-slate-700 dark:text-slate-300">
-                This button sends an Action to the Formbricks API called &apos;New Session&apos;. You will
-                find it in the Actions Tab.
-              </p>
-            </div>
-          </div>
-
-          <div className="pt-6">
-            <div>
-              <button
-                className="mb-4 rounded-lg bg-slate-800 px-6 py-3 text-white hover:bg-slate-700 dark:bg-slate-700 dark:hover:bg-slate-600"
-                onClick={() => {
-                  formbricksWebsite.track("Exit Intent");
-                }}>
-                Track Exit Intent
-              </button>
-            </div>
-            <div>
-              <p className="text-xs text-slate-700 dark:text-slate-300">
-                This button sends an Action to the Formbricks API called &apos;Exit Intent&apos;. You can also
-                move your mouse to the top of the browser to trigger the exit intent.
-              </p>
-            </div>
-          </div>
-
-          <div className="pt-6">
-            <div>
-              <button
-                className="mb-4 rounded-lg bg-slate-800 px-6 py-3 text-white hover:bg-slate-700 dark:bg-slate-700 dark:hover:bg-slate-600"
-                onClick={() => {
-                  formbricksWebsite.track("50% Scroll");
-                }}>
-                Track 50% Scroll
-              </button>
-            </div>
-            <div>
-              <p className="text-xs text-slate-700 dark:text-slate-300">
-                This button sends an Action to the Formbricks API called &apos;50% Scroll&apos;. You can also
-                scroll down to trigger the 50% scroll.
-              </p>
-            </div>
-          </div>
-        </div>
-      </div>
-    </div>
-  );
-}

apps/demo/tsconfig.json

@@ -1,5 +1,23 @@
 {
-  "extends": "@formbricks/tsconfig/nextjs.json",
+  "compilerOptions": {
+    "target": "es5",
+    "lib": ["dom", "dom.iterable", "esnext"],
+    "allowJs": true,
+    "skipLibCheck": true,
+    "strict": true,
+    "forceConsistentCasingInFileNames": true,
+    "noEmit": true,
+    "esModuleInterop": true,
+    "module": "esnext",
+    "moduleResolution": "node",
+    "resolveJsonModule": true,
+    "isolatedModules": true,
+    "jsx": "preserve",
+    "incremental": true,
+    "paths": {
+      "@/*": ["./*"]
+    }
+  },
   "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx"],
   "exclude": ["node_modules"]
 }

apps/formbricks-com/.env.example

@@ -4,7 +4,3 @@ NEXT_PUBLIC_FORMBRICKS_COM_DOCS_FEEDBACK_SURVEY_ID=
 
 # Strapi API Key
 STRAPI_API_KEY=
-
-NEXT_PUBLIC_DOCSEARCH_APP_ID=
-NEXT_PUBLIC_DOCSEARCH_API_KEY=
-NEXT_PUBLIC_DOCSEARCH_INDEX_NAME=

apps/formbricks-com/app/[surveyId]/route.ts

@@ -1,5 +0,0 @@
-export async function GET(_: Request, { params }: { params: { surveyId: string } }) {
-  const surveyId = params.surveyId;
-  // redirect to Formbricks Cloud
-  return Response.redirect(`https://app.formbricks.com/s/${surveyId}`, 301);
-}

apps/formbricks-com/app/docs/additional-features/multi-language-surveys/page.mdx

@@ -1,174 +0,0 @@
-import { MdxImage } from "@/components/shared/MdxImage";
-
-import AddLanguageInSurvey from "./add-language-in-survey.webp";
-import AddLanguages from "./add-languages.webp";
-import EditMultiLang from "./edit-multi-lang.webp";
-import EnableMultiLang from "./enable-multi-lang.webp";
-import SeeSurveyInLanguage from "./see-survey-in-language.webp";
-import SurveyLanguagesFromHome from "./survey-languages-from-home.webp";
-import SurveyLanguageSettings from "./survey-languague-settings.webp";
-import SurveySharing from "./survey-sharing.webp";
-import SurveysHome from "./surveys-home.webp";
-import TranslateAsPerLanguage from "./translate-as-per-language.webp";
-
-export const metadata = {
-  title: "Multi-language Surveys | Formbricks",
-  description:
-    "Create multi-language link & in-app surveys with Formbricks. Get feedback from your users in their preferred language without writing a single line of code.",
-};
-
-#### Additional Features
-
-# Multi-language Surveys
-
-Multi-Language Surveys allow you to create surveys that support multiple languages using translations. This makes it easier to reach a diverse audience without creating separate surveys for each language. This feature simplifies the creation, delivery, and analysis of surveys for a multilingual audience.
-
-How to deliver a specific language depends on the survey type (in-app or link survey):
-
-- In-app survey: Set a `language` attribute for the user. [See the guide below for In-App Surveys](#in-app-surveys-configuration)
-- Link survey: Add a `lang` parameter in the survey URL. [See the guide below for Link Surveys](#link-surveys-configuration)
-
-<Note>
-  Multi-Language is feature of the Enterprise Edition. You can use it for **free** by adding your credit card details
-  on the Formbricks Cloud.
-</Note>
-
-<iframe
-  width="700"
-  height="450"
-  src="https://www.youtube.com/embed/Vol5zjYIoos?si=FOeDSqcy_OgtaUyM"
-  title="YouTube video player: Formbricks"
-  frameborder="0"
-  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"></iframe>
-
----
-
-## Creating a Multi-language Survey
-
-1. Open the **Survey Languages** page in the Formbricks settings via the top-right menu:
-
-<MdxImage
-  src={SurveyLanguagesFromHome}
-  alt="Formbricks Home"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-2. Click on the **Edit Languages** button, to add a new language to your survey
-
-<MdxImage
-  src={SurveyLanguageSettings}
-  alt="Formbricks Home"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-3. Select the preferred language from the dropdown and assign an identifier Alias. Click the **Add Language** button to add the language to your product.
-
-<MdxImage
-  src={AddLanguages}
-  alt="Add Multiple Languages to your Product"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-You can come back to this page anytime to add more languages or remove existing ones.
-
-4. Now, return to the dashboard to create a new survey or edit an existing one.
-
-<MdxImage
-  src={SurveysHome}
-  alt="Add Multiple Languages to your Product"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-5. In the survey editor, scroll down to the **Multiple Languages** section at the bottom and enable the toggle next to it.
-
-<MdxImage
-  src={EnableMultiLang}
-  alt="Enable Multi-language for a survey"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-6. Now choose a **Default Language** for your survey. This is the language that will be shown to users who have not selected a preferred language.
-
-<Note>Changing the default language will reset all the translations you have made for the survey.</Note>
-
-7. Now, add the languages from the dropdown that you want to support in your survey.
-
-<MdxImage
-  src={AddLanguageInSurvey}
-  alt="Enable Multi-language for a survey"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-8. You can now see the survey in the selected language by clicking on the language dropdown in any of the questions.
-
-<MdxImage
-  src={SeeSurveyInLanguage}
-  alt="Enable Multi-language for a survey"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-9. You can now translate all survey content, including questions, options, and button placeholders, into the selected language.
-
-<MdxImage
-  src={TranslateAsPerLanguage}
-  alt="Enable Multi-language for a survey"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-10. Once you are done, click on the **Publish** button to save the survey.
-
-## In-App Surveys Configuration
-
-1. When you initialise the Formbricks SDK for your user, you can pass a `language` attribute with the language code. This can be either the ISO identifier or the Alias you set when creating the language. The `language` attribute makes sure that this user only sees surveys with a translation in this specific language available.
-<Col>
-  <CodeGroup title="Configuring Formbricks SDK with Multi-language">
-
-```js
-Formbricks.init({
-  environmentId: "<environment-id>",
-  apiHost: "<api-host>",
-  userId: "<user_id>",
-  attributes: {
-    language: "de", // ISO identifier or Alias set when creating language
-  },
-});
-```
-
-  </CodeGroup>
-</Col>
-
-
-<Note>If a user has a language assigned, a survey has multi-language activate and it is missing a translation in the language of the user, the survey will not be displayed.</Note>
-
-
-2. That's it! Now, users with the language attribute set will see the survey in their preferred language. You can start collecting responses in multiple languages and filter them by language on the summary page.
-
----
-
-## Link Surveys Configuration
-
-For link surveys, the translation delivery is dependent on the `land` URL parameter.
-
-After publishing the survey, just copy the survey link and append the `lang` query parameter with the language alias you have set.
-
-For example, if you have set the alias for French as `fr`, you can share the survey link as
-
-`https://your-survey-url.com?lang=fr`
-
-Here are two examples:
-
-- English: https://app.Formbricks.com/s/clptfos2i1pj516pvhxqyu3bn?lang=en
-- German: https://app.Formbricks.com/s/clptfos2i1pj516pvhxqyu3bn?lang=de
-
-Without the `lang` parameter, Formbricks will show the survey in the default language you have set.
-
-You can now start collecting responses in multiple languages! 
-
-Can’t figure it out? Join our [Discord](https://discord.com/invite/3YFcABF2Ts)!

apps/formbricks-com/app/docs/api/management/api-key-setup/page.mdx

@@ -1,4 +1,4 @@
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import AddApiKey from "./add-api-key.webp";
 import ApiKeySecret from "./api-key-secret.webp";
@@ -21,25 +21,25 @@ The API requests are authorized with a personal API key. This API key gives you
 
 1. Go to your settings on [app.formbricks.com](https://app.formbricks.com).
 2. Go to page “API keys”
-   <MdxImage src={AddApiKey} alt="Add API Key" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+   <Image src={AddApiKey} alt="Add API Key" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 3. Create a key for the development or production environment.
 4. Copy the key immediately. You won’t be able to see it again.
-   <MdxImage
+   <Image
      src={ApiKeySecret}
      alt="API Key Secret"
      quality="100"
-     className="max-w-full rounded-lg sm:max-w-3xl"
+     className="rounded-lg max-w-full sm:max-w-3xl"
    />
 
 <Note>
-  ### Store API key safely! 
-  Anyone who has your API key has full control over your account. For security
-  reasons, you cannot view the API key again.
+  ### Store API key safely
+  Anyone who has your API key has full control over your account.
+  For security reasons, you cannot view the API key again.
 </Note>
 
 ### Test your API Key
 
-Hit the below request to verify that you are authenticated with your API Key and the server is responding.
+Hit the below request to verify that you are authenticated with your API Key and the server is responding. 
 
 ## Get My Profile {{ tag: 'GET', label: '/api/v1/me' }}
 

apps/formbricks-com/app/docs/api/management/surveys/page.mdx

@@ -1,14 +1,13 @@
 import { Fence } from "@/components/shared/Fence";
-import { generateManagementApiMetadata } from "@/lib/utils";
+import {generateManagementApiMetadata} from "@/lib/utils"
 
-export const metadata = generateManagementApiMetadata("Surveys", ["Fetch", "Create", "Update", "Delete"]);
+export const metadata = generateManagementApiMetadata("Surveys",["Fetch","Create","Update","Delete"])
 
 #### Management API
 
 # Surveys API
 
 This set of API can be used to
-
 - [List All Surveys](#list-all-surveys)
 - [Get Survey](#get-survey-by-id)
 - [Create Survey](#create-survey)
@@ -23,7 +22,8 @@ This set of API can be used to
 
 <Row>
   <Col>
-    Retrieve all the surveys you have for the environment with pagination.
+
+    Retrieve all the surveys you have for the environment.
 
     ### Mandatory Headers
 
@@ -33,26 +33,14 @@ This set of API can be used to
       </Property>
     </Properties>
 
-    ### Query Parameters
-    <Properties>
-      <Property name="offset" type="number">
-        The number of surveys to skip before returning the results.
-      </Property>
-
-      <Property name="limit" type="number">
-        The number of surveys to return.
-      </Property>
-    </Properties>
-
   </Col>
   <Col sticky>
 
     <CodeGroup title="Request" tag="GET" label="/api/v1/management/surveys">
 
     ```bash {{ title: 'cURL' }}
-
     curl --location \
-    'https://app.formbricks.com/api/v1/management/surveys?offset=20&limit=10' \
+    'https://app.formbricks.com/api/v1/management/surveys' \
     --header \
     'x-api-key: <your-api-key>'
     ```
@@ -91,7 +79,7 @@ This set of API can be used to
                                 "destination": "end"
                             }
                         ],
-                        "html": "<p class=\"fb-editor-paragraph\" dir=\"ltr\"><span>We would love to understand your user experience better. Sharing your insight helps a lot.</span></p>",
+                        "html": "<p class=\"fb-editor-paragraph\" dir=\"ltr\"><span>We would love to understand your user experience better. Sharing your insight helps a lot!</span></p>",
                         "buttonExternal": false,
                         "dismissButtonLabel": "No, thanks."
                     },
@@ -415,6 +403,7 @@ This set of API can be used to
     ```
     </CodeGroup>
 
+
   </Col>
   <Col sticky>
 
@@ -464,7 +453,7 @@ This set of API can be used to
         }
     }
     ```
-
+    
     ```json {{ title: '401 Not Authenticated' }}
     {
       "code": "not_authenticated",
@@ -508,13 +497,14 @@ This set of API can be used to
     ```
     </CodeGroup>
 
+
   </Col>
   <Col sticky>
 
     <CodeGroup title="Request" tag="PUT" label="/api/v1/management/surveys/<survey-id>">
 
     ```bash {{ title: 'cURL' }}
-    curl -X PUT https://app.formbricks.com/api/v1/management/surveys/<survey-id> \
+    curl -X POST https://app.formbricks.com/api/v1/management/surveys/<survey-id> \
      --header 'Content-Type: application/json' \
      --header 'x-api-key: <your-api-key>' \
      -d '{"name": "My renamed Survey"}'
@@ -578,7 +568,7 @@ This set of API can be used to
         }
     }
     ```
-
+    
     ```json {{ title: '401 Not Authenticated' }}
     {
       "code": "not_authenticated",
@@ -595,6 +585,7 @@ This set of API can be used to
 
 ---
 
+
 ## Delete Survey by ID {{ tag: 'DELETE', label: '/api/v1/management/surveys/<survey-id>' }}
 
 <Row>

apps/formbricks-com/app/docs/best-practices/cancel-subscription/page.mdx

@@ -1,5 +1,5 @@
 import DemoPreview from "@/components/dummyUI/DemoPreview";
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import ChangeText from "./change-text.webp";
 import CreateChurnFlow from "./create-cancel-flow.webp";
@@ -46,7 +46,8 @@ To run the Churn Survey in your app you want to proceed as follows:
 4. Prevent that churn!
 
 <Note>
-  ## Formbricks Widget running? We assume that you have already installed the Formbricks Widget in your web
+  ## Formbricks Widget running? 
+  We assume that you have already installed the Formbricks Widget in your web
   app. It’s required to display messages and surveys in your app. If not, please follow the [Quick Start Guide
   (takes 15mins max.)](/docs/getting-started/quickstart-in-app-survey)
 </Note>
@@ -57,7 +58,7 @@ If you don't have an account yet, create one at [app.formbricks.com](https://app
 
 Click on "Create Survey" and choose the template “Churn Survey”:
 
-<MdxImage
+<Image
   src={CreateChurnFlow}
   alt="Create churn survey by template"
   quality="100"
@@ -68,7 +69,7 @@ Click on "Create Survey" and choose the template “Churn Survey”:
 
 You’re free to update the question and answer options. However, based on our experience, we suggest giving the provided template a go 😊
 
-<MdxImage
+<Image
   src={ChangeText}
   alt="Change text content"
   quality="100"
@@ -89,7 +90,7 @@ To create the trigger for your Churn Survey, you have two options to choose from
 
 1. **Trigger by innerText:** You likely have a “Cancel Subscription” button in your app. You can setup a user Action with the according `innerText` to trigger the survey, like so:
 
-<MdxImage
+<Image
   src={TriggerInnerText}
   alt="Set the trigger by inner Text"
   quality="100"
@@ -98,7 +99,7 @@ To create the trigger for your Churn Survey, you have two options to choose from
 
 2. **Trigger by CSS Selector:** In case you have more than one button saying “Cancel Subscription” in your app and only want to display the survey when one of them is clicked, you want to be more specific. The best way to do that is to give this button the HTML `id=“cancel-subscription”` and set your user action up like so:
 
-<MdxImage
+<Image
   src={TriggerCSS}
   alt="Set the trigger by CSS Selector"
   quality="100"
@@ -107,7 +108,7 @@ To create the trigger for your Churn Survey, you have two options to choose from
 
 3. **Trigger by pageURL:** Lastly, you could also display your survey on a subpage “/subscription-cancelled” where you forward users once they cancelled the trial subscription. You can then create a user Action with the type `pageURL` with the following settings:
 
-<MdxImage
+<Image
   src={TriggerPageUrl}
   alt="Set the trigger by page URL"
   quality="100"
@@ -119,14 +120,15 @@ Whenever a user visits this page, matches the filter conditions above and the re
 Here is our complete [Actions manual](/docs/actions/why) covering [Code](/docs/actions/code) and [No-Code](/docs/actions/no-code) Actions.
 
 <Note>
-  ## Pre-churn flow coming soon We’re currently building full-screen survey pop-ups. You’ll be able to prevent
+  ## Pre-churn flow coming soon 
+  We’re currently building full-screen survey pop-ups. You’ll be able to prevent
   users from closing the survey unless they respond to it. It’s certainly debatable if you want that but you
   could force them to click through the survey before letting them cancel 🤷
 </Note>
 
 ### 5. Select Action in the “When to ask” card
 
-<MdxImage
+<Image
   src={SelectAction}
   alt="Select feedback button action"
   quality="100"
@@ -137,7 +139,7 @@ Here is our complete [Actions manual](/docs/actions/why) covering [Code](/docs/a
 
 Lastly, scroll down to “Recontact Options”. Here you have to choose the correct settings to make sure you milk these super valuable insights. You want to make sure that this survey is always displayed, no matter if the user has already seen a survey in the past days:
 
-<MdxImage
+<Image
   src={RecontactOptions}
   alt="Set recontact options"
   quality="100"
@@ -148,7 +150,7 @@ These settings make sure the survey is always displayed, when a user wants to Ca
 
 ### 7. Congrats! You’re ready to publish your survey 💃
 
-<MdxImage
+<Image
   src={PublishSurvey}
   alt="Publish survey"
   quality="100"
@@ -156,7 +158,8 @@ These settings make sure the survey is always displayed, when a user wants to Ca
 />
 
 <Note>
-  ## Formbricks Widget running? You need to have the Formbricks Widget installed to display the Churn Survey
+  ## Formbricks Widget running? 
+  You need to have the Formbricks Widget installed to display the Churn Survey
   in your app. Please follow [this tutorial (Step 4 onwards)](/docs/getting-started/quickstart-in-app-survey)
   to install the widget.
 </Note>

apps/formbricks-com/app/docs/best-practices/docs-feedback/page.mdx

@@ -1,4 +1,4 @@
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import DocsFeedback from "@/components/docs/DocsFeedback";
 import AddAction from "./add-action.webp";
@@ -46,7 +46,7 @@ To get this running, you'll need a bit of time. Here are the steps we're going t
 
 2. In the Menu (top right) you see that you can switch between a “Development” and a “Production” environment. These are two separate environments so your test data doesn’t mess up the insights from prod. Switch to “Development”:
 
-<MdxImage
+<Image
   src={SwitchToDev}
   alt="switch to dev environment"
   quality="100"
@@ -55,7 +55,7 @@ To get this running, you'll need a bit of time. Here are the steps we're going t
 
 3. Then, create a survey using the template “Docs Feedback”:
 
-<MdxImage
+<Image
   src={DocsTemplate}
   alt="select docs template"
   quality="100"
@@ -64,7 +64,7 @@ To get this running, you'll need a bit of time. Here are the steps we're going t
 
 4. Change the Internal Question ID of the first question to **“isHelpful”** to make your life easier 😉
 
-<MdxImage
+<Image
   src={ChangeId}
   alt="switch to dev environment"
   quality="100"
@@ -80,7 +80,7 @@ To get this running, you'll need a bit of time. Here are the steps we're going t
 
 6. Click on “Continue to Settings or select the audience tab manually. Scroll down to “When to ask” and create a new Action:
 
-<MdxImage
+<Image
   src={WhenToAsk}
   alt="set up when to ask card"
   quality="100"
@@ -89,7 +89,7 @@ To get this running, you'll need a bit of time. Here are the steps we're going t
 
 7. Our goal is to create an event that never fires. This is a bit nonsensical because it is a workaround. Stick with me 😃 Fill the action out like on the screenshot:
 
-<MdxImage
+<Image
   src={AddAction}
   alt="add action"
   quality="100"
@@ -99,7 +99,7 @@ To get this running, you'll need a bit of time. Here are the steps we're going t
 
 8. Select the Non-Event in the dropdown. Now you see that the “Publish survey” button is active. Publish your survey 🤝
 
-<MdxImage
+<Image
   src={SelectNonevent}
   alt="select nonevent"
   quality="100"
@@ -128,7 +128,7 @@ This allows us to capture and analyze partial feedback where the user is not wil
 
 2. Likely, you have a template file or similar which renders the navigation at the bottom of the page:
 
-<MdxImage
+<Image
   src={DocsNavi}
   alt="doc navigation"
   quality="100"
@@ -412,7 +412,7 @@ Before you roll it out in production, you want to test it. To do so, you need tw
 
 When you are on the survey detail page, you’ll find both of them in the URL:
 
-<MdxImage src={CopyIds} alt="copy IDs" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+<Image src={CopyIds} alt="copy IDs" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
 
 Now, you have to replace the IDs and the API host accordingly in your `handleFeedbackSubmit`:
 <Col>

apps/formbricks-com/app/docs/best-practices/feature-chaser/page.mdx

@@ -1,5 +1,5 @@
 import DemoPreview from "@/components/dummyUI/DemoPreview";
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import ActionCSS from "./action-css.webp";
 import ActionText from "./action-text.webp";
@@ -43,7 +43,8 @@ To run the Feature Chaser survey in your app you want to proceed as follows:
 2. Setup a user action to display survey at the right point in time
 
 <Note>
-  ## Formbricks Widget running? We assume that you have already installed the Formbricks Widget in your web
+  ## Formbricks Widget running? 
+  We assume that you have already installed the Formbricks Widget in your web
   app. It’s required to display messages and surveys in your app. If not, please follow the [Quick Start Guide
   (takes 15mins max.)](/docs/getting-started/quickstart-in-app-survey)
 </Note>
@@ -54,7 +55,7 @@ If you don't have an account yet, create one at [app.formbricks.com](https://app
 
 Click on "Create Survey" and choose the template “Feature Chaser”:
 
-<MdxImage
+<Image
   src={CreateSurvey}
   alt="Create survey by template"
   quality="100"
@@ -65,7 +66,7 @@ Click on "Create Survey" and choose the template “Feature Chaser”:
 
 The questions you want to ask are dependent on your feature and can be very specific. In the template, we suggest a high-level check on how easy it was for the user to achieve their goal. We also add an opportunity to provide context:
 
-<MdxImage
+<Image
   src={ChangeText}
   alt="Change text content"
   quality="100"
@@ -84,7 +85,7 @@ There are two ways to track a button:
 
 1. **Trigger by innerText:** You might have a button with a unique text at the end of your feature e.g. "Export Report". You can setup a user Action with the according `innerText` to trigger the survey, like so:
 
-<MdxImage
+<Image
   src={ActionText}
   alt="Set the trigger by inner Text"
   quality="100"
@@ -93,7 +94,7 @@ There are two ways to track a button:
 
 2. **Trigger by CSS Selector:** In case you have more than one button saying “Export Report” in your app and only want to display the survey when one of them is clicked, you want to be more specific. The best way to do that is to give this button the HTML `id=“export-report-featurename”` and set your user action up like so:
 
-<MdxImage
+<Image
   src={ActionCSS}
   alt="Set the trigger by CSS Selector"
   quality="100"
@@ -104,7 +105,7 @@ Please follow our [Actions manual](/docs/actions/why) for an in-depth descriptio
 
 ### 4. Select Action in the “When to ask” card
 
-<MdxImage
+<Image
   src={SelectAction}
   alt="Select PMF trigger button action"
   quality="100"
@@ -115,7 +116,7 @@ Please follow our [Actions manual](/docs/actions/why) for an in-depth descriptio
 
 Lastly, scroll down to “Recontact Options”. Here you have full freedom to decide who you want to ask. Generally, you only want to ask every user once and prevent survey fatigue. It's up to you to decide if you want to ask again, when the user did not yet reply:
 
-<MdxImage
+<Image
   src={RecontactOptions}
   alt="Set recontact options"
   quality="100"
@@ -124,10 +125,11 @@ Lastly, scroll down to “Recontact Options”. Here you have full freedom to de
 
 ### 7. Congrats! You’re ready to publish your survey 💃
 
-<MdxImage src={Publish} alt="Publish survey" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+<Image src={Publish} alt="Publish survey" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
 
 <Note>
-  ## Formbricks Widget running? You need to have the Formbricks Widget installed to display the Feature Chaser
+  ## Formbricks Widget running?
+   You need to have the Formbricks Widget installed to display the Feature Chaser
   in your app. Please follow [this tutorial (Step 4 onwards)](/docs/getting-started/quickstart-in-app-survey)
   to install the widget.
 </Note>

apps/formbricks-com/app/docs/best-practices/feedback-box/page.mdx

@@ -1,6 +1,6 @@
-import DemoPreview from "@/components/dummyUI/DemoPreview";
-import { MdxImage } from "@/components/shared/MdxImage";
 import Link from "next/link";
+import Image from "next/image";
+import DemoPreview from "@/components/dummyUI/DemoPreview";
 
 import AddAction from "./add-action.webp";
 import AddCSSAction from "./add-css-action.webp";
@@ -13,8 +13,7 @@ import RecontactOptions from "./set-recontact-options.webp";
 
 export const metadata = {
   title: "Implementing the Feedback Box with Formbricks: A Step-by-Step Tutorial",
-  description:
-    "Unlock user insights effortlessly! Discover how to set up the Feedback Box in your app using Formbricks, allowing your users to provide real-time feedback. Follow our comprehensive guide to enhance user experience and respond rapidly to feedback",
+  description: "Unlock user insights effortlessly! Discover how to set up the Feedback Box in your app using Formbricks, allowing your users to provide real-time feedback. Follow our comprehensive guide to enhance user experience and respond rapidly to feedback",
 };
 
 #### Best Practices
@@ -50,34 +49,34 @@ If you don't have an account yet, create one at [app.formbricks.com](https://app
 
 Then, create a new survey and look for the "Feedback Box" template:
 
-<MdxImage
+<Image
   src={CreateFeedbackBox}
   alt="Create feedback box by template"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 ### 2. Update question content
 
 Change the questions and answer options according to your preference:
 
-<MdxImage
+<Image
   src={ChangeTextContent}
   alt="Change text content"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 ### 3. Create user action to trigger Feedback Box:
 
 Go to the “Audience” tab, find the “When to send” card and choose “Add Action”. We will now use our super cool No-Code User Action Tracker:
 
-<MdxImage src={AddAction} alt="Add action" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+<Image src={AddAction} alt="Add action" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 <Note>
-  ## You can also add actions in your code You can also create [Code Actions](/docs/actions/code) using
-  `formbricks.track("Eventname")` - they will automatically appear in your Actions overview as long as the SDK
-  is embedded.
+  ## You can also add actions in your code 
+  You can also create [Code Actions](/docs/actions/code) using `formbricks.track("Eventname")` - they will automatically
+  appear in your Actions overview as long as the SDK is embedded.
 </Note>
 
 We have two options to track the Feedback Button in your application: innerText and CSS-Selector:
@@ -85,46 +84,46 @@ We have two options to track the Feedback Button in your application: innerText
 1. **innerText:** This means that whenever a user clicks any HTML item in your app which has an `innerText` of `Feedback` the Feedback Box will be displayed.
 2. **CSS-Selector:** This means that when an element with a specific CSS-Selector like `#feedback-button` is clicked, your Feedback Box is triggered.
 
-<div className="grid max-w-full grid-cols-2 space-x-2 sm:max-w-3xl">
-  <MdxImage src={AddHTMLAction} alt="Add HTML action" quality="100" className="rounded-lg" />
-  <MdxImage src={AddCSSAction} alt="Add CSS action" quality="100" className="rounded-lg" />
+<div className="grid grid-cols-2 space-x-2 max-w-full sm:max-w-3xl">
+  <Image src={AddHTMLAction} alt="Add HTML action" quality="100" className="rounded-lg" />
+  <Image src={AddCSSAction} alt="Add CSS action" quality="100" className="rounded-lg" />
 </div>
 
 ### 4. Select action in the “When to ask” card
 
-<MdxImage
+<Image
   src={SelectAction}
   alt="Select feedback button action"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 ### 5. Set Recontact Options correctly
 
 Scroll down to “Recontact Options”. Here you have to choose the right settings so that the Feedback Box pops up every time the user action is performed. (Our default is that every user sees every survey only once):
 
-<MdxImage
+<Image
   src={RecontactOptions}
   alt="Set recontact options"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 ### 6. You’re ready publish your survey!
 
-<MdxImage
+<Image
   src={PublishSurvey}
   alt="Publish survey"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 ## Setting up the Widget
 
 <Note>
-  ## Formbricks Widget running? You need to have the Formbricks Widget installed to display the Feedback Box
-  in your app. Please follow [this tutorial (Step 4 onwards)](/docs/getting-started/quickstart-in-app-survey)
-  to install the widget.
+  ## Formbricks Widget running?
+  You need to have the Formbricks Widget installed to display the Feedback Box in your app. Please follow [this
+  tutorial (Step 4 onwards)](/docs/getting-started/quickstart-in-app-survey) to install the widget.
 </Note>
 
 ### &nbsp;

apps/formbricks-com/app/docs/best-practices/improve-email-content/page.mdx

@@ -1,12 +1,10 @@
 import DemoPreview from "@/components/dummyUI/DemoPreview";
-import { MdxImage } from "@/components/shared/MdxImage";
-
-import NewsletterSurveyType from "./choose-survey-type.webp";
-import NewsletterSurveyEmbedCode from "./embed-survey-code-in-your-email.webp";
-import NewsletterSurveyEmbedPrompt from "./embed-survey-prompt.webp";
-import NewsletterSurveyEditor from "./improve-newsletter-content-editor-formbricks.webp";
-import NewsletterSurvey from "./improve-newsletter-content-survey-location.webp";
-
+import Image from "next/image";
+import NewsletterSurveyType from './choose-survey-type.webp';
+import NewsletterSurveyEmbedCode from './embed-survey-code-in-your-email.webp';
+import NewsletterSurveyEmbedPrompt from './embed-survey-prompt.webp';
+import NewsletterSurveyEditor from './improve-newsletter-content-editor-formbricks.webp';
+import NewsletterSurvey from './improve-newsletter-content-survey-location.webp';
 export const metadata = {
   title: "Measure email content quality with Formbricks",
   description:
@@ -16,9 +14,9 @@ export const metadata = {
 #### Best Practices
 
 # Improve Email Content
-
 Email remains the predominant way to communicate with your customers. Measure the effectiveness to improve your offering.
 
+
 ## Purpose
 
 Measuring the content quality of both transactional and marketing email is a key element for improving customer communication.
@@ -39,7 +37,7 @@ To embed the newsletter survey into your email, follow these steps:
 
 1. Create new 'Improve Newsletter Content' survey at [app.formbricks.com](https://app.formbricks.com/)
 2. Select how you where you want to display the survey.
-3. Copy the embed code anywhere you want in your newsletter.
+3. Copy the embed code anywhere you want in your newsletter. 
 
 ### 1. Create new 'Improve Newsletter Content' Survey
 
@@ -47,44 +45,44 @@ If you don't have an account yet, create one at [app.formbricks.com](https://app
 
 Then, create a new survey and look for the "Improve Newsletter Content" template:
 
-<MdxImage
+<Image
   src={NewsletterSurvey}
   alt="Create Improve Newsletter Content by template"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 ### 2. Customize Survey questions
 
 Customize survey questions, emojis or stars however you like:
 
-<MdxImage
+<Image
   src={NewsletterSurveyEditor}
   alt="Edit Improve Newsletter Content template"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 ### 3. Configure Survey Settings
 
 When you are done customizing your survey questions, navigate to the Settings tab and choose the type of survey you want. You need to choose Link Survey:
 
-<MdxImage
+<Image
   src={NewsletterSurveyType}
   alt="Choose survey type"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 ### 4. Choose how you want to embed your survey
 
 After publishing your survey, a modal that prompts you to embed your survey will pop up.
 
-<MdxImage
+<Image
   src={NewsletterSurveyEmbedPrompt}
   alt="Embed newsletter survey"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 Select the Embed Survey card and you will be directed to another modal, where the first embed option displayed will be to embed the survey in an email.
@@ -93,23 +91,23 @@ Select the Embed Survey card and you will be directed to another modal, where th
 
 Click the button with the “View Embed Code” text at the top right corner of the modal and simply paste the HTML code for your survey anywhere you want it in your newsletter. You can see the preview in the below image:
 
-<MdxImage
+<Image
   src={NewsletterSurveyEmbedCode}
   alt="Embed survey code"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 And you're done! Send a test email to yourself and try it out 🤓
 
-## Learn about data prefilling
+
+## Learn about data prefilling 
 
 <Note>
-  ## How does data prefilling work? Learn about how link prefilling and user identification maximize your
-  insights in [this detailed
-  guide](/blog/how-smart-writers-use-formbricks-open-source-tool-to-measure-the-quality-of-their-newsletter-content).
+  ## How does data prefilling work?
+  Learn about how link prefilling and user identification maximize your insights in [this detailed guide](/blog/how-smart-writers-use-formbricks-open-source-tool-to-measure-the-quality-of-their-newsletter-content).
 </Note>
 
 ### &nbsp;
 
-# That’s it! 🎉
+# That’s it! 🎉

apps/formbricks-com/app/docs/best-practices/improve-trial-cr/page.mdx

@@ -1,5 +1,5 @@
 import DemoPreview from "@/components/dummyUI/DemoPreview";
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import ActionText from "./action-innertext.webp";
 import ActionPageurl from "./action-pageurl.webp";
@@ -43,7 +43,8 @@ To display the Trial Conversion Survey in your app you want to proceed as follow
 3. Print that 💸
 
 <Note>
-  ## Formbricks Widget running? We assume that you have already installed the Formbricks Widget in your web
+  ## Formbricks Widget running?
+   We assume that you have already installed the Formbricks Widget in your web
   app. It’s required to display messages and surveys in your app. If not, please follow the [Quick Start Guide
   (takes 15mins max.)](/docs/getting-started/quickstart-in-app-survey)
 </Note>
@@ -54,7 +55,7 @@ If you don't have an account yet, create one at [app.formbricks.com](https://app
 
 Click on "Create Survey" and choose the template “Improve Trial Conversion”:
 
-<MdxImage
+<Image
   src={CreateSurvey}
   alt="Create survey by template"
   quality="100"
@@ -65,7 +66,7 @@ Click on "Create Survey" and choose the template “Improve Trial Conversion”:
 
 You’re free to update the questions and answer options. However, based on our experience, we suggest giving the provided template a go 😊
 
-<MdxImage
+<Image
   src={ChangeText}
   alt="Change text content"
   quality="100"
@@ -79,7 +80,8 @@ Save, and move over to the “Audience” tab.
 ### 3. Pre-segment your audience (coming soon)
 
 <Note>
-  ## Filter by attribute coming soon We're working on pre-segmenting users by attributes. We will update this
+  ## Filter by attribute coming soon 
+  We're working on pre-segmenting users by attributes. We will update this
   manual in the next days.
 </Note>
 
@@ -91,7 +93,7 @@ How you trigger your survey depends on your product. There are two options:
 
 1. **Trigger by pageURL:** Let’s say you have a page under “/trial-cancelled” where you forward users once they cancelled the trial subscription. You can then create an user Action with the type `pageURL` with the following settings:
 
-<MdxImage
+<Image
   src={ActionPageurl}
   alt="Change text content"
   quality="100"
@@ -102,7 +104,7 @@ Whenever a user visits this page, the survey will be displayed ✅
 
 2. **Trigger by Button Click:** In a different case, you have a “Cancel Trial button in your app. You can setup a user Action with the according `innerText` like so:
 
-<MdxImage
+<Image
   src={ActionText}
   alt="Change text content"
   quality="100"
@@ -113,7 +115,7 @@ Please have a look at our complete [Actions manual](/docs/actions/why) if you ha
 
 ### 5. Select Action in the “When to ask” card
 
-<MdxImage
+<Image
   src={SelectAction}
   alt="Select feedback button action"
   quality="100"
@@ -124,7 +126,7 @@ Please have a look at our complete [Actions manual](/docs/actions/why) if you ha
 
 Lastly, scroll down to “Recontact Options”. Here you have to choose the correct settings to make sure you gather as many insights as possible. You want to make sure that this survey is always displayed, no matter if the user has already seen a survey in the past days:
 
-<MdxImage
+<Image
   src={RecontactOptions}
   alt="Set recontact options"
   quality="100"
@@ -133,10 +135,11 @@ Lastly, scroll down to “Recontact Options”. Here you have to choose the corr
 
 ### 7. Congrats! You’re ready to publish your survey 💃
 
-<MdxImage src={Publish} alt="Publish survey" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+<Image src={Publish} alt="Publish survey" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
 
 <Note>
-  ## Formbricks Widget running? You need to have the Formbricks Widget installed to display the Feedback Box
+  ## Formbricks Widget running? 
+  You need to have the Formbricks Widget installed to display the Feedback Box
   in your app. Please follow [this tutorial (Step 4 onwards)](/docs/getting-started/quickstart-in-app-survey)
   to install the widget.
 </Note>

apps/formbricks-com/app/docs/best-practices/interview-prompt/page.mdx

@@ -1,5 +1,5 @@
 import DemoPreview from "@/components/dummyUI/DemoPreview";
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import ActionCSS from "./action-css.webp";
 import ActionInner from "./action-innertext.webp";
@@ -48,7 +48,8 @@ To display an Interview Prompt in your app you want to proceed as follows:
 3. That’s it! 🎉
 
 <Note>
-  ## Formbricks Widget running? We assume that you have already installed the Formbricks Widget in your web
+  ## Formbricks Widget running?
+   We assume that you have already installed the Formbricks Widget in your web
   app. It’s required to display messages and surveys in your app. If not, please follow the [Quick Start Guide
   (15mins).](/docs/getting-started/quickstart-in-app-survey)
 </Note>
@@ -59,7 +60,7 @@ If you don't have an account yet, create one at [app.formbricks.com](https://app
 
 Click on "Create Survey" and choose the template “Interview Prompt”:
 
-<MdxImage
+<Image
   src={CreatePrompt}
   alt="Create interview prompt by template"
   quality="100"
@@ -70,7 +71,7 @@ Click on "Create Survey" and choose the template “Interview Prompt”:
 
 Update the prompt, description and button text to match your products tonality. You can also update the button color in the Product Settings.
 
-<MdxImage
+<Image
   src={ChangeText}
   alt="Change text content"
   quality="100"
@@ -79,7 +80,7 @@ Update the prompt, description and button text to match your products tonality.
 
 In the button settings you have to make sure it is set to “External URL”. In the URL field, copy your booking link (e.g. https://cal.com/company/user-interview). If you don’t have a booking link yet, head over to [cal.com](http://cal.com) and get one - they have the best free plan out there!
 
-<MdxImage
+<Image
   src={InterviewExample}
   alt="Add CSS action"
   quality="100"
@@ -91,7 +92,8 @@ Save, and move over to the “Audience” tab.
 ### 3. Pre-segment your audience (coming soon)
 
 <Note>
-  ## Filter by attribute coming soon We're working on pre-segmenting users by attributes. We will update this
+  ## Filter by attribute coming soon 
+  We're working on pre-segmenting users by attributes. We will update this
   manual in the next few days.
 </Note>
 
@@ -105,10 +107,11 @@ Great, now only the “Power User” segment will see our Interview Prompt. But
 
 To create the trigger to show your Interview Prompt, go to the “Audience” tab, find the “When to send” card and choose “Add Action”. We will now use our super cool No-Code User Action Tracker:
 
-<MdxImage src={AddAction} alt="Add action" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+<Image src={AddAction} alt="Add action" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
 
 <Note>
-  ## You can also add actions in your code You can also create [Code Actions](/docs/actions/code) using
+  ## You can also add actions in your code
+   You can also create [Code Actions](/docs/actions/code) using
   `formbricks.track("Eventname")` - they will automatically appear in your Actions overview as long as the SDK
   is embedded.
 </Note>
@@ -117,7 +120,7 @@ Generally, we have two types of user actions: Page views and clicks. The Intervi
 
 1. **pageURL:** Whenever a user visits a page the survey will be displayed, as long as the other conditions match. Other conditions are pre-segmentation, if this user has seen a survey in the past 2 weeks, etc.
 
-<MdxImage
+<Image
   src={ActionPageurl}
   alt="Add page URL action"
   quality="100"
@@ -127,13 +130,8 @@ Generally, we have two types of user actions: Page views and clicks. The Intervi
 2. **innerText & CSS-Selector:** When a user clicks an element (like a button) with a specific text content or CSS selector, the prompt will be displayed as long as the other conditions also match.
 
 <div className="flex max-w-full flex-col sm:max-w-3xl lg:gap-1">
-  <MdxImage
-    src={ActionCSS}
-    alt="Add CSS action"
-    quality="100"
-    className="max-w-full rounded-lg sm:max-w-3xl"
-  />
-  <MdxImage
+  <Image src={ActionCSS} alt="Add CSS action" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+  <Image
     src={ActionInner}
     alt="Add inner text action"
     quality="100"
@@ -143,7 +141,7 @@ Generally, we have two types of user actions: Page views and clicks. The Intervi
 
 ### 5. Select action in the “When to ask” card
 
-<MdxImage
+<Image
   src={SelectAction}
   alt="Select feedback button action"
   quality="100"
@@ -154,7 +152,7 @@ Generally, we have two types of user actions: Page views and clicks. The Intervi
 
 Scroll down to “Recontact Options”. Here you have to choose the correct settings to strike the right balance between asking for user feedback and preventing survey fatigue. Your settings also depend on the size of your user base or segment. If you e.g. have thousands of “Power Users” you can easily afford to only display the prompt once. If you have a smaller user base you might want to ask twice to get a sufficient amount of bookings:
 
-<MdxImage
+<Image
   src={RecontactOptions}
   alt="Set recontact options"
   quality="100"
@@ -163,10 +161,11 @@ Scroll down to “Recontact Options”. Here you have to choose the correct sett
 
 ### 7. Congrats! You’re ready to publish your survey 💃 🤸
 
-<MdxImage src={Publish} alt="Publish survey" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+<Image src={Publish} alt="Publish survey" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
 
 <Note>
-  ## Formbricks Widget running? You need to have the Formbricks Widget installed to display the Feedback Box
+  ## Formbricks Widget running?
+   You need to have the Formbricks Widget installed to display the Feedback Box
   in your app. Please follow [this tutorial (Step 4 onwards)](/docs/getting-started/quickstart-in-app-survey)
   to install the widget.
 </Note>

apps/formbricks-com/app/docs/best-practices/pmf-survey/page.mdx

@@ -1,5 +1,5 @@
 import DemoPreview from "@/components/dummyUI/DemoPreview";
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import ActionCSS from "./action-css.webp";
 import ActionPageurl from "./action-pageurl.webp";
@@ -42,7 +42,8 @@ To display the Product-Market Fit survey in your app you want to proceed as foll
 3. Setup the user action to display survey at good point in time
 
 <Note>
-  ## Formbricks Widget running? We assume that you have already installed the Formbricks Widget in your web
+  ## Formbricks Widget running?
+   We assume that you have already installed the Formbricks Widget in your web
   app. It’s required to display messages and surveys in your app. If not, please follow the [Quick Start Guide
   (15mins).](/docs/getting-started/quickstart-in-app-survey)
 </Note>
@@ -53,7 +54,7 @@ If you don't have an account yet, create one at [app.formbricks.com](https://app
 
 Click on "Create Survey" and choose one of the PMF survey templates. The first one is rather short, the latter builds on the ["Product-Market Fit Engine"](https://review.firstround.com/how-superhuman-built-an-engine-to-find-product-market-fit) developed by Superhuman:
 
-<MdxImage
+<Image
   src={CreateSurvey}
   alt="Create survey by template"
   quality="100"
@@ -64,7 +65,7 @@ Click on "Create Survey" and choose one of the PMF survey templates. The first o
 
 You’re free to update the question and answer options. However, based on our experience, we suggest giving the provided template a go 😊 Here is a very [detailed description](https://coda.io/@rahulvohra/superhuman-product-market-fit-engine) of what to do with the data you’re collecting.
 
-<MdxImage
+<Image
   src={ChangeText}
   alt="Change text content"
   quality="100"
@@ -78,7 +79,8 @@ Save, and move over to where the magic happens: The “Audience” tab.
 ### 3. Pre-segment your audience (coming soon)
 
 <Note>
-  ## Filter by attribute coming soon We're working on pre-segmenting users by attributes. We will update this
+  ## Filter by attribute coming soon
+   We're working on pre-segmenting users by attributes. We will update this
   manual in the next days.
 </Note>
 
@@ -100,13 +102,13 @@ You need a trigger to display the survey but in this case, the filtering does al
 
 <Col>
   <div>
-    <MdxImage
+    <Image
       src={ActionCSS}
       alt="Add CSS action"
       quality="100"
       className="max-w-full rounded-lg sm:max-w-3xl"
     />
-    <MdxImage
+    <Image
       src={ActionPageurl}
       alt="Add inner text action"
       quality="100"
@@ -116,7 +118,7 @@ You need a trigger to display the survey but in this case, the filtering does al
 </Col>
 ### 5. Select Action in the “When to ask” card
 <Col>
-  <MdxImage
+  <Image
     src={SelectAction}
     alt="Select PMF trigger button action"
     quality="100"
@@ -127,7 +129,7 @@ You need a trigger to display the survey but in this case, the filtering does al
 
 Lastly, scroll down to “Recontact Options”. Here you have to choose the correct settings to make sure your data remains of high quality. You want to make sure that this survey is only responded to once per user. It is up to you to decide if you want to display it several times until the user responds:
 
-<MdxImage
+<Image
   src={RecontactOptions}
   alt="Set recontact options"
   quality="100"
@@ -136,10 +138,11 @@ Lastly, scroll down to “Recontact Options”. Here you have to choose the corr
 
 ### 7. Congrats! You’re ready to publish your survey 💃
 
-<MdxImage src={Publish} alt="Publish survey" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+<Image src={Publish} alt="Publish survey" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
 
 <Note>
-  ## Formbricks Widget running? You need to have the Formbricks Widget installed to display the Feedback Box
+  ## Formbricks Widget running? 
+  You need to have the Formbricks Widget installed to display the Feedback Box
   in your app. Please follow [this tutorial (Step 4 onwards)](/docs/getting-started/quickstart-in-app-survey)
   to install the widget.
 </Note>

apps/formbricks-com/app/docs/contributing/creating-a-service/page.mdx

@@ -1,5 +1,4 @@
-import { MdxImage } from "@/components/shared/MdxImage";
-
+import Image from "next/image";
 import UnstableCache from "./unstable-cache-documentation.webp";
 
 export const metadata = {
@@ -210,7 +209,6 @@ We will rewrite the function `getApiKey` we created in the `service.ts` file to
 
 ```ts
 import { unstable_cache } from "next/cache";
-
 import { SERVICES_REVALIDATION_INTERVAL } from "../constants";
 import { apiKeyCache } from "./cache";
 
@@ -254,7 +252,7 @@ _Breakdown of the above code._
 
 In the above code we only introduce something new called `unstable_cache`, read more about it [here](https://nextjs.org/docs/app/api-reference/functions/unstable_cache#parameters). In a nutshell these are its parameters:
 
-<MdxImage
+<Image
   src={UnstableCache}
   alt="Unstable Cache Parameters"
   quality="100"

apps/formbricks-com/app/docs/contributing/demo/page.mdx

@@ -1,4 +1,4 @@
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import DemoApp from "./demoapp.webp";
 
@@ -14,7 +14,7 @@ export const metadata = {
 
 To play around with the in-app [User Actions](/docs/actions/why), you can use the Demo App. It's a simple React app that you can run locally and use to trigger actions and set [Attributes](/docs/attributes/why).
 
-<MdxImage src={DemoApp} alt="Demo App Preview" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+<Image src={DemoApp} alt="Demo App Preview" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
 
 ## Functionality
 

apps/formbricks-com/app/docs/contributing/how-we-code/page.mdx

@@ -1,4 +1,4 @@
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import CorsHandling from "./cors-handling-in-api.webp";
 
@@ -65,7 +65,7 @@ Please keep the following in mind:
 - When dealing with Management APIs always make sure to require authentication via API keys and a sufficient authorization check.
 - Make sure to handle CORS requests in any new Client API endpoint you create as these are called from the browser in link surveys or `formbricks-js`. Example below:
 
-<MdxImage
+<Image
   src={CorsHandling}
   alt="Cors handling within an API"
   quality="100"

apps/formbricks-com/app/docs/contributing/setup/page.mdx

@@ -1,4 +1,4 @@
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import GitpodAuth from "./gitpod/auth.webp";
 import GitpodNewWorkspace from "./gitpod/new-workspace.webp";
@@ -93,18 +93,13 @@ After clicking the one-click setup button, Gitpod will open a new tab or window.
 
 ### 2. Authorizing in Gitpod
 
-<MdxImage
-  src={GitpodAuth}
-  alt="Gitpod Auth Page"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={GitpodAuth} alt="Gitpod Auth Page" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
 - This is the Gitpod Authentication Page. It appears when you click the "Open in GitPod" button and Gitpod needs
 to authenticate your access to the workspace. Click on 'Continue With Github' to authorize your GitPod session.
 
 ### 3. Creating a New Workspace
 
-<MdxImage
+<Image
   src={GitpodNewWorkspace}
   alt="Gitpod New workspace Page"
   quality="100"
@@ -118,7 +113,7 @@ and follow the prompts to authorize the integration. 2. Change the `WEBAPP_URL`
 
 ### 4. Gitpod preparing the created Workspace
 
-<MdxImage
+<Image
   src={GitpodPreparing}
   alt="Gitpod Preparing workspace Page"
   quality="100"
@@ -129,7 +124,7 @@ page while Gitpod sets up your development environment.
 
 ### 5. Gitpod running the Workspace
 
-<MdxImage
+<Image
   src={GitpodRunning}
   alt="Gitpod Running Workspace Page"
   quality="100"
@@ -194,7 +189,7 @@ Here are the ports and corresponding URLs for the services within your Gitpod en
 
 {" "}
 
-<MdxImage
+<Image
   src={GitpodPorts}
   alt="Gitpod Ports tab"
   quality="100"
@@ -209,7 +204,7 @@ These URLs and port numbers represent various services and endpoints within your
 
 1. After clicking the one-click setup button, you will be redirected to the Github Codespaces page. Review the configuration and click on the 'Create Codespace' button to create a new Codespace.
 
-<MdxImage
+<Image
   src={GithubCodespaceNew}
   alt="New Github Codespace"
   quality="100"
@@ -218,7 +213,7 @@ These URLs and port numbers represent various services and endpoints within your
 
 2. This will start loading the Codespace. Keep in mind this might take a few minutes to complete depending on your internet connection and the instance availability.
 
-<MdxImage
+<Image
   src={GithubCodespaceLoading}
   alt="Loading Github Codespace"
   quality="100"
@@ -247,7 +242,7 @@ These URLs and port numbers represent various services and endpoints within your
 
 5. Right next to the Terminal, you will see a **Ports** tab, click on it to see the ports and their respective URLs. Now access the Forwarded Address for port 3000 and you should be able to visit your Formbricks App!
 
-<MdxImage
+<Image
   src={GithubCodespacePorts}
   alt="Github Codespace Ports"
   quality="100"
@@ -340,12 +335,6 @@ pnpm go
 - Demo App at [http://localhost:3002](http://localhost:3002)
 - Landing Page at [http://localhost:3001](http://localhost:3001)
 
-<Note>
-  **WSL2 users**: If you encounter connection issues with Prisma, ensure your WSL2 instance's PostgreSQL
-  service is stopped before running `pnpm go`. Use the command `sudo systemctl stop postgresql` to stop the
-  service.
-</Note>
-
 **You can now access the Formbricks app on [http://localhost:3000](http://localhost:3000)**. You will be automatically redirected to the login. To use your local installation of formbricks, create a new account.
 
 {" "}

apps/formbricks-com/app/docs/contributing/troubleshooting/page.mdx

@@ -1,8 +1,8 @@
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import ClearAppData from "./clear-app-data.webp";
-import Logout from "./logout.webp";
 import UncaughtPromise from "./uncaught-promise.webp";
+import Logout from "./logout.webp";
 
 export const metadata = {
   title: "Formbricks Troubleshooting Guide: How to Solve & Debug Common Issues",
@@ -20,7 +20,7 @@ Here you'll find help with frequently recurring problems
 
 This can happen but fear not, the fix is easy: Delete the application storage of your browser and reload the page. This will force the app to re-fetch the data from the server:
 
-<MdxImage
+<Image
   src={ClearAppData}
   alt="Demo App Preview"
   quality="100"
@@ -34,7 +34,6 @@ If nothing helps, run `pnpm clean` and then `pnpm i` again. This solves a lot.
 ## "I get a full-screen error with cryptic strings"
 
 This usually happens when the Formbricks Widget wasn't correctly or completely built.
-
 <Col>
 <CodeGroup title="Build js library first and then run again">
 
@@ -50,7 +49,6 @@ pnpm dev
 ## My machine struggles with the repository
 
 Since we're working with a monorepo structure, the repository can get quite big. If you're having trouble working with the repository, try the following:
-
 <Col>
 <CodeGroup title="Only run the required project">
 
@@ -72,7 +70,7 @@ However, in our experience it's better to run `pnpm dev` than having two termina
 
 ## Uncaught (in promise) SyntaxError: Unexpected token !DOCTYPE ... is not valid JSON
 
-<MdxImage
+<Image
   src={UncaughtPromise}
   alt="Uncaught promise"
   quality="100"
@@ -81,4 +79,4 @@ However, in our experience it's better to run `pnpm dev` than having two termina
 
 This happens when you're using the Demo App and delete the Person within the Formbricks app which the widget is currently connected with. We're fixing it, but you can also just logout your test person and reload the page to get rid of it.
 
-<MdxImage src={Logout} alt="Logout Person" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+<Image src={Logout} alt="Logout Person" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />

apps/formbricks-com/app/docs/getting-started/framework-guides/page.mdx

@@ -1,5 +1,5 @@
 import { Libraries } from "@/components/docs/Libraries";
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import SetupChecklist from "./env-id.webp";
 import ReactApp from "./react-in-app-survey-app-popup-form.webp";
@@ -28,7 +28,7 @@ Before getting started, make sure you have:
 1. A web application in your desired framework is set up and running.
 2. A Formbricks account with access to your environment ID and API host. You can find these in the **Setup Checklist** in the Settings:
 
-<MdxImage
+<Image
   src={SetupChecklist}
   alt="Step 2 - Setup Checklist"
   quality="100"
@@ -76,7 +76,7 @@ Install the Formbricks SDK using one of the package managers ie `npm`,`pnpm`,`ya
 <Col>
 <CodeGroup title="Install Formbricks JS library">
 ```shell {{ title: 'npm' }}
-npm install @formbricks/js
+npm install --save @formbricks/js
 ```
 ```shell {{ title: 'pnpm' }}
 pnpm add @formbricks/js
@@ -99,6 +99,7 @@ if (typeof window !== "undefined") {
   formbricks.init({
     environmentId: "<environment-id>",
     apiHost: "<api-host>",
+    debug: true, // remove when in production
   });
 }
 
@@ -128,9 +129,9 @@ export default App;
 
 The app initializes 'formbricks' when it's loaded in a browser environment (due to the typeof window !== "undefined" check) and then renders your components or content.
 
-<MdxImage
+<Image
   src={ReactApp}
-  alt="In-app survey in React app for micro surveys"
+  alt="In app survey in React app for micro surveys"
   quality="100"
   className="max-w-full rounded-lg sm:max-w-3xl"
 />
@@ -153,7 +154,7 @@ Code snippets for the integration for both conventions are provided to further a
 <Col>
 <CodeGroup title="Install Formbricks JS library">
 ```shell {{ title: 'npm' }}
-npm install  @formbricks/js
+npm install --save @formbricks/js
 ```
 ```shell {{ title: 'pnpm' }}
 pnpm add @formbricks/js
@@ -181,6 +182,7 @@ useEffect(() => {
 formbricks.init({
 environmentId: "<environment-id>",
 apiHost: "<api-host>",
+debug: true, // remove when in production
 });
 }, []);
 
@@ -230,6 +232,7 @@ if (typeof window !== "undefined") {
   formbricks.init({
     environmentId: "<environment-id>",
     apiHost: "<api-host>",
+    debug: true, // remove when in production
   });
 }
 
@@ -266,6 +269,14 @@ Refer to our [Example NextJS Pages Directory project](https://github.com/formbri
   </Property>
 </Properties>
 
+### Optional Customizations to be Made
+
+<Properties>
+  <Property name="debug" type="boolean">
+    Whether you want to see debug messages from Formbricks on your client-side console.
+  </Property>
+</Properties>
+
 ### What are we doing here?
 
 First we need to initialize the Formbricks SDK, making sure it only runs on the client side.
@@ -283,7 +294,7 @@ We will make sure the SDK is only loaded and used on the client side, as it's no
 <Col>
 <CodeGroup title="Install Formbricks JS library">
 ```shell {{ title: 'npm' }}
-npm install  @formbricks/js
+npm install --save @formbricks/js
 ````
 
 ```shell {{ title: 'pnpm' }}
@@ -347,13 +358,21 @@ router.afterEach((to, from) => {
   </Property>
 </Properties>
 
+### Optional Customizations to be Made
+
+<Properties>
+  <Property name="debug" type="boolean">
+    Whether you want to see debug messages from Formbricks on your client-side console.
+  </Property>
+</Properties>
+
 Refer to our [Example VueJs project](https://github.com/formbricks/examples/tree/main/vuejs) for more help! Now visit the [Validate your Setup](#validate-your-setup) section to verify your setup!
 
 ## Validate your setup
 
 Once you have completed the steps above, you can validate your setup by checking the **Setup Checklist** in the Settings. Your widget status indicator should go from this:
 
-<MdxImage
+<Image
   src={WidgetNotConnected}
   alt="Widget isnt connected"
   quality="100"
@@ -362,7 +381,7 @@ Once you have completed the steps above, you can validate your setup by checking
 
 To this:
 
-<MdxImage
+<Image
   src={WidgetConnected}
   alt="Widget is connected"
   quality="100"
@@ -377,9 +396,10 @@ Enabling Formbricks debug mode in your browser is a useful troubleshooting step
 
 To activate Formbricks debug mode:
 
-1. **Via URL Parameter:**
+1. **In Your Integration Code:**
 
-   - Enable debug mode mode by adding `?formbricksDebug=true` to your application's URL (e.g. `https://example.com?formbricksDebug=true` or `https://example.com?page=123&formbricksDebug=true`). This parameter will enable debugging for the current page.
+   - Locate the initialization code for Formbricks in your application (HTML, ReactJS, NextJS, VueJS).
+   - Set the `debug` option to `true` when initializing Formbricks.
 
 2. **View Debug Logs:**
 
@@ -393,21 +413,29 @@ To activate Formbricks debug mode:
      - **Safari:** Press `Option + Command + C` to open the developer tools and navigate to the "Console" tab.
      - **Edge:** Press `F12` or right-click, select "Inspect Element," and go to the "Console" tab.
 
+3. **Via URL Parameter:**
+
+   - For quick activation, add `?formbricksDebug=true` to your application's URL.
+
+   This parameter will enable debugging for the current session.
+
 ### Common Use Cases
 
 Debug mode is beneficial for scenarios such as:
 
-- Verifying Formbricks initialization.
-- Identifying survey trigger issues.
+- Verifying Formbricks functionality.
+- Identifying integration issues.
 - Troubleshooting unexpected behavior.
 
 ### Debug Log Messages
 
-Debug log messages provide insights into:
+Specific debug log messages may provide insights into:
 
 - API calls and responses.
-- Event tracking, survey triggers and form interactions.
-- Initialization errors.
+- Event tracking and form interactions.
+- Integration errors.
+
+**Note:** Disable debugging in production to prevent unnecessary logs and improve performance.
 
 ## Overwrite CSS Styles for In-App Surveys
 

apps/formbricks-com/app/docs/getting-started/quickstart-in-app-survey/page.mdx

@@ -1,6 +1,5 @@
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
-import ReactApp from "../framework-guides/react-in-app-survey-app-popup-form.webp";
 import I1 from "./1-in-app-survey-or-popup-survey-setup.webp";
 import I2 from "./2-settings-for-survey-popup-in-app-for-feedback.webp";
 import I3 from "./3-web-app-survey-settings-for-in-app-survey-popup.webp";
@@ -9,6 +8,7 @@ import I5 from "./5-options-survey-popup-in-app-for-feedback.webp";
 import I6 from "./6-setup-in-app-survey-popup-feedback-box.webp";
 import I7 from "./7-in-app-survey-popup-for-feedback.webp";
 import I8 from "./8-pop-up-form-in-web-app-survey.webp";
+import ReactApp from "../framework-guides/react-in-app-survey-app-popup-form.webp";
 
 export const metadata = {
   title: "Formbricks Quickstart Guide: In-App Surveys Made Simple",
@@ -20,15 +20,15 @@ export const metadata = {
 
 # Quickstart
 
-In-app surveys have 6-10x better conversion rates than emailed out surveys. This tutorial explains how to run an in-app survey in your web app in 10 to 15 minutes. Let’s go!
+In app surveys have 6-10x better conversion rates than emailed out surveys. This tutorial explains how to run an in app survey in your web app in 10 to 15 minutes. Let’s go!
 
 ## Create a free Formbricks Cloud account
 
 While you can [self-host](/docs/self-hosting/deployment) Formbricks, the quickest and easiest way to get started is with the free Cloud plan. Just [sign up here](https://app.formbricks.com/auth/signup) and click through the onboarding, until you’re here:
 
-<MdxImage
+<Image
   src={I1}
-  alt="Choose in-app survey template"
+  alt="Choose in app survey template"
   quality="100"
   className="max-w-full rounded-lg sm:max-w-3xl "
 />
@@ -37,7 +37,7 @@ While you can [self-host](/docs/self-hosting/deployment) Formbricks, the quickes
 
 To be able to see a survey in your app, you need to create one. We’ll choose one of the templates and head over to the survey settings:
 
-<MdxImage
+<Image
   src={I2}
   alt="Settings for popup survey inside web app"
   quality="100"
@@ -48,7 +48,7 @@ As you can see in the orange note here, we have not yet connected Formbricks Clo
 
 Select “Web App” in the How to ask settings:
 
-<MdxImage
+<Image
   src={I3}
   alt="Survey settings for popup micro surve"
   quality="100"
@@ -57,25 +57,25 @@ Select “Web App” in the How to ask settings:
 
 Scroll down to Survey Trigger and choose “New Session”. This will cause this survey to appear when the Formbricks Widget tracks a new user session:
 
-<MdxImage
+<Image
   src={I4}
-  alt="In-app survey trigger for feedback popup micro survey"
+  alt="In app survey trigger for feedback popup micro survey"
   quality="100"
   className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 In **Recontact Options** we choose the following settings, so that we can play around with the survey more easily. By default, each survey will be shown only once to each user to prevent survey fatigue:
 
-<MdxImage
+<Image
   src={I5}
-  alt="Options for survey popup in-app micro survey"
+  alt="Options for survey popup in app micro survey"
   quality="100"
   className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 Now hit **Publish** and you’ll be forwarded to the Summary Page. This is where you’ll find the responses to this survey. On the Summary Page click through to the Setup Checklist:
 
-<MdxImage
+<Image
   src={I6}
   alt="pop up survey settings for inapp web survey"
   quality="100"
@@ -86,9 +86,9 @@ Now hit **Publish** and you’ll be forwarded to the Summary Page. This is where
 
 On the Setup Checklist you have two elements. At the top you find the Widget Status Indicator. Once your app is connected to Formbricks Cloud successfully, this will turn green:
 
-<MdxImage
+<Image
   src={I7}
-  alt="feedback popup in-app survey"
+  alt="feedback popup in app survey"
   quality="100"
   className="max-w-full rounded-lg sm:max-w-3xl"
 />
@@ -98,9 +98,9 @@ In the manual below, this code snippet contains all the information you need:
 - The **Environment ID** of your current Formbricks workspace
 - The **API Host** which is ‘https://app.formbricks.com’ for Cloud users
 
-<MdxImage
+<Image
   src={I8}
-  alt="settings for in-app survey popping up"
+  alt="settings for in app survey popping up"
   quality="100"
   className="max-w-full rounded-lg sm:max-w-3xl"
 />
@@ -120,9 +120,9 @@ In a local instance of your app, you'll embed the Formbricks Widget. Dependent o
 
 Now, restart your app in your terminal to make sure the widget is loaded. Once its loaded, open the browser console to see the Formbricks debug logs. If you did everything right, you should now see your survey in the lower right corner:
 
-<MdxImage
+<Image
   src={ReactApp}
-  alt="In-app survey in React app for micro surveys"
+  alt="In app survey in React app for micro surveys"
   quality="100"
   className="max-w-full rounded-lg sm:max-w-3xl"
 />

apps/formbricks-com/app/docs/getting-started/troubleshooting/page.mdx

@@ -1,4 +1,4 @@
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import I1 from "./1-set-up-in-app-micro-survey-popup.webp";
 import I2 from "./2-micro-survey-pop-up-in-app.webp";
@@ -20,9 +20,9 @@ In case you don’t see your survey right away, here's what you can do. Go throu
 
 Go back to [app.formbricks.com](http://app.formbricks.com) or your self-hosted instance's URL and go to the Setup Checklist in the Settings. If the status is still indicated as “Not connected” your app hasn't yet pinged the Formbricks Cloud:
 
-<MdxImage
+<Image
   src={I1}
-  alt="setup checklist ui of survey popup for in-app surveys"
+  alt="setup checklist ui of survey popup for in app surveys"
   quality="100"
   className="max-w-full rounded-lg sm:max-w-3xl"
 />
@@ -37,9 +37,9 @@ Go back to [app.formbricks.com](http://app.formbricks.com) or your self-hosted i
 
 If your app is connected with Formbricks Cloud, the survey might have not been loaded properly. Check the debug logs and search for the list of surveys loaded. It should look like so:
 
-<MdxImage
+<Image
   src={I3}
-  alt="survey logs for in-app survey pop up micro"
+  alt="survey logs for in app survey pop up micro"
   quality="100"
   className="max-w-full rounded-lg sm:max-w-3xl"
 />
@@ -48,9 +48,9 @@ If your app is connected with Formbricks Cloud, the survey might have not been l
 
 The widget only loads surveys which are **public** and **in progress**. Go to Formbricks Cloud and to the Survey Summary page. Check if your survey is live:
 
-<MdxImage
+<Image
   src={I2}
-  alt="ui of survey popup for in-app micro surveys"
+  alt="ui of survey popup for in app micro surveys"
   quality="100"
   className="max-w-full rounded-lg sm:max-w-3xl"
 />

apps/formbricks-com/app/docs/in-app-surveys/advanced-targeting/page.mdx

@@ -1,97 +0,0 @@
-import { MdxImage } from "@/components/shared/MdxImage";
-
-import GermansGpt from "./germans-gpt.webp";
-import Hni from "./hni.webp";
-import PowerUsers from "./power-users.webp";
-import RideHailing from "./ride-hailing.webp";
-import UpsellMiro from "./upsell-miro.webp";
-
-export const metadata = {
-  title: "Advanced Targeting in Surveys | Formbricks",
-  description:
-    "Advanced Targeting allows you to show surveys to just the right group of people. You can target surveys based on user attributes, user events, metadata , literally anything! This helps you get more relevant feedback and make data-driven decisions. All of this without writing a single line of code.",
-};
-
-#### In-App Surveys
-
-# Advanced Targeting
-
-Advanced Targeting allows you to show surveys to the right group of people. You can target surveys based on user attributes, user events, and more instead of spraying and praying. This helps you get more relevant feedback and make data-driven decisions. All of this without writing a single line of code.
-
-<iframe
-  width="700"
-  height="450"
-  src="https://www.youtube.com/embed/0BQp6N4cXzU?si=gyeEZRXZ6Kei1zzm"
-  title="YouTube video player: Formbricks"
-  frameborder="0"
-  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"></iframe>
-
-## How to setup Advanced Targeting
-
-<Note>
-  Advanced Targeting is available on the Pro plan! Don't worry, you just need to enter your credit card
-  details to start the freemium plan.
-</Note>
-
-1. On the Formbricks dashboard, click on **People & Segments** tab from the top navigation bar.
-
-2. Switch to the **Segments** tab & click on **Create Segment**.
-
-3. Give your segment a title & a description to help you remember what this segment is about.
-
-4. Now click on the **Add Filter** button to add a filter. You can filter based on actions, user attributes, other segments, devices, and more.
-
-5. To group a set of filters together, click on the Three Dots icon on the right side of the filter and click on **Create Group**.
-
-6. Try playing around with different filters & conditions that we have provided to see how the segment size changes.
-
-7. Once you are happy with the segment, click on **Save Segment**.
-
-8. Now, when you create a survey, you can select this segment to target your survey to.
-
-## Examples:
-
-1. Let's say you want to upsell to: Miro, Loom, Figma, Slack and Asana.
-
-   <MdxImage
-     src={UpsellMiro}
-     alt="Upselling Opportunity"
-     quality="100"
-     className="max-w-full rounded-lg sm:max-w-3xl"
-   />
-
-2. Post-experience surveying for a ride hailing app where users who have taken more than 1 ride are shown a survey.
-
-   <MdxImage
-     src={RideHailing}
-     alt="Ride Hailing Targeting"
-     quality="100"
-     className="max-w-full rounded-lg sm:max-w-3xl"
-   />
-
-3. Target High Value users who have $100k+ in their bank account, own 20+ stocks, and have are an active user.
-
-   <MdxImage
-     src={Hni}
-     alt="Target Active High Net Worth Individuals"
-     quality="100"
-     className="max-w-full rounded-lg sm:max-w-3xl"
-   />
-
-4. Target Germans on mobile phones who have regenerated chatGPT answers frequently in the last quarter and did so today.
-
-   <MdxImage
-     src={GermansGpt}
-     alt="Target Germans on Mobile Phones who have regenerated chatGPT answers frequently in the last quarter and did so today"
-     quality="100"
-     className="max-w-full rounded-lg sm:max-w-3xl"
-   />
-
-5. Sneak Peak: How we at Formbricks automate inviting power users to chat with us
-
-   <MdxImage
-     src={PowerUsers}
-     alt="Automate inviting power users to chat with us at Formbricks"
-     quality="100"
-     className="max-w-full rounded-lg sm:max-w-3xl"
-   />

apps/formbricks-com/app/docs/integrations/airtable/page.mdx

@@ -1,18 +1,17 @@
-import { Callout } from "@/components/shared/Callout";
 import { Fence } from "@/components/shared/Fence";
-import { MdxImage } from "@/components/shared/MdxImage";
-
-import AirtableConnected from "./airtable-connected.webp";
-import ConnectWithAirtable from "./connect-with-airtable.webp";
-import CreateNewIntegration from "./create-new-integration.webp";
-import DeleteIntegration from "./deleteIntegration.webp";
+import { Callout } from "@/components/shared/Callout";
 import IntegrationTab from "./integrations-tab.webp";
+import ConnectWithAirtable from "./connect-with-airtable.webp";
+import AirtableConnected from "./airtable-connected.webp";
 import LinkSurveyWithTable from "./link-survey-with-table.webp";
 import LinkWithQuestions from "./link-with-questions.webp";
 import ListLinkedSurveys from "./list-linked-surveys.webp";
 import OpenDeveloperHub from "./open-developer-hub.webp";
+import CreateNewIntegration from "./create-new-integration.webp";
 import RegisterNewIntegration from "./register-new-integration.webp";
 import SelectScopes from "./select-scopes.webp";
+import DeleteIntegration from "./deleteIntegration.webp";
+import Image from "next/image";
 
 export const metadata = {
   title: "Airtable Setup",
@@ -34,7 +33,7 @@ The Airtable integration allows you to automatically send responses to an Airtab
 
 1. Go to the Integrations tab in your [Formbricks Cloud dashboard](https://app.formbricks.com/) and click on the "Connect" button under Airtable integration.
 
-<MdxImage
+<Image
   src={IntegrationTab}
   alt="Formbricks Integrations Tab"
   quality="100"
@@ -43,7 +42,7 @@ The Airtable integration allows you to automatically send responses to an Airtab
 
 2. Now click on the "Connect with Airtable" button to authenticate yourself with Airtable.
 
-<MdxImage
+<Image
   src={ConnectWithAirtable}
   alt="Connect Formbricks with Airtable"
   quality="100"
@@ -52,7 +51,7 @@ The Airtable integration allows you to automatically send responses to an Airtab
 
 3. You will now be taken to a page where you need to add and grant access to the base you want to use for the integration.
 
-<MdxImage
+<Image
   src={ConnectWithAirtable}
   alt="Add and grant access to airtable base"
   quality="100"
@@ -61,7 +60,7 @@ The Airtable integration allows you to automatically send responses to an Airtab
 
 4. Once you add and grant access to your base, you will be taken back to Formbricks Cloud and see the connected status as below:
 
-<MdxImage
+<Image
   src={AirtableConnected}
   alt="Formbricks is now connected with Google"
   quality="100"
@@ -76,7 +75,7 @@ Before the next step, make sure that you have a Formbricks Survey with at least
 
 6. Now click on the "Link New Table" button to link a new Airtable with Formbricks and a modal will open up.
 
-<MdxImage
+<Image
   src={LinkSurveyWithTable}
   alt="Link Formbricks with a Airtable"
   quality="100"
@@ -85,7 +84,7 @@ Before the next step, make sure that you have a Formbricks Survey with at least
 
 7. Select the Base and table you want to link with Formbricks and the Survey. On doing so, you will be asked with what questions' responses you want to feed in Airtable. Select the questions and click on the "Save" button.
 
-<MdxImage
+<Image
   src={LinkWithQuestions}
   alt="Select question to link with Airtable"
   quality="100"
@@ -95,7 +94,7 @@ Before the next step, make sure that you have a Formbricks Survey with at least
 
 8. On submitting, the modal will close and you will see the linked table in the list of linked tables.
 
-<MdxImage
+<Image
   src={ListLinkedSurveys}
   alt="List of linked tables"
   quality="100"
@@ -114,7 +113,7 @@ Enabling the Airtable Integration in a self-hosted environment requires creating
 
 2. Click on user icon on top left and open to Developer hub
 
-<MdxImage
+<Image
   src={OpenDeveloperHub}
   alt="List of linked tables"
   quality="100"
@@ -123,7 +122,7 @@ Enabling the Airtable Integration in a self-hosted environment requires creating
 
 3. Navigate to OAuth integrations and click on **Register an OAuth integrations**
 
-<MdxImage
+<Image
   src={CreateNewIntegration}
   alt="List of linked tables"
   quality="100"
@@ -132,7 +131,7 @@ Enabling the Airtable Integration in a self-hosted environment requires creating
 
 3. Select a name for you integration and also add a redirect URL which will be YOUR_WEBAPP_URL/api/v1/integrations/airtable/callback
 
-   <MdxImage
+   <Image
      src={RegisterNewIntegration}
      alt="List of linked tables"
      quality="100"
@@ -149,7 +148,7 @@ Enabling the Airtable Integration in a self-hosted environment requires creating
 
 {" "}
 
-<MdxImage
+<Image
   src={SelectScopes}
   alt="List of linked tables"
   quality="100"
@@ -175,7 +174,7 @@ To remove the integration with Airtable,
 3. Click on the "Connected with `<your-email-here`>" just before the "Link new Table" button.
 4. It will now ask for a confirmation to remove the integration. Click on the "Delete" button to remove the integration. You can always come back and connect again with the same Airtable Account.
 
-<MdxImage
+<Image
   src={DeleteIntegration}
   alt="Delete Airtable Integration with Formbricks"
   quality="100"

apps/formbricks-com/app/docs/integrations/google-sheets/page.mdx

@@ -1,14 +1,13 @@
-import { Callout } from "@/components/shared/Callout";
 import { Fence } from "@/components/shared/Fence";
-import { MdxImage } from "@/components/shared/MdxImage";
-
-import ConnectWithGoogle from "./connect-with-google.webp";
-import DeleteConnection from "./delete-connection.webp";
-import GoogleConnected from "./google-connected.webp";
+import { Callout } from "@/components/shared/Callout";
 import IntegrationTab from "./integrations-tab.webp";
+import ConnectWithGoogle from "./connect-with-google.webp";
+import GoogleConnected from "./google-connected.webp";
 import LinkSurveyWithSheet from "./link-survey-with-sheet.webp";
 import LinkWithQuestions from "./link-with-questions.webp";
 import ListLinkedSurveys from "./list-linked-surveys.webp";
+import DeleteConnection from "./delete-connection.webp";
+import Image from "next/image";
 
 export const metadata = {
   title: "Google Sheets",
@@ -31,7 +30,7 @@ The Google Sheets integration allows you to automatically send responses to a Go
 
 1. Go to the Integrations tab in your [Formbricks Cloud dashboard](https://app.formbricks.com/) and click on the "Connect" button under Google Sheets integration.
 
-<MdxImage
+<Image
   src={IntegrationTab}
   alt="Formbricks Integrations Tab"
   quality="100"
@@ -40,7 +39,7 @@ The Google Sheets integration allows you to automatically send responses to a Go
 
 2. Now click on the "Connect with Google" button to authenticate yourself with Google.
 
-<MdxImage
+<Image
   src={ConnectWithGoogle}
   alt="Connect Formbricks with your Google"
   quality="100"
@@ -51,7 +50,7 @@ The Google Sheets integration allows you to automatically send responses to a Go
 
 4. Once you have selected the account and completed the authentication process, you will be taken back to Formbricks Cloud and see the connected status as below:
 
-<MdxImage
+<Image
   src={GoogleConnected}
   alt="Formbricks is now connected with Google"
   quality="100"
@@ -66,7 +65,7 @@ Before the next step, make sure that you have a Formbricks Survey with at least
 
 5. Now click on the "Link New Sheet" button to link a new Google Sheet with Formbricks and a modal will open up.
 
-<MdxImage
+<Image
   src={LinkSurveyWithSheet}
   alt="Link Formbricks with a Google Sheet"
   quality="100"
@@ -75,7 +74,7 @@ Before the next step, make sure that you have a Formbricks Survey with at least
 
 6. Select the Google Sheet you want to link with Formbricks and the Survey. On doing so, you will be asked with what questions' responses you want to feed in the Google Sheet. Select the questions and click on the "Link Sheet" button.
 
-<MdxImage
+<Image
   src={LinkWithQuestions}
   alt="Select question to link with Google Sheet"
   quality="100"
@@ -84,7 +83,7 @@ Before the next step, make sure that you have a Formbricks Survey with at least
 
 7. On submitting, the modal will close and you will see the linked Google Sheet in the list of linked Google Sheets.
 
-<MdxImage
+<Image
   src={ListLinkedSurveys}
   alt="List of linked Google Sheets"
   quality="100"
@@ -139,11 +138,11 @@ Voila! You have successfully enabled the Google Sheets integration in your self-
 To remove the integration with Google Account,
 
 1. Visit the Integrations tab in your Formbricks Cloud dashboard.
-2. Select "Manage Sheets" button in the Google Sheets card.
-3. Click on the "Delete Integration" button.
+2. Select "Manage" button in the Google Sheets card.
+3. Click on the "Connected with `<your-email-here`>" just before the "Link new Sheet" button.
 4. It will now ask for a confirmation to remove the integration. Click on the "Delete" button to remove the integration. You can always come back and connect again with the same Google Account.
 
-<MdxImage
+<Image
   src={DeleteConnection}
   alt="Delete Google Integration with Formbricks"
   quality="100"

apps/formbricks-com/app/docs/integrations/make/page.mdx

@@ -1,23 +1,22 @@
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
-import AddModule from "./add-module.webp";
-import CreateNewScenario from "./create-new-scenario.webp";
-import CreateWebhook from "./create-webhook.webp";
-import DuplicateSurvey from "./duplicate-survey.webp";
-import EnterApiKey from "./enter-api-key.webp";
-import Result from "./result.webp";
-import SearchFormbricks from "./search-formbricks.webp";
-import SelectAction from "./select-action.webp";
-import SelectFields from "./select-fields.webp";
-import SelectSurvey from "./select-survey.webp";
-import SelectTriggers from "./select-trigger.webp";
-import SubmitTestResponse from "./submit-test-response.webp";
 import UpdateQuestionId from "./update-question-id.webp";
+import DuplicateSurvey from "./duplicate-survey.webp";
+import CreateNewScenario from "./create-new-scenario.webp";
+import SearchFormbricks from "./search-formbricks.webp";
+import SelectTriggers from "./select-trigger.webp";
+import CreateWebhook from "./create-webhook.webp";
+import EnterApiKey from "./enter-api-key.webp";
+import SelectSurvey from "./select-survey.webp";
+import SubmitTestResponse from "./submit-test-response.webp";
+import AddModule from "./add-module.webp";
+import SelectFields from "./select-fields.webp";
+import Result from "./result.webp";
+import SelectAction from "./select-action.webp";
 
 export const metadata = {
   title: "Formbricks Integration with Make.com: A Step-by-Step Guide",
-  description:
-    "Discover how to seamlessly integrate Formbricks with Make.com. Dive into our comprehensive guide to set up scenarios, connect with a plethora of apps, and send your survey data to more than 1000 platforms.",
+  description: "Discover how to seamlessly integrate Formbricks with Make.com. Dive into our comprehensive guide to set up scenarios, connect with a plethora of apps, and send your survey data to more than 1000 platforms.",
 };
 
 #### Integrations
@@ -27,7 +26,8 @@ export const metadata = {
 Make is a powerful tool to send information between Formbricks and thousands of apps. Here's how to set it up.
 
 <Note>
-  ### Nail down your survey first ? Any changes in the survey cause additional work in the _Scenario_. It
+  ### Nail down your survey first ? 
+  Any changes in the survey cause additional work in the _Scenario_. It
   makes sense to first settle on the survey you want to run and then get to setting up Make.
 </Note>
 
@@ -35,23 +35,24 @@ Make is a powerful tool to send information between Formbricks and thousands of
 
 Set up the `questionId`s of your survey questions before publishing.
 
-<MdxImage
+<Image
   src={UpdateQuestionId}
   alt="Update Question ID"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 _Update the Question ID field in every question card under Advanced Settings._
 
 <Note>
-  ### Already published? Duplicate survey You can only update the questionId before publishing the survey. If
+  ### Already published? Duplicate survey 
+  You can only update the questionId before publishing the survey. If
   already published, simply duplicate it.
-  <MdxImage
+  <Image
     src={DuplicateSurvey}
     alt="Duplicate Survey"
     quality="100"
-    className="max-w-full rounded-lg sm:max-w-3xl"
+    className="rounded-lg max-w-full sm:max-w-3xl"
   />
 </Note>
 
@@ -59,97 +60,77 @@ _Update the Question ID field in every question card under Advanced Settings._
 
 Visit [Make.com](https://make.com) to start a new scenario.
 
-<MdxImage
+<Image
   src={CreateNewScenario}
   alt="Create New Scenario"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 Search for `Formbricks`:
 
-<MdxImage
+<Image
   src={SearchFormbricks}
   alt="Search Formbricks"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 Choose the event to trigger the Scenario:
 
-<MdxImage
+<Image
   src={SelectTriggers}
   alt="Select Triggers"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 ## Step 3: Connect Formbricks with Make
 
 Click "Create a webhook":
 
-<MdxImage
+<Image
   src={CreateWebhook}
   alt="Create Webhook"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 Enter the Formbricks API key. Learn how to get one from the [API Key tutorial](/docs/api/management/api-key-setup).
 
-<MdxImage
-  src={EnterApiKey}
-  alt="Enter API Key"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={EnterApiKey} alt="Enter API Key" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 ## Step 4: Select Survey
 
 Choose from your created surveys:
 
-<MdxImage
-  src={SelectSurvey}
-  alt="Select Survey"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={SelectSurvey} alt="Select Survey" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 ## Step 5: Send a test response
 
 You need a test response for Make setup. For local Formbricks setup, use the [Demo App](/docs/contributing/demo) to submit a test response.
 
-<MdxImage
+<Image
   src={SubmitTestResponse}
   alt="Submit Test Response"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 ## Step 6: Set up Google Sheet
 
 Decide on the desired action for the data. Here, we'll send submissions to a Google Sheet:
 
-<MdxImage src={AddModule} alt="Add Module" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+<Image src={AddModule} alt="Add Module" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 Choose "Add a Row" for the action:
 
-<MdxImage
-  src={SelectAction}
-  alt="Select Action"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={SelectAction} alt="Select Action" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 Specify the spreadsheet details and match the Formbricks data:
 
-<MdxImage
-  src={SelectFields}
-  alt="Select Fields"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={SelectFields} alt="Select Fields" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 A new row gets added to the spreadsheet for every response:
 
-<MdxImage src={Result} alt="Result" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+<Image src={Result} alt="Result" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />

apps/formbricks-com/app/docs/integrations/n8n/page.mdx

@@ -1,27 +1,26 @@
-import { Callout } from "@/components/shared/Callout";
 import { Fence } from "@/components/shared/Fence";
-import { MdxImage } from "@/components/shared/MdxImage";
+import { Callout } from "@/components/shared/Callout";
+import Image from "next/image";
 
-import AddApiKey from "./add-api-key.png";
-import AddDiscord from "./add-discord.png";
 import AddFormbricksTrigger from "./add-formbricks-trigger.png";
 import CreateNewCredentialBtn from "./create-new-credential-btn.png";
-import DiscordResponse from "./discord-response.png";
+import AddApiKey from "./add-api-key.png";
 import DuplicateSurvey from "./duplicate-survey.png";
-import FillDiscordDetails from "./fill-discord-details.png";
-import ListenForEvent from "./listen-for-event.png";
 import SelectEvent from "./select-event.png";
 import SelectSurvey from "./select-survey.png";
 import SelectedSurveys from "./selected-surveys.png";
+import ListenForEvent from "./listen-for-event.png";
+import TestResponseSuccess from "./test-response-success.png";
+import AddDiscord from "./add-discord.png";
+import FillDiscordDetails from "./fill-discord-details.png";
+import DiscordResponse from "./discord-response.png";
 import SubmitTestResponse from "./submit-test-response.png";
 import SuccessConnection from "./success-connection.png";
-import TestResponseSuccess from "./test-response-success.png";
 import UpdateQuestionId from "./update-question-id.png";
 
 export const metadata = {
   title: "Comprehensive Guide to Integrating Formbricks with n8n",
-  description:
-    "Unlock the potential of combining Formbricks with n8n for a streamlined workflow experience. Dive into our step-by-step guide and send your survey data effortlessly to 350+ applications. Streamline your data processes now!",
+  description: "Unlock the potential of combining Formbricks with n8n for a streamlined workflow experience. Dive into our step-by-step guide and send your survey data effortlessly to 350+ applications. Streamline your data processes now!",
 };
 
 #### Integrations
@@ -31,31 +30,28 @@ export const metadata = {
 n8n allows you to build flexible workflows focused on deep data integration. And with sharable templates and a user-friendly UI, the less technical people on your team can collaborate on them too. Unlike other tools, complexity is not a limitation. So you can build whatever you want — without stressing over budget. Hook up Formbricks with n8n and you can send your data to 350+ other apps. Here is how to do it.
 
 <Note>
-  ### Nail down your survey first Any changes in the survey cause additional work in the n8n node. It makes
-  sense to first settle on the survey you want to run and then get to setting up n8n.
+  ### Nail down your survey first
+  Any changes in the survey cause additional work in the n8n node. It makes sense to first settle on the survey
+  you want to run and then get to setting up n8n.
 </Note>
 
 ## Step 1: Setup your survey incl. `questionId` for every question
 
 When setting up the node your life will be easier when you change the `questionId`s of your survey questions. You can only do so **before** you publish your survey.
 
-<MdxImage
-  src={UpdateQuestionId}
-  alt="Update Question ID"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={UpdateQuestionId} alt="Update Question ID" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 _In every question card in the Advanced Settings you find the Question ID field. Update it so that you'll recognize the response tied to this question._
 
 <Note>
-  ### Already published? Duplicate survey You can only update the questionId when the survey was not yet
-  published. Already published it? Just **duplicate it** to update the questionIds.
-  <MdxImage
+  ### Already published? Duplicate survey
+  You can only update the questionId when the survey was not yet published. Already published it? Just **duplicate
+  it** to update the questionIds.
+  <Image
     src={DuplicateSurvey}
     alt="Duplicate Survey"
     quality="100"
-    className="max-w-full rounded-lg sm:max-w-3xl"
+    className="rounded-lg max-w-full sm:max-w-3xl"
   />
 </Note>
 
@@ -63,49 +59,29 @@ _In every question card in the Advanced Settings you find the Question ID field.
 
 Go to [n8n.io](https://n8n.io) and create a new workflow. Search for “Formbricks” to get started:
 
-<MdxImage
-  src={AddFormbricksTrigger}
-  alt="Add Formbricks Trigger"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={AddFormbricksTrigger} alt="Add Formbricks Trigger" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 ## Step 3: Connect Formbricks with n8n
 
 Now, you have to connect n8n with Formbricks via an API Key:
 
-<MdxImage
-  src={CreateNewCredentialBtn}
-  alt="Create new credential button"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={CreateNewCredentialBtn} alt="Create new credential button" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 Click on Create New Credentail button to add your host and API Key
 
-<MdxImage
-  src={AddApiKey}
-  alt="Add host and api key"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={AddApiKey} alt="Add host and api key" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 Now you need an API key. Please refer to the [API Key Setup](/docs/api/management/api-key-setup) page to learn how to create one.
 
 Once you copied it in the API Key field, hit Save button to test the connection and save the credentials.
 
-<MdxImage
-  src={SuccessConnection}
-  alt="Successful Connection"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={SuccessConnection} alt="Successful Connection" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 ## Step 4: Select Event
 
 Next, you can choose the event you want to trigger the node on. You can select multiple events:
 
-<MdxImage src={SelectEvent} alt="Select Event" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+<Image src={SelectEvent} alt="Select Event" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 Here, we are adding `Response Finished` as an event, which will trigger when the survey has been filled out.
 
@@ -113,50 +89,25 @@ Here, we are adding `Response Finished` as an event, which will trigger when the
 
 Next, you can choose from all the surveys you have created in this environment. You can select multiple surveys:
 
-<MdxImage
-  src={SelectSurvey}
-  alt="Select Survey"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={SelectSurvey} alt="Select Survey" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 Here, we are selecting two surveys.
 
-<MdxImage
-  src={SelectedSurveys}
-  alt="Selected Surveys"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={SelectedSurveys} alt="Selected Surveys" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 ## Step 6: Test your trigger
 
 In order to set up n8n you'll need a test response in the selected survey. This allows you to select the individual values of each response in your workflow. If you have Formbricks running locally and you want to set up an in-app survey, you can use our [Demo App](/docs/contributing/demo) to trigger a survey and submit a response.
 
-<MdxImage
-  src={SubmitTestResponse}
-  alt="Submit Test Response"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={SubmitTestResponse} alt="Submit Test Response" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 Next, click on Listen for event button.
 
-<MdxImage
-  src={ListenForEvent}
-  alt="Listen for event"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={ListenForEvent} alt="Listen for event" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 Then, go to the survey which you selected. Fill it out, and wait for the particular event to trigger (in this case it's `Response Finished`). Once the event is triggered you will see the response that you filled out in the survey.
 
-<MdxImage
-  src={TestResponseSuccess}
-  alt="Test Response Success"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={TestResponseSuccess} alt="Test Response Success" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 Now you have all the data you need at hand. The next steps depend on what you want to do with it. In this tutorial, we will send submissions to a discord channel:
 
@@ -164,22 +115,12 @@ Now you have all the data you need at hand. The next steps depend on what you wa
 
 Click on the plus and search `Discord`.
 
-<MdxImage src={AddDiscord} alt="Add Discord" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+<Image src={AddDiscord} alt="Add Discord" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 Fill in the `Webhook URL` and the `Content` that you want to receive in the respective discord channel. Next, click on `Execute Node` button to test the node.
 
-<MdxImage
-  src={FillDiscordDetails}
-  alt="Fill Discord Details"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={FillDiscordDetails} alt="Fill Discord Details" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 Once the execution is successful, you'll receive the content in the discord channel.
 
-<MdxImage
-  src={DiscordResponse}
-  alt="Discord Response"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={DiscordResponse} alt="Discord Response" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />

apps/formbricks-com/app/docs/integrations/notion/page.mdx

@@ -1,12 +1,11 @@
-import { MdxImage } from "@/components/shared/MdxImage";
-
-import ConnectWithNotion from "./images/connect-with-notion.png";
-import DeleteConnection from "./images/delete-connection.png";
 import IntegrationsTab from "./images/integrations-tab.png";
+import ConnectWithNotion from "./images/connect-with-notion.png";
+import NotionConnected from "./images/notion-connected.png";
 import LinkSurveyWithDatabase from "./images/link-survey-with-database.png";
 import LinkWithDatabases from "./images/link-with-databases.png";
 import ListLinkedDatabases from "./images/list-linked-databases.png";
-import NotionConnected from "./images/notion-connected.png";
+import DeleteConnection from "./images/delete-connection.png";
+import Image from "next/image";
 
 export const metadata = {
   title: "Notion",
@@ -29,7 +28,7 @@ The notion integration allows you to automatically send responses to a Notion da
 
 1. Go to the Integrations tab in your [Formbricks Cloud dashboard](https://app.formbricks.com/) and click on the "Connect" button under Notion integration.
 
-<MdxImage
+<Image
   src={IntegrationsTab}
   alt="Formbricks Integrations Tab"
   quality="100"
@@ -38,7 +37,7 @@ The notion integration allows you to automatically send responses to a Notion da
 
 2. Now click on the "Connect with Notion" button to authenticate yourself with Notion.
 
-<MdxImage
+<Image
   src={ConnectWithNotion}
   alt="Connect Formbricks with your Notion account"
   quality="100"
@@ -49,7 +48,7 @@ The notion integration allows you to automatically send responses to a Notion da
 
 4. Once you have selected the account and databases and completed the authentication and authorization process, you will be taken back to Formbricks Cloud and see the connected status as below:
 
-<MdxImage
+<Image
   src={NotionConnected}
   alt="Formbricks is now connected with Notion"
   quality="100"
@@ -63,7 +62,7 @@ The notion integration allows you to automatically send responses to a Notion da
 
 5. Now click on the "Link New Database" button to link a new Notion database with Formbricks and a modal will open up.
 
-<MdxImage
+<Image
   src={LinkSurveyWithDatabase}
   alt="Link Formbricks with a Notion database"
   quality="100"
@@ -72,7 +71,7 @@ The notion integration allows you to automatically send responses to a Notion da
 
 6. Select the Notion database you want to link with Formbricks and the Survey. On doing so, you will be asked to map formbricks' survey questions with selected databases' column. Complete the mapping and click on the "Link Database" button.
 
-<MdxImage
+<Image
   src={LinkWithDatabases}
   alt="Question to notion database column mapping"
   quality="100"
@@ -81,7 +80,7 @@ The notion integration allows you to automatically send responses to a Notion da
 
 7. On submitting, the modal will close and you will see the linked Notion database in the list of linked Notion databases.
 
-<MdxImage
+<Image
   src={ListLinkedDatabases}
   alt="List of linked notion databases"
   quality="100"
@@ -102,7 +101,7 @@ Enabling the Notion Integration in a self-hosted environment requires a setup us
    - If you are running formbricks locally, you can enter `http://localhost:3000/api/v1/integrations/notion/callback`.
    - Or, you can enter `https://<your-public-facing-url>/api/v1/integrations/notion/callback`
 6. Once you've filled all the necessary details, click on **Submit**.
-7. A screen will appear which will have **Client ID** and **Client secret**. Copy them and set them as the environment variables in your Formbricks instance as:
+7. A screen will appear which will have **Client ID**, **Client secret** and **Authorization URL**. Copy them and set them as the environment variables in your Formbricks instance as:
    - `NOTION_OAUTH_CLIENT_ID` - OAuth Client ID
    - `NOTION_OAUTH_CLIENT_SECRET` - OAuth Client Secret
 
@@ -110,14 +109,14 @@ Voila! You have successfully enabled the Notion integration in your self-hosted
 
 ## Remove Integration with Notion Account
 
-To remove the integration with Slack Workspace,
+To remove the integration with Notion Account,
 
 1. Visit the Integrations tab in your Formbricks Cloud dashboard.
-2. Select "Manage" button in the Slack card.
-3. Click on the "Delete Integration" button.
+2. Select "Manage" button in the Notion card.
+3. Click on the "Connected with `<your-workspace-name-here`> Workspace" just before the "Link new Database" button.
 4. It will now ask for a confirmation to remove the integration. Click on the "Delete" button to remove the integration. You can always come back and connect again with the same Notion Account.
 
-<MdxImage
+<Image
   src={DeleteConnection}
   alt="Delete Notion Integration with Formbricks"
   quality="100"

apps/formbricks-com/app/docs/integrations/slack/page.mdx

@@ -1,168 +0,0 @@
-import { MdxImage } from "@/components/shared/MdxImage";
-
-import ConnectWithSlack from "./images/connect-with-slack.png";
-import DeleteConnection from "./images/delete-connection.png";
-import IntegrationsTab from "./images/integrations-tab.png";
-import LinkSurveyWithChannel from "./images/link-survey-with-channel.png";
-import LinkWithQuestions from "./images/link-with-questions.png";
-import ListLinkedSurveys from "./images/list-linked-surveys.png";
-import SlackAuth from "./images/slack-auth.png";
-import SlackConnected from "./images/slack-connected.png";
-
-export const metadata = {
-  title: "Slack",
-  description:
-    "The slack integration allows you to automatically send responses to a Slack channel of your choice.",
-};
-
-#### Integrations
-
-# Slack
-
-The slack integration allows you to automatically send responses to a Slack channel of your choice.
-
-<Note>
-  This feature is enabled by default in Formbricks Cloud but needs to be self-configured when running a
-  self-hosted version of Formbricks.
-</Note>
-
-## Formbricks Cloud
-
-1. Go to the Integrations tab in your [Formbricks Cloud dashboard](https://app.formbricks.com/) and click on the "Connect" button under Slack integration.
-
-<MdxImage
-  src={IntegrationsTab}
-  alt="Formbricks Integrations Tab"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-2. Now click on the "Connect with Slack" button to authenticate yourself with Slack.
-
-<MdxImage
-  src={ConnectWithSlack}
-  alt="Connect Formbricks with your Slack Workspace"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-3. You will now be taken to the Slack OAuth page where you can select the Slack channel you want to link with Formbricks and click on the "Allow" button.
-
-<MdxImage
-  src={SlackAuth}
-  alt="Slack OAuth Page"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-4. Once you have selected the account and completed the authentication process, you will be taken back to Formbricks Cloud and see the connected status as below:
-
-<MdxImage
-  src={SlackConnected}
-  alt="Formbricks is now connected with Slack"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-<Note>
-  Before the next step, make sure that you have a Formbricks Survey with at least one question and a Slack
-  channel in the Slack workspace you integrated.
-</Note>
-
-5. Now click on the "Link channel" button to link a new Slack channel with Formbricks and a modal will open up.
-
-<MdxImage
-  src={LinkSurveyWithChannel}
-  alt="Link Formbricks with a Slack Channel"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-6. Select the channel you want to link with Formbricks and the Survey. On doing so, you will be asked to select the questions' responses you want to feed in the Slack channel. Select the questions and click on the "Link Channel" button.
-
-<MdxImage
-  src={LinkWithQuestions}
-  alt="Select question to link with Slack Channel"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-7. On submitting, the modal will close and you will see the linked Slack channel in the list of linked Slack channels.
-
-<MdxImage
-  src={ListLinkedSurveys}
-  alt="List of linked Slack Channels"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-Congratulations! You have successfully linked a Slack channel with Formbricks. Now whenever a response is submitted for the linked Survey, it will be automatically sent to the linked Slack channel.
-
-## Setup in self-hosted Formbricks
-
-Enabling the Slack Integration in a self-hosted environment requires a setup using slack workspace account and changing the environment variables of your Formbricks instance.
-
-<Note>
-  If you are running Formbricks locally:
-  
-  You need to use `https` instead of `http` for the redirect URI. 
-  - You can update the `go` script in your `apps/web/package.json` to include the `--experimental-https` flag. The
-  command will look like: <br />
-    ```bash
-      "go": next dev --experimental-https -p 3000
-    ```
-
-- You also need to update the .env file in the `apps/web` directory to include the `NEXTAUTH_URL` and `WEBAPP_URL` as `https://localhost:3000` instead of `http://localhost:3000`.
-
-- You also need to run the terminal in admin mode to run the `go` script(to acquire the SSL certificate). You can do this by running the terminal as an administrator or using the `sudo` command in Unix-based systems.
-
-</Note>
-
-1. Create a Slack workspace if you don't have one already.
-2. Go to the [Your apps](https://api.slack.com/apps) page and **Create New App**.
-3. Click on **From Scratch** and provide the **App Name** and select your workspace in **Pick a workspace to develop your app in:** dropdown. Click on **Create App**.
-4. Go to the **OAuth & Permissions** tab on the sidebar and add the following **Bot Token Scopes**:
-
-   - `channels:read`
-   - `chat:write`
-   - `chat:write.public`
-   - `chat:write.customize`
-
-5. Add the **Redirect URLs** under **OAuth & Permissions** tab. You can add the following URLs:
-
-   - If you are running formbricks locally, you can enter `https://localhost:3000/api/v1/integrations/slack/callback`.
-   - Or, you can enter `https://<your-public-facing-url>/api/v1/integrations/slack/callback`
-
-6. Now, click on **Install to Workspace** and **Allow** the permissions.
-7. Go to the **Basic Information** tab on the sidebar and copy the **Client ID** and **Client Secret**. Copy them and set them as the environment variables in your Formbricks instance as:
-
-- `SLACK_CLIENT_ID` - OAuth Client ID
-- `SLACK_CLIENT_SECRET` - OAuth Client Secret
-
-8. Now, you need to enable the public distribution of your app. Go to the **Basic Information** tab and click on the **Manage distribution** button and click on the "Distribute App".
-9. Scroll down to the **Share your app with other workspaces** section, complete the checklist and click on the **Activate public distribution** button.
-
-### By now, your environment variables should include the below ones:
-
-- `SLACK_CLIENT_ID`
-- `SLACK_CLIENT_SECRET`
-
-Voila! You have successfully enabled the Slack integration in your self-hosted Formbricks instance. Now you can follow the steps mentioned in the [Formbricks Cloud](#formbricks-cloud) section to link a Slack workspace with Formbricks.
-
-## Remove Integration with Slack Workspace
-
-To remove the integration with Slack Workspace,
-
-1. Visit the Integrations tab in your Formbricks Cloud dashboard.
-2. Select "Manage" button in the Slack card.
-3. Click on the "Delete Integration" button.
-4. It will now ask for a confirmation to remove the integration. Click on the "Delete" button to remove the integration. You can always come back and connect again with the same Slack Workspace.
-
-<MdxImage
-  src={DeleteConnection}
-  alt="Delete Slack Integration with Formbricks"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-Still struggling or something not working as expected? [Join our Discord!](https://formbricks.com/discord) and we'd be glad to assist you!

apps/formbricks-com/app/docs/integrations/wordpress/page.mdx

@@ -1,12 +1,12 @@
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import Img1 from "./1-wordpress-targeted-survey-on-website-free.webp";
 import Img2 from "./2-run-website-survey-wordpress-targeted-for-free.webp";
 import Img3 from "./3-wordpress-setup-survey-on-website-targeted-free-open-source.webp";
 import Img4 from "./4-wordpress-website-survey-target-visitor-free.webp";
+import Img5 from "./step-4-copy-to-wordpress-for-free-targeted-survey.webp";
 import Img6 from "./6-targeted-survey-on-wordpress-website-for-free.webp";
 import Img7 from "./7-wordpress-free-hotjar-survey-open-source-website-survey-hotjar.webp";
-import Img5 from "./step-4-copy-to-wordpress-for-free-targeted-survey.webp";
 
 export const metadata = {
   title: "Run targeted surveys on your WordPress page",
@@ -32,7 +32,7 @@ If you want to run a targeted survey on your WordPress website, Formbricks is th
 
 As long as the Formbricks plugin is in review, please download it from our [GitHub repository directly.](https://github.com/formbricks/wordpress)
 
-<MdxImage
+<Image
   src={Img1}
   alt="Run targeted website survye on any WordPress site"
   quality="100"
@@ -45,7 +45,7 @@ This is super straight forward: Go to [app.formbricks.com/auth/signup](https://a
 
 When you see this screen, you’re there:
 
-<MdxImage
+<Image
   src={Img2}
   alt="Free HotJar survey alternative open source"
   quality="100"
@@ -56,7 +56,7 @@ When you see this screen, you’re there:
 
 Go to Settings > Setup Checklist where you’ll find your environmentId:
 
-<MdxImage
+<Image
   src={Img3}
   alt="Run targeted surveys for free on WordPress pages"
   quality="100"
@@ -67,7 +67,7 @@ Go to Settings > Setup Checklist where you’ll find your environmentId:
 
 In your WordPress instance, go to the Formbricks Plugin settings and copy the environmentId in the correct field:
 
-<MdxImage
+<Image
   src={Img5}
   alt="Free and open source HotJar survey on WordPress page"
   quality="100"
@@ -84,7 +84,7 @@ Great!
 
 Now that all is setup, we create a survey to display an example survey. Pick any template here:
 
-<MdxImage
+<Image
   src={Img2}
   alt="Free HotJar survey alternative open source"
   quality="100"
@@ -93,20 +93,22 @@ Now that all is setup, we create a survey to display an example survey. Pick any
 
 Keep the content for now, click on the Settings tab:
 
-<MdxImage
+<Image
   src={Img4}
   alt="Free and open source HotJar survey on WordPress page"
   quality="100"
   className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
+
+
 Here we do three things:
 
 1. Change survey type to “In-App Survey”
 2. Select trigger “New Session”
 3. Publish
 
-<MdxImage
+<Image
   src={Img6}
   alt="Open Source survey on targeted website wordpress"
   quality="100"
@@ -115,7 +117,7 @@ Here we do three things:
 
 When you see this page, you did it!
 
-<MdxImage
+<Image
   src={Img7}
   alt="Run free an open source targeted survey on any page"
   quality="100"
@@ -126,6 +128,6 @@ When you see this page, you did it!
 
 You did it! Reload the WordPress page and your survey should appear!
 
-## Doesn't work?
 
-Join our [Discord to get help 🤓](https://formbricks.com/discord)
+## Doesn't work?
+Join our [Discord to get help 🤓](https://formbricks.com/discord)

apps/formbricks-com/app/docs/integrations/zapier/page.mdx

@@ -1,4 +1,4 @@
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import AddNewZap from "./add-new-zap.webp";
 import ChooseEvent from "./choose-event.webp";
@@ -16,8 +16,7 @@ import ZapierMessage from "./zapier-message.webp";
 
 export const metadata = {
   title: "Step-by-Step Guide to Integrating Formbricks with Zapier",
-  description:
-    "Master the integration of Formbricks with Zapier using our detailed guide. Seamlessly connect your surveys to 5000+ apps, automate data transfers, and enhance feedback management. Start optimizing your workflow today.",
+  description: "Master the integration of Formbricks with Zapier using our detailed guide. Seamlessly connect your surveys to 5000+ apps, automate data transfers, and enhance feedback management. Start optimizing your workflow today.",
 };
 
 #### Integrations
@@ -27,31 +26,33 @@ export const metadata = {
 Zapier is a powerful ally. Hook up Formbricks with Zapier and you can send your data to 5000+ other apps. Here is how to do it.
 
 <Note>
-  ### Nail down your survey first? Any changes in the survey cause additional work in the Zap. It makes sense
-  to first settle on the survey you want to run and then get to setting up Zapier.
+  ### Nail down your survey first? 
+  Any changes in the survey cause additional work in the Zap. It makes sense to first settle on the survey you
+  want to run and then get to setting up Zapier.
 </Note>
 
 ## Step 1: Setup your survey incl. `questionId` for every question
 
 When setting up the Zap your life will be easier when you change the `questionId`s of your survey questions. You can only do so **before** you publish your survey.
 
-<MdxImage
+<Image
   src={UpdateQuestionId}
   alt="Update Question ID"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 _In every question card in the Advanced Settings you find the Question ID field. Update it so that you’ll recognize the response tied to this question._
 
 <Note>
-  ### Already published? Duplicate survey You can only update the questionId when the survey was not yet
-  published. Already published it? Just **duplicate it** to update the questionIds.
-  <MdxImage
+  ### Already published? Duplicate survey 
+  You can only update the questionId when the survey was not yet published. Already published it? Just **duplicate
+  it** to update the questionIds.
+  <Image
     src={DuplicateSurvey}
     alt="Duplicate Survey"
     quality="100"
-    className="max-w-full rounded-lg sm:max-w-3xl"
+    className="rounded-lg max-w-full sm:max-w-3xl"
   />
 </Note>
 
@@ -59,71 +60,66 @@ _In every question card in the Advanced Settings you find the Question ID field.
 
 In order to set up Zapier you’ll need a test response. This allows you to select the individual values of each response in your Zap. If you have Formbricks running locally and you want to set up an in-app survey, you can use our [Demo App](/docs/contributing/demo) to trigger a survey and submit a response.
 
-<MdxImage
+<Image
   src={SubmitTestResponse}
   alt="Submit Test Response"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 ## Step 3: Setup your Zap
 
 Go to [zapier.com](https://zapier.com) and create a new Zap. Search for “Formbricks” to get started:
 
-<MdxImage src={AddNewZap} alt="Add New Zap" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+<Image src={AddNewZap} alt="Add New Zap" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 Then, choose the event you want to trigger the Zap on:
 
-<MdxImage src={ChooseEvent} alt="Choose Event" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+<Image src={ChooseEvent} alt="Choose Event" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 ## Step 4: Connect Formbricks with Zapier
 
 Now, you have to connect Zapier with Formbricks via an API Key:
 
-<MdxImage
+<Image
   src={ConnectWithFB1}
   alt="Connect with Formbricks - 1"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
-<MdxImage
+<Image
   src={ConnectWithFB2}
   alt="Connect with Formbricks - 2"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 Now you need an API key. Please refer to the [API Key Setup](/docs/api/management/api-key-setup) page to learn how to create one.
 
 Once you copied it in the newly opened Zapier window, you will be connected:
 
-<MdxImage
+<Image
   src={SuccessConnection}
   alt="Successful Connection"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 ## Step 5: Select Survey
 
 Next, you can choose from all the surveys you have created in this environment:
 
-<MdxImage
-  src={SelectSurvey}
-  alt="Select Survey"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+<Image src={SelectSurvey} alt="Select Survey" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 ## Step 6: Test your trigger
 
 Once you hit “Test” you will see the three most recent submissions for this survey. If you don’t have any submissions in the survey, submit one to continue setting up your Zap:
 
-<MdxImage
+<Image
   src={TestSubmission}
   alt="Test Submission"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 _Now you're happy that you updated the questionId's_
 
@@ -131,22 +127,22 @@ _Now you're happy that you updated the questionId's_
 
 Now you have all the data you need at hand. The next steps depend on what you want to do with it. In this tutorial, we will send submissions to a Slack channel:
 
-<MdxImage
+<Image
   src={SlackChannelMsg}
   alt="Slack Channel Message"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 In the action itself we can determine the data and layout of the message. Here, we only choose the submission data. You can also refer to the meta data of the submission and the [attributes](/docs/attributes/why) of the person who submitted the survey.
 
-<MdxImage src={SlackMsg} alt="Slack Message" quality="100" className="max-w-full rounded-lg sm:max-w-3xl" />
+<Image src={SlackMsg} alt="Slack Message" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
 
 We now receive a notifcation in our Slack channel whenever a Churn survey is completed:
 
-<MdxImage
+<Image
   src={ZapierMessage}
   alt="Zapier Message"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />

apps/formbricks-com/app/docs/introduction/how-it-works/page.mdx

@@ -1,10 +1,10 @@
-import Analytics from "./analytics.webp";
+import Image from "next/image";
+
 import FormBuilder from "./form-builder.webp";
-import integrations from "./integrations.webp";
 import Targeting from "./targeting.webp";
 import Trigger from "./trigger.webp";
-
-import { MdxImage } from "@/components/shared/MdxImage";
+import integrations from "./integrations.webp";
+import Analytics from "./analytics.webp";
 
 export const metadata = {
   title: "Inside Look: Formbricks In-Product Micro-Surveys",
@@ -29,49 +29,49 @@ Formbricks is a powerful platform designed to help you create and manage in-prod
 
 The Form Builder is where you create and customize your micro-surveys. With its intuitive drag-and-drop interface, you can easily add different question types, set response options, and apply your branding to the survey forms. The Form Builder allows you to preview your survey in real-time, ensuring it looks and feels perfect for your users.
 
-<MdxImage
+<Image
   src={FormBuilder}
   alt="Create & Customize Surveys No Code with Formbricks"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 ## Targeting & Triggers
 
 Formbricks offers fine-grained user targeting and event-based triggers to help you display your surveys to the most relevant audience. Using the platform, you can define user segments based on attributes and behaviors, and set up triggers to show your surveys at specific moments within your product. This ensures that you're capturing the most accurate and valuable feedback possible.
 
-<MdxImage
+<Image
   src={Targeting}
   alt="Targeting & Triggers with Formbricks"
   quality="100"
-  className="w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg w-full sm:max-w-3xl"
 />
 
-<MdxImage
+<Image
   src={Trigger}
   alt="Targeting & Triggers with Formbricks"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 ## Integration
 
 Integrating Formbricks into your web or mobile application is a breeze. With SDKs for popular web frameworks like React, and an HTML snippet for non-framework based websites, you can quickly add Formbricks to your project. The provided code snippets make it easy to initialize the Formbricks widget and configure it to communicate with your backend.
 
-<MdxImage
+<Image
   src={integrations}
   alt="Integrations with Formbricks"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 ## Analytics & Insights
 
 Formbricks provides powerful analytics and insights to help you understand user responses and make data-driven decisions. The platform aggregates survey results and presents them in an easy-to-understand format, enabling you to identify trends, spot issues, and uncover opportunities for improvement. With Formbricks, you're always one step ahead in understanding your users and optimizing your product experience.
 
-<MdxImage
+<Image
   src={Analytics}
   alt="Analytics & Insights with Formbricks"
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
+  className="rounded-lg max-w-full sm:max-w-3xl"
+/>

apps/formbricks-com/app/docs/link-surveys/data-prefilling/page.mdx

@@ -1,11 +1,10 @@
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import QuestionId from "./question-id.webp";
 
 export const metadata = {
   title: "URL Data Prefilling for Link Surveys in Formbricks",
-  description:
-    "Master the art of data prefilling in Formbricks link surveys. Dive into our guide on how to use URL parameters to prepopulate answers, boosting conversion rates and enhancing user experience. Learn through examples and ensure correct validation for each question type.",
+  description: "Master the art of data prefilling in Formbricks link surveys. Dive into our guide on how to use URL parameters to prepopulate answers, boosting conversion rates and enhancing user experience. Learn through examples and ensure correct validation for each question type.",
 };
 
 #### Link Surveys
@@ -23,7 +22,6 @@ URL prefilling of data comes in handy when you:
 - Want to embed the first question in an email and increase conversion by prefilling the choice
 
 ## Quick Example
-
 <Col>
 <CodeGroup title="Example URL">
 
@@ -40,18 +38,19 @@ To prefill the first question of a survey, append `?question_id=answer` at the e
 Please make sure the answer is [URL encoded](https://www.urlencoder.org/).
 
 <Note>
-  ## Prefill only the first question Currently, you can only prefill the first question of a link survey.
+  ## Prefill only the first question 
+  Currently, you can only prefill the first question of a link survey.
 </Note>
 
 ## Where do I find my question Id?
 
 You find the `questionId` in the Advanced Settings at the bottom of each question card in the Survey Editor. As you see, you can update the `questionId` to any string you like. However, once you published your survey, this `questionId` cannot be updated anymore:
 
-<MdxImage
+<Image
   src={QuestionId}
   alt="The question Id is located at the bottom of each question card in the survey editor."
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />
 
 ## Examples
@@ -59,7 +58,6 @@ You find the `questionId` in the Advanced Settings at the bottom of each questio
 Here are a few examples to get you started:
 
 ### Rating Question
-
 <Col>
 <CodeGroup title="Translates to 5 stars / points / emojis">
 

apps/formbricks-com/app/docs/link-surveys/embed-surveys/page.mdx

@@ -1,81 +0,0 @@
-import { TellaVideo } from "@/components/docs/TellaVideo";
-
-export const metadata = {
-  title: "Embed Surveys in Your Web Page",
-  description: "Embed Formbricks surveys seamlessly into your website or web application using an iframe.",
-};
-
-#### Embed Surveys
-
-# Embed Surveys in Your Web Page
-
-Embedding Formbricks surveys directly into your web pages allows you to integrate interactive surveys without redirecting users to a separate survey site. This method ensures a seamless integration and maintains the aesthetic continuity of your website or application.
-
-## How to Use it?
-
-<TellaVideo tellaVideoIdentifier="clvavyy2f00000fjr0mple922"/>
-
-1. Create and publish a link survey.
-
-2. Open survey summary page and click on **share** button on the top right.
-
-3. In the survey share modal, click on **Embed survey** button.
-
-4. Navigate to **Embed in a Web Page** tab and click on Copy code
-
-5. Paste the copied iframe code into the HTML of your web page where you want the survey to appear.
-
-### Example of Embedding a Survey
-
-<Col>
-<CodeGroup title="Example Embedding Code">
-
-```html
-<div style="position: relative; height:100vh; max-height:100vh; overflow:auto;">
-  <iframe
-    src="https://app.formbricks.com/s/<your-surveyId>"
-    frameborder="0"
-    style="position: absolute; left:0; top:0; width:100%; height:100%; border:0;">
-  </iframe>
-</div>
-```
-
-</CodeGroup>
-</Col>
-
-## Iframe Events
-
-The iframe fires a **formbricksSurveyCompleted** event when a user finishes a survey within the embedded iframe. This event can be captured through a message listener in your webpage's JavaScript
-
-### How to Use it?
-
-1. Embed the Formbricks survey on your webpage using the iframe method as described above.
-
-2. Add an event listener to your webpage’s JavaScript that listens for `message` events from the iframe.
-
-3. Check if the received message indicates that the survey is completed by comparing the `event.data` with the value `formbricksSurveyCompleted`.
-
-<Note>
-  It is important to verify the origin of the message to ensure it comes from the iframe containing your
-  survey, enhancing the security of your event handling.
-</Note>
-
-4. Implement your custom actions within the callback function based on the survey completion.
-
-### Example of Handling Survey Completion Events
-
-<Col>
-<CodeGroup title="Example Code for Event Listener">
-
-```javascript
-window.addEventListener("message", (event) => {
-  // Replace 'https://app.formbricks.com' with the actual web app url
-  if (event.origin === "https://app.formbricks.com" && event.data === "formbricksSurveyCompleted") {
-    console.log("Survey completed!");
-    // Implement your custom actions here
-  }
-});
-```
-
-</CodeGroup>
-</Col>

apps/formbricks-com/app/docs/link-surveys/hidden-fields/page.mdx

@@ -1,4 +1,4 @@
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import FilledHiddenFields from "./filled-hidden-fields.webp";
 import HiddenFieldResponses from "./hidden-field-responses.webp";
@@ -23,7 +23,7 @@ Hidden fields are a powerful feature in Formbricks that allows you to add data t
 
 1. Edit the survey you want to add hidden fields to & open it's settings, make sure it's selected as a **Link Survey**.
 
-<MdxImage
+<Image
   src={SettingsPage}
   alt="Select the Survey Type as Link Survey"
   quality="100"
@@ -32,7 +32,7 @@ Hidden fields are a powerful feature in Formbricks that allows you to add data t
 
 2. Switch to the Questions tab and scroll down to the bottom of the page. You will see a section called **Hidden Fields**. Make sure to enable it by toggling the switch.
 
-<MdxImage
+<Image
   src={HiddenFields}
   alt="Enable Hidden Fields"
   quality="100"
@@ -41,14 +41,14 @@ Hidden fields are a powerful feature in Formbricks that allows you to add data t
 
 3. Now click on it to add a new hidden field ID. You can add as many hidden fields as you want.
 
-<MdxImage
+<Image
   src={InputHiddenFields}
   alt="Add Hidden Fields"
   quality="100"
   className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
-<MdxImage
+<Image
   src={FilledHiddenFields}
   alt="Filled Hidden Fields"
   quality="100"
@@ -83,7 +83,7 @@ https://formbricks.com/clin3dxja02k8l80hpwmx4bjy?screen=landing_page&job=Founder
 
 These hidden fields will now be visible in the responses tab just like other fields in the Summary as well as the Response Cards, and you can use them to filter and analyze your responses.
 
-<MdxImage
+<Image
   src={HiddenFieldResponses}
   alt="Hidden Field Responses"
   quality="100"

apps/formbricks-com/app/docs/link-surveys/quickstart/page.mdx

@@ -1,10 +1,10 @@
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import HomePage from "./home-page.webp";
-import SurveyPublished from "./survey-published.webp";
 import SurveyQuestions from "./survey-questions.webp";
-import SurveyResponseOptions from "./survey-response-options.webp";
 import SurveySettings from "./survey-settings.webp";
+import SurveyResponseOptions from "./survey-response-options.webp";
+import SurveyPublished from "./survey-published.webp";
 
 export const metadata = {
   title: "Formbricks Quickstart Guide: Link Surveys Made Easier & Faster",
@@ -22,7 +22,7 @@ Link Surveys make it easy for your users to give you feedback. They are a great
 
 While you can [self-host](/docs/self-hosting/deployment) Formbricks, but the quickest and easiest way to get started is with the free Cloud plan. Just [sign up here](https://app.formbricks.com/auth/signup) and click through the onboarding, until you’re here:
 
-<MdxImage
+<Image
   src={HomePage}
   alt="Choose a link survey template"
   quality="100"
@@ -35,7 +35,7 @@ Choose one of the pre-created templates to get started. We’ll choose the **Pro
 
 On clicking the template, you’ll be forwarded to the survey editor. Here you can edit the survey questions and settings. For the sake of simplicity, we'll keep the questions as they are and move to the survey settings.
 
-<MdxImage
+<Image
   src={SurveyQuestions}
   alt="Survey Editor opens up in the Formbricks App"
   quality="100"
@@ -48,13 +48,13 @@ Click on the **Settings** tab to edit the survey settings.
 
 Formbricks packs a lot of useful functionality out of the box. You can:
 
-- Close the survey on a specidic date
+- Close the survey on a specidic date 
 - After a number of response
 - Redirect users to a URL after they completed the survey
 - Protect survey with a Pin
 - ... and much more!
 
-<MdxImage
+<Image
   src={SurveyResponseOptions}
   alt="Survey response configuration for link survey"
   quality="100"
@@ -65,7 +65,7 @@ Formbricks packs a lot of useful functionality out of the box. You can:
 
 Style your survey to your need. You can keep it simplistic or use animated backgrounds. You can change the main color and soon you'll be able to fully control the appearance of the survey.
 
-<MdxImage
+<Image
   src={SurveySettings}
   alt="UI & View configuration for link survey"
   quality="100"
@@ -76,7 +76,7 @@ Style your survey to your need. You can keep it simplistic or use animated backg
 
 Once you’re happy with the survey settings, hit **Publish** and you’ll be forwarded to the Summary Page. This is where you’ll find the responses to this survey.
 
-<MdxImage
+<Image
   src={SurveyPublished}
   alt="Survey published successfully and received link to share with users"
   quality="100"

apps/formbricks-com/app/docs/link-surveys/single-use-links/page.mdx

@@ -1,10 +1,10 @@
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import EnvVar from "./env-variable.webp";
-import Metadata from "./metadata.webp";
 import ShareModal from "./share-modal.webp";
 import Settings from "./single-use-setting.webp";
 import Message from "./used-message.webp";
+import Metadata from "./metadata.webp";
 
 export const metadata = {
   title: "Single Use Links",
@@ -29,7 +29,7 @@ Using single-use links with Formbricks is quite straight-forward:
 
 1. In the survey settings, toggle "Single Use Link" on:
 
-   <MdxImage
+   <Image
      src={Settings}
      alt="Single use survey settings"
      quality="100"
@@ -37,7 +37,7 @@ Using single-use links with Formbricks is quite straight-forward:
    />
 
 2. When you publish your survey, the following modal will open:
-   <MdxImage
+   <Image
      src={ShareModal}
      alt="Share modal with 7 single use links which can be regenerated"
      quality="100"
@@ -50,7 +50,7 @@ Here, you can copy and generate as many single-use links as you need.
 
 You can encrypt single use URLs to assure information to be protected. To enable it, you have to set the correct environment variable:
 
-<MdxImage
+<Image
   src={EnvVar}
   alt="Set the right env var to be able to enable encryption."
   quality="100"
@@ -61,7 +61,7 @@ You can encrypt single use URLs to assure information to be protected. To enable
 
 You can find the suId of each submission in the submission meta data. To view it, simple hover over the Avatar:
 
-<MdxImage
+<Image
   src={Metadata}
   alt="View suId in the submission meta data."
   quality="100"
@@ -72,7 +72,7 @@ You can find the suId of each submission in the submission meta data. To view it
 
 You can customize the 'link used' messaging in the Survey Editor settings:
 
-<MdxImage
+<Image
   src={Message}
   alt="Adjust the message shown to people if a link was already used."
   quality="100"

apps/formbricks-com/app/docs/link-surveys/source-tracking/page.mdx

@@ -1,4 +1,4 @@
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import ShareLink from "./share-link.webp";
 import ViewResponse from "./view-response.webp";
@@ -17,14 +17,7 @@ Understand the source a survey respondent comes from when responding to your sur
 Check out this video to learn more about source tracking in link surveys:
 
 {/* Replace link below with our new link on Source Tracking */}
-
-<iframe
-  width="700"
-  height="450"
-  src="https://www.youtube.com/embed/CytWhuyEMVI?si=t-SFB2A1l1RZDdAC"
-  title="YouTube video player: Formbricks"
-  frameborder="0"
-  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"></iframe>
+<iframe width="700" height="450" src="https://www.youtube.com/embed/CytWhuyEMVI?si=t-SFB2A1l1RZDdAC" title="YouTube video player: Formbricks" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"></iframe>
 
 ## Purpose
 
@@ -34,7 +27,6 @@ Source tracking for link surveys is essential when you:
 - Aim to ensure compliance with tracking and data collection regulations.
 
 ## Code Example
-
 <Col>
 <CodeGroup title="Example Source as Google">
 
@@ -65,13 +57,14 @@ https://formbricks.com/clin3dxja02k8l80hpwmx4bjy?source=Google
 
 3. **View Responses**: Use the collected source data to analyze where your survey respondents are coming from. You can hover over the user icon in the responses tab to see the source of the user.
 
-<MdxImage
-  src={ViewResponse}
-  alt="View Source in Response"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+<Image
+    src={ViewResponse}
+    alt="View Source in Response"
+    quality="100"
+    className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 4. **Analyse Data**: Download all the responses as a CSV/Excel and get access to the source information. This can provide valuable insights into your audience.
 
 Source tracking allows you to make informed decisions based on the origin of your survey participants, helping you tailor your surveys and marketing strategies accordingly.
+

apps/formbricks-com/app/docs/link-surveys/start-at-question/page.mdx

@@ -1,43 +0,0 @@
-export const metadata = {
-  title: "Start At Specific Question",
-  description: "Start a survey at a specific question using the URL to skip the initial questions.",
-};
-
-#### Link Surveys
-
-# Start At Specific Question
-
-You can start a survey at a specific question from the survey using the URL to skip the initial questions. This is useful when you want to link to a specific question from an external source or want to use the same survey in different parts of the user journey.
-
-## How to Use it?
-
-1. In the Survey Editor, open the Questions Tab and ensure the survey is set as a **Link Survey**.
-
-2. Find the question you want to start at, click on **Show Advanced Settings**, and copy the **Question ID**.
-
-<Note>
-  Each question has a unique Question ID, which is used to identify it in the survey. You can use different
-  Question IDs for multiple **startAt** points in the URL.
-</Note>
-
-3. Append `?startAt=question_id` to your survey's URL, replacing `question_id` with the copied Question ID.
-
-4. Share this modified URL with your users to start the survey at the specified question.
-
-### Sample Link Survey URL with `startAt`
-
-<Col>
-<CodeGroup title="Example Link Survey URL with startAt configured">
-
-```sh
-https://formbricks.com/clny997dj087ho30fdzyf4nkl?startAt=bqd29m94l9k0hnc3azbrexl8
-```
-
-</CodeGroup>
-</Col>
-
-## Use Cases
-
-- **Link to a specific question from an external source:** Use this feature to direct users to a specific question in your survey from emails, chatbots, or web pages, providing a seamless experience.
-- **Use the same survey in different parts of the user journey:** Employ the same survey at various stages of the user journey, starting at different questions to gather comprehensive insights.
-- **Create a personalized survey experience:** Tailor the survey experience by starting at a particular question based on the user's past interactions or preferences, enhancing engagement.

apps/formbricks-com/app/docs/link-surveys/user-identification/page.mdx

@@ -1,4 +1,4 @@
-import { MdxImage } from "@/components/shared/MdxImage";
+import Image from "next/image";
 
 import PeopleView from "./people-view.webp";
 
@@ -23,7 +23,6 @@ Identifying users in link surveys comes in handy when you:
 - Want to gather data and later connect it to a user who has not signed up yet
 
 ## Quick Example
-
 <Col>
 <CodeGroup title="User Identification Example">
 
@@ -43,9 +42,9 @@ The `userId` we are refering to is the `userId` of your own system. For example,
 
 This allows you to connect the response to the user profile of this specific in the Formbricks database. You can then use the response data to create segments for further surveying or invite them to an interview, etc.
 
-<MdxImage
+<Image
   src={PeopleView}
   alt="If users are identified by email, it will show. If not, the internal Id will be set."
   quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
+  className="rounded-lg max-w-full sm:max-w-3xl"
 />

apps/formbricks-com/app/docs/self-hosting/enterprise/page.mdx

@@ -1,6 +1,7 @@
 export const metadata = {
   title: "Enterprise License to unlock advanced functionality",
-  description: "Request a enterprise licenses to unlock advanced enterprise functionality",
+  description:
+    "Request a self-hosting licenses to unlock advanced enterprise functionality",
 };
 
 #### Self-Hosting
@@ -11,37 +12,15 @@ We're handing out free enterprise license keys during our beta.
 
 Additional to the AGPL licensed Formbricks core, the Formbricks repository contains code licensed under an [Enterprise license](https://github.com/formbricks/formbricks/blob/main/packages/ee/LICENSE). This additional functionality is not part of the AGPLv3 licensed Formbricks core and is designed to meet the needs of larger teams and enterprises. This advanced functionality is already included in the Docker images, but you need an [Enterprise License Key](https://formbricks.com/docs/self-hosting/license) to unlock it.
 
-### When do I need an Enterprise License?
-
-|  | Community Edition | Enterprise License |
-| --- | --- | --- |
-| Self-host for commercial purposes | ✅ | No EE license needed |
-| To make changes to the code base (happy to publish them) | ✅ | No EE license needed |
-| Unlimited responses | ✅ | No EE license needed |
-| Unlimited surveys | ✅ | No EE license needed |
-| Remove branding | ✅ | No EE license needed |
-| SSO | ✅ | No EE license needed |
-| Use any of the other 100 features | ✅ | No EE license needed |
-| Team roles | ❌ | ✅ |
-| Multi-language surveys | ❌ | ✅ |
-| Advanced targeting / Segments | ❌ | ✅ |
-| Make code changes and keep private | ❌ | ✅ |
-| Whitelabel Formbricks | ❌ | ✅ |
-| Sell Formbricks as SaaS to others | ❌ | ✅ |
-
 **Please note:** Sooner than later we will introduce a enterprise license pricing. For a free beta key, fill out this form:
 
-<div
-  style={{
-    position: "relative",
-    height: "100vh",
-    maxHeight: "100vh",
-    overflow: "auto",
-    borderRadius: "12px",
-  }}>
+<div style={{ position: 'relative', height: '100vh', maxHeight: '100vh', overflow: 'auto', borderRadius:'12px' }}>
   <iframe
     src="https://app.formbricks.com/s/clrf4z8zg1u3912250j7shqb5"
-    style={{ position: "absolute", left: 0, top: 0, width: "100%", height: "100%", border: 0 }}></iframe>
+    style={{ position: 'absolute', left: 0, top: 0, width: '100%', height: '100%', border: 0 }}
+  >
+  </iframe>
 </div>
 
+
 **Can’t figure it out?**: [Join our Discord!](https://formbricks.com/discord)

apps/formbricks-com/app/docs/self-hosting/external-auth-providers/page.mdx

@@ -76,27 +76,6 @@ GOOGLE_CLIENT_SECRET=your-client-secret-here
    - Navigate to your Docker setup directory where your `docker-compose.yml` file is located.
    - Run the following command to bring down your current Docker containers and then bring them back up with the updated environment configuration:
 
-## Azure SSO Integration
-
-Have an Azure Active Directory (AAD) instance? Integrate it with your Formbricks instance to allow users to log in using their existing AAD credentials. This guide will walk you through the process of setting up Azure SSO for your Formbricks instance.
-
-### Requirements
-
-- An Azure Active Directory (AAD) instance.
-- A Formbricks instance running and accessible.
-
-### Steps
-
-1. Create a new Tenant in Azure Active Directory as per their [official documentation](https://learn.microsoft.com/en-us/entra/fundamentals/create-new-tenant).
-2. Add Users & Groups to your AAD instance.
-3. Now we need to fill the below environment variables in our Formbricks instance so get them from your AD configuration:
-   - `AZUREAD_CLIENT_ID`
-   - `AZUREAD_CLIENT_SECRET`
-   - `AZUREAD_TENANT_ID`
-4. Update these environment variables in your `docker-compose.yml` or pass it like your other environment variables to the Formbricks container.
-5. Restart your Formbricks instance.
-6. You're all set! Users can now signup & log in using their AAD credentials.
-
 ## OpenID Integration
 
 Integrating your own OIDC (OpenID Connect) instance with your Formbricks instance allows users to log in using their OIDC credentials, ensuring a secure and streamlined user experience. Please follow the steps below to set up OIDC for your Formbricks instance.
@@ -136,54 +115,52 @@ OIDC_SIGNING_ALGORITHM=HS256
 
 These variables can be provided at the runtime i.e. in your docker-compose file.
 
-| Variable                    | Description                                                                                  | Required                                                | Default                   |
-|-----------------------------|----------------------------------------------------------------------------------------------|---------------------------------------------------------|---------------------------|
-| WEBAPP_URL                  | Base URL of the site.                                                                        | required                                                | `http://localhost:3000`   |
-| DATABASE_URL                | Database URL with credentials.                                                               | required                                                |                           |
-| NEXTAUTH_SECRET             | Secret for NextAuth, used for session signing and encryption.                                | required                                                | (Generated by the user)   |
-| ENCRYPTION_KEY              | Secret for used by Formbricks for data encryption                                            | required                                                | (Generated by the user)   |
-| NEXTAUTH_URL                | Location of the auth server. By default, this is the Formbricks docker instance itself.      | required                                                | `http://localhost:3000`   |
-| UPLOADS_DIR                 | Local directory for storing uploads.                                                         | optional                                                | `./uploads`               |
-| S3_ACCESS_KEY               | Access key for S3.                                                                           | optional                                                | (resolved by the AWS SDK) |
-| S3_SECRET_KEY               | Secret key for S3.                                                                           | optional                                                | (resolved by the AWS SDK) |
-| S3_REGION                   | Region for S3.                                                                               | optional                                                | (resolved by the AWS SDK) |
-| S3_BUCKET_NAME              | Bucket name for S3.                                                                          | optional (required if S3 is enabled)                    |                           |
-| S3_ENDPOINT                 | Endpoint for S3.                                                                             | optional                                                | (resolved by the AWS SDK) |
-| PRIVACY_URL                 | URL for privacy policy.                                                                      | optional                                                |                           |
-| TERMS_URL                   | URL for terms of service.                                                                    | optional                                                |                           |
-| IMPRINT_URL                 | URL for imprint.                                                                             | optional                                                |                           |
-| SIGNUP_DISABLED             | Disables the ability for new users to create an account if set to `1`.                       | optional                                                |                           |
-| EMAIL_AUTH_DISABLED         | Disables the ability for users to signup or login via email and password if set to `1`.      | optional                                                |                           |
-| PASSWORD_RESET_DISABLED     | Disables password reset functionality if set to `1`.                                         | optional                                                |                           |
-| EMAIL_VERIFICATION_DISABLED | Disables email verification if set to `1`.                                                   | optional                                                |                           |
-| RATE_LIMITING_DISABLED      | Disables rate limiting if set to `1`.                                                        | optional                                                |                           |
-| INVITE_DISABLED             | Disables the ability for invited users to create an account if set to `1`.                   | optional                                                |                           |
-| MAIL_FROM                   | Email address to send emails from.                                                           | optional (required if email services are to be enabled) |                           |
-| SMTP_HOST                   | Host URL of your SMTP server.                                                                | optional (required if email services are to be enabled) |                           |
-| SMTP_PORT                   | Host Port of your SMTP server.                                                               | optional (required if email services are to be enabled) |                           |
-| SMTP_USER                   | Username for your SMTP Server.                                                               | optional (required if email services are to be enabled) |                           |
-| SMTP_PASSWORD               | Password for your SMTP Server.                                                               | optional (required if email services are to be enabled) |                           |
-| SMTP_SECURE_ENABLED         | SMTP secure connection. For using TLS, set to `1` else to `0`.                               | optional (required if email services are to be enabled) |                           |
-| GITHUB_ID                   | Client ID for GitHub.                                                                        | optional (required if GitHub auth is enabled)           |                           |
-| GITHUB_SECRET               | Secret for GitHub.                                                                           | optional (required if GitHub auth is enabled)           |                           |
-| GOOGLE_CLIENT_ID            | Client ID for Google.                                                                        | optional (required if Google auth is enabled)           |                           |
-| GOOGLE_CLIENT_SECRET        | Secret for Google.                                                                           | optional (required if Google auth is enabled)           |                           |
-| CRON_SECRET                 | API Secret for running cron jobs.                                                            | optional                                                |                           |
-| STRIPE_SECRET_KEY           | Secret key for Stripe integration.                                                           | optional                                                |                           |
-| STRIPE_WEBHOOK_SECRET       | Webhook secret for Stripe integration.                                                       | optional                                                |                           |
-| TELEMETRY_DISABLED          | Disables telemetry if set to `1`.                                                            | optional                                                |                           |
-| INSTANCE_ID                 | Instance ID for Formbricks Cloud to be sent to Telemetry.                                    | optional                                                |                           |
-| INTERNAL_SECRET             | Internal Secret (Currently we overwrite the value with a random value).                      | optional                                                |                           |
-| DEFAULT_BRAND_COLOR         | Default brand color for your app (Can be overwritten from the UI as well).                   | optional                                                | `#64748b`                 |
-| DEFAULT_TEAM_ID             | Automatically assign new users to a specific team when joining                               | optional                                                |                           |
-| DEFAULT_TEAM_ROLE           | Role of the user in the default team.                                                        | optional                                                | `admin`                   |
-| ONBOARDING_DISABLED         | Disables onboarding for new users if set to `1`                                              | optional                                                |                           |
-| OIDC_DISPLAY_NAME           | Display name for Custom OpenID Connect Provider                                              | optional                                                |                           |
-| OIDC_CLIENT_ID              | Client ID for Custom OpenID Connect Provider                                                 | optional (required if OIDC auth is enabled)             |                           |
-| OIDC_CLIENT_SECRET          | Secret for Custom OpenID Connect Provider                                                    | optional (required if OIDC auth is enabled)             |                           |
-| OIDC_ISSUER                 | Issuer URL for Custom OpenID Connect Provider (should have `.well-known` configured at this) | optional (required if OIDC auth is enabled)             |                           |
-| OIDC_SIGNING_ALGORITHM      | Signing Algorithm for Custom OpenID Connect Provider                                         | optional                                                | `RS256`                   |
-| OPENTELEMETRY_LISTENER_URL  | URL for OpenTelemetry listener inside Formbricks.                                            | optional |                                              |                           |
+| Variable                    | Description                                                                                  | Required                                                | Default                 |
+| --------------------------- | -------------------------------------------------------------------------------------------- | ------------------------------------------------------- | ----------------------- |
+| WEBAPP_URL                  | Base URL of the site.                                                                        | required                                                | `http://localhost:3000` |
+| DATABASE_URL                | Database URL with credentials.                                                               | required                                                |                         |
+| NEXTAUTH_SECRET             | Secret for NextAuth, used for session signing and encryption.                                | required                                                | (Generated by the user) |
+| ENCRYPTION_KEY              | Secret for used by Formbricks for data encryption                                            | required                                                | (Generated by the user) |
+| NEXTAUTH_URL                | Location of the auth server. By default, this is the Formbricks docker instance itself.      | required                                                | `http://localhost:3000` |
+| S3_ACCESS_KEY               | Access key for S3.                                                                           | optional (required if S3 is enabled)                    |                         |
+| S3_SECRET_KEY               | Secret key for S3.                                                                           | optional (required if S3 is enabled)                    |                         |
+| S3_REGION                   | Region for S3.                                                                               | optional (required if S3 is enabled)                    |                         |
+| S3_BUCKET                   | Bucket name for S3.                                                                          | optional (required if S3 is enabled)                    |                         |
+| S3_ENDPOINT                 | Endpoint for S3.                                                                             | optional (required if S3 is enabled)                    |                         |
+| PRIVACY_URL                 | URL for privacy policy.                                                                      | optional                                                |                         |
+| TERMS_URL                   | URL for terms of service.                                                                    | optional                                                |                         |
+| IMPRINT_URL                 | URL for imprint.                                                                             | optional                                                |                         |
+| SIGNUP_DISABLED             | Disables the ability for new users to create an account if set to `1`.                       | optional                                                |                         |
+| EMAIL_AUTH_DISABLED         | Disables the ability for users to signup or login via email and password if set to `1`.      | optional                                                |                         |
+| PASSWORD_RESET_DISABLED     | Disables password reset functionality if set to `1`.                                         | optional                                                |                         |
+| EMAIL_VERIFICATION_DISABLED | Disables email verification if set to `1`.                                                   | optional                                                |                         |
+| RATE_LIMITING_DISABLED      | Disables rate limiting if set to `1`.                                                        | optional                                                |                         |
+| INVITE_DISABLED             | Disables the ability for invited users to create an account if set to `1`.                   | optional                                                |                         |
+| MAIL_FROM                   | Email address to send emails from.                                                           | optional (required if email services are to be enabled) |                         |
+| SMTP_HOST                   | Host URL of your SMTP server.                                                                | optional (required if email services are to be enabled) |                         |
+| SMTP_PORT                   | Host Port of your SMTP server.                                                               | optional (required if email services are to be enabled) |                         |
+| SMTP_USER                   | Username for your SMTP Server.                                                               | optional (required if email services are to be enabled) |                         |
+| SMTP_PASSWORD               | Password for your SMTP Server.                                                               | optional (required if email services are to be enabled) |                         |
+| SMTP_SECURE_ENABLED         | SMTP secure connection. For using TLS, set to `1` else to `0`.                               | optional (required if email services are to be enabled) |                         |
+| GITHUB_ID                   | Client ID for GitHub.                                                                        | optional (required if GitHub auth is enabled)           |                         |
+| GITHUB_SECRET               | Secret for GitHub.                                                                           | optional (required if GitHub auth is enabled)           |                         |
+| GOOGLE_CLIENT_ID            | Client ID for Google.                                                                        | optional (required if Google auth is enabled)           |                         |
+| GOOGLE_CLIENT_SECRET        | Secret for Google.                                                                           | optional (required if Google auth is enabled)           |                         |
+| CRON_SECRET                 | API Secret for running cron jobs.                                                            | optional                                                |                         |
+| STRIPE_SECRET_KEY           | Secret key for Stripe integration.                                                           | optional                                                |                         |
+| STRIPE_WEBHOOK_SECRET       | Webhook secret for Stripe integration.                                                       | optional                                                |                         |
+| TELEMETRY_DISABLED          | Disables telemetry if set to `1`.                                                            | optional                                                |                         |
+| INSTANCE_ID                 | Instance ID for Formbricks Cloud to be sent to Telemetry.                                    | optional                                                |                         |
+| INTERNAL_SECRET             | Internal Secret (Currently we overwrite the value with a random value).                      | optional                                                |                         |
+| DEFAULT_BRAND_COLOR         | Default brand color for your app (Can be overwritten from the UI as well).                   | optional                                                | `#64748b`               |
+| DEFAULT_TEAM_ID             | Automatically assign new users to a specific team when joining                               | optional                                                |                         |
+| DEFAULT_TEAM_ROLE           | Role of the user in the default team.                                                        | optional                                                | `admin`                 |
+| ONBOARDING_DISABLED         | Disables onboarding for new users if set to `1`                                              | optional                                                |                         |
+| OIDC_DISPLAY_NAME           | Display name for Custom OpenID Connect Provider                                              | optional                                                |                         |
+| OIDC_CLIENT_ID              | Client ID for Custom OpenID Connect Provider                                                 | optional (required if OIDC auth is enabled)             |                         |
+| OIDC_CLIENT_SECRET          | Secret for Custom OpenID Connect Provider                                                    | optional (required if OIDC auth is enabled)             |                         |
+| OIDC_ISSUER                 | Issuer URL for Custom OpenID Connect Provider (should have `.well-known` configured at this) | optional (required if OIDC auth is enabled)             |                         |
+| OIDC_SIGNING_ALGORITHM      | Signing Algorithm for Custom OpenID Connect Provider                                         | optional                                                | `RS256`                 | 
 
 ## Build-time Variables
 

apps/formbricks-com/app/docs/self-hosting/migration-guide/page.mdx

@@ -29,22 +29,12 @@ To run all these steps, please navigate to the `formbricks` folder where your `d
 <CodeGroup title="Backup Postgres">
 
 ```bash
-docker exec formbricks-quickstart-postgres-1 pg_dump -Fc -U postgres -d formbricks > formbricks_pre_v1.6_$(date +%Y%m%d_%H%M%S).dump
+docker exec formbricks-quickstart-postgres-1 pg_dump -U postgres -d formbricks > formbricks_pre_v1.6_$(date +%Y%m%d_%H%M%S).sql
 ```
 
 </CodeGroup>
 </Col>
 
-<Note>
-  If you run into “No such container”, use `docker ps` to find your container name, e.g.
-  `formbricks_postgres_1`.
-</Note>
-
-<Note>
-  If you prefer storing the backup as an `*.sql` file remove the `-Fc` (custom format) option. In case of a
-  restore scenario you will need to use `psql` then with an empty `formbricks` database.
-</Note>
-
 2. Stop the running Formbricks instance & remove the related containers:
 
 <Col>
@@ -81,7 +71,7 @@ docker run --rm \
   --network=formbricks_default \
   -e DATABASE_URL="postgresql://postgres:postgres@postgres:5432/formbricks?schema=public" \
   -e UPGRADE_TO_VERSION="v1.6" \
-  ghcr.io/formbricks/data-migrations:v1.6.1
+  ghcr.io/formbricks/data-migrations:v1.6
 ```
 
 </CodeGroup>
@@ -91,40 +81,9 @@ The above command will migrate your data to the latest schema. This is a crucial
 
 5. That's it! Once the migration is complete, you can **now access your Formbricks instance** at the same URL as before.
 
-#### Restoring the database after a failed upgrade
-
-<Col>
-<CodeGroup title="Restore the database">
-
-```bash
-docker exec -i formbricks-quickstart-postgres-1 pg_restore --clean -U postgres -v -d formbricks < formbricks_pre_v1.6_<timestamp_of_your_dump_file>.dump
-```
-
-</CodeGroup>
-</Col>
-
-<Note>Replace the path to `formbricks_pre_v1.6_<timestamp_of_your_dump_file>.dump` with the exact path to your `.dump` file.</Note>
-
-<Note>This will wipe the database and restore from the `.dump` file</Note>
-
 ### In-App Surveys with @formbricks/js
 
-If you are using the `@formbricks/js` package, please make sure to update it to version `~1.6.5` to use the latest features and improvements.
-
-<Note>
-  Currently the package needs to be pinned to `~1.6.5`, see
-  https://github.com/formbricks/formbricks/issues/2273
-</Note>
-
-<Col>
-<CodeGroup title="Upgrade and pin the client package">
-
-```bash
-npm install @formbricks/js@~1.6.5
-```
-
-</CodeGroup>
-</Col>
+If you are using the `@formbricks/js` package, please make sure to update it to version 1.6.0 to use the latest features and improvements.
 
 ### Deprecated Environment Variables
 

apps/formbricks-com/components/demo/HeaderLight.tsx

@@ -0,0 +1,45 @@
+import { Popover } from "@headlessui/react";
+import { usePlausible } from "next-plausible";
+import Link from "next/link";
+import { useRouter } from "next/router";
+
+import { Button } from "@formbricks/ui/Button";
+
+import { FooterLogo } from "../shared/Logo";
+
+export default function HeaderLight() {
+  const plausible = usePlausible();
+  const router = useRouter();
+  return (
+    <Popover className="relative" as="header">
+      <div className="max-w-8xl mx-auto flex items-center justify-between py-6 sm:px-2  md:justify-start lg:px-8 xl:px-12">
+        <div className="flex w-0 flex-1 justify-start">
+          <Link href="/">
+            <span className="sr-only">Formbricks</span>
+            <FooterLogo className="ml-7 h-8 w-auto sm:h-10" />
+          </Link>
+        </div>
+
+        <div className="hidden flex-1 items-center justify-end md:flex">
+          <Button
+            variant="secondary"
+            onClick={() => {
+              router.push("https://cal.com/johannes/formbricks-demo");
+              plausible("Demo_CTA_TalkToUs");
+            }}>
+            Talk to us
+          </Button>
+          <Button
+            variant="highlight"
+            className="ml-2"
+            onClick={() => {
+              router.push("https://app.formbricks.com/auth/signup");
+              plausible("Demo_CTA_TryForFree");
+            }}>
+            Start for free
+          </Button>
+        </div>
+      </div>
+    </Popover>
+  );
+}

apps/formbricks-com/components/demo/LayoutLight.tsx

@@ -8,14 +8,16 @@ interface LayoutProps {
   description: string;
 }
 
-export default function LayoutLight({ title, description, children }: LayoutProps) {
+export default function Layout({ title, description, children }: LayoutProps) {
   return (
     <div className="mx-auto w-full">
       <MetaInformation title={title} description={description} />
       <HeaderLight />
-      <main className="max-w-8xl relative mx-auto flex w-full flex-col justify-center space-y-24 px-6 lg:space-y-40 lg:px-24 xl:px-36 ">
-        {children}
-      </main>
+      {
+        <main className="max-w-8xl relative mx-auto flex w-full flex-col justify-center px-2 lg:px-8 xl:px-12">
+          {children}
+        </main>
+      }
       <Footer />
     </div>
   );

apps/formbricks-com/components/docs/Header.tsx

@@ -1,7 +1,6 @@
 "use client";
 
 import { FooterLogo } from "@/components/shared/Logo";
-import { Search } from "@/components/shared/Search";
 import clsx from "clsx";
 import { motion, useScroll, useTransform } from "framer-motion";
 import Link from "next/link";
@@ -9,6 +8,7 @@ import { forwardRef } from "react";
 
 import { Button } from "./Button";
 import { MobileNavigation, useIsInsideMobileNavigation, useMobileNavigationStore } from "./MobileNavigation";
+import { MobileSearch, Search } from "./Search";
 import { ThemeToggle } from "./ThemeToggle";
 
 function TopLevelNavItem({ href, children }: { href: string; children: React.ReactNode }) {
@@ -57,9 +57,7 @@ export const Header = forwardRef<React.ElementRef<"div">, { className?: string }
           (isInsideMobileNavigation || !mobileNavIsOpen) && "bg-slate-900/7.5 dark:bg-white/7.5"
         )}
       />
-      <div className="hidden md:block">
-        <Search />
-      </div>
+      <Search />
       <div className="flex items-center gap-5 lg:hidden">
         <MobileNavigation />
         <Link href="/" aria-label="Home">
@@ -77,9 +75,7 @@ export const Header = forwardRef<React.ElementRef<"div">, { className?: string }
         </nav>
         <div className="hidden md:block md:h-5 md:w-px md:bg-slate-900/10 md:dark:bg-white/15" />
         <div className="flex gap-4">
-          <div className="block md:hidden">
-            <Search />
-          </div>
+          <MobileSearch />
           <ThemeToggle />
         </div>
         <div className="hidden min-[416px]:contents">

apps/formbricks-com/components/docs/Navigation.tsx

@@ -197,7 +197,6 @@ export const navigation: Array<NavGroup> = [
       { title: "Identify Users", href: "/docs/in-app-surveys/user-identification" },
       { title: "Actions", href: "/docs/in-app-surveys/actions" },
       { title: "Attributes", href: "/docs/in-app-surveys/attributes" },
-      { title: "Advanced Targeting", href: "/docs/in-app-surveys/advanced-targeting" },
     ],
   },
   {
@@ -209,14 +208,8 @@ export const navigation: Array<NavGroup> = [
       { title: "Single Use Links", href: "/docs/link-surveys/single-use-links" },
       { title: "Source Tracking", href: "/docs/link-surveys/source-tracking" },
       { title: "Hidden Fields", href: "/docs/link-surveys/hidden-fields" },
-      { title: "Start At Question", href: "/docs/link-surveys/start-at-question" },
-      { title: "Embed Surveys", href: "/docs/link-surveys/embed-surveys" },
     ],
   },
-  {
-    title: "Additional Features",
-    links: [{ title: "Multi Language Surveys", href: "/docs/additional-features/multi-language-surveys" }],
-  },
   {
     title: "Best Practices",
     links: [
@@ -238,7 +231,6 @@ export const navigation: Array<NavGroup> = [
       { title: "Notion", href: "/docs/integrations/notion" },
       { title: "Make.com", href: "/docs/integrations/make" },
       { title: "n8n", href: "/docs/integrations/n8n" },
-      { title: "Slack", href: "/docs/integrations/slack" },
       { title: "Wordpress", href: "/docs/integrations/wordpress" },
       { title: "Zapier", href: "/docs/integrations/zapier" },
     ],

apps/formbricks-com/components/docs/TellaVideo.tsx

@@ -1,18 +0,0 @@
-import React from "react";
-
-export function TellaVideo({ tellaVideoIdentifier }: { tellaVideoIdentifier: string }) {
-  return (
-    <div>
-      <iframe
-        className="aspect-video"
-        style={{
-          width: "100%",
-          height: "100%",
-          border: 0,
-        }}
-        src={`https://www.tella.tv/video/${tellaVideoIdentifier}/embed?b=0&title=0&a=1&loop=0&autoPlay=true&t=0&muted=1&wt=0`}
-        allowFullScreen={true}
-        title="Tella Video Help"></iframe>
-    </div>
-  );
-}

apps/formbricks-com/components/dummyUI/AddEventDummy.tsx

@@ -1,4 +1,4 @@
-import { PlusIcon, TrashIcon } from "lucide-react";
+import { PlusIcon, TrashIcon } from "@heroicons/react/24/solid";
 import { useState } from "react";
 
 import { Button } from "@formbricks/ui/Button";

apps/formbricks-com/components/dummyUI/AddNoCodeEventModalDummy.tsx

@@ -1,4 +1,4 @@
-import { MousePointerClickIcon } from "lucide-react";
+import { CursorArrowRaysIcon } from "@heroicons/react/24/solid";
 
 import { Button } from "@formbricks/ui/Button";
 import { Input } from "@formbricks/ui/Input";
@@ -20,7 +20,7 @@ export const AddNoCodeEventModalDummy: React.FC<EventDetailModalProps> = ({ open
           <div className="p-4 sm:p-6">
             <div className="flex items-center space-x-2">
               <div className="h-6 w-6 text-slate-500">
-                <MousePointerClickIcon className="h-5 w-5" />
+                <CursorArrowRaysIcon />
               </div>
               <div>
                 <div className="text-lg font-medium text-slate-700 dark:text-slate-300">Add Action</div>