feat: 99 unlimited plan (#2137)

Co-authored-by: Matti Nannt <mail@matthiasnannt.com>

.changeset/README.md

@@ -1,8 +0,0 @@
-# Changesets
-
-Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
-with multi-package repos, or single-package repos to help you version and publish your code. You can
-find the full documentation for it [in our repository](https://github.com/changesets/changesets)
-
-We have a quick list of common questions to get you started engaging with this project in
-[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

.devcontainer/devcontainer.json

@@ -22,6 +22,7 @@
 
   // Use 'postCreateCommand' to run commands after the container is created.
   "postCreateCommand": "cp .env.example .env && sed -i '/^ENCRYPTION_KEY=/c\\ENCRYPTION_KEY='$(openssl rand -hex 32) .env && sed -i '/^NEXTAUTH_SECRET=/c\\NEXTAUTH_SECRET='$(openssl rand -hex 32) .env && pnpm install && pnpm db:migrate:dev",
+  "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"

.dockerignore

@@ -1,7 +1,7 @@
 # See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
 
 # dependencies
-**/node_modules
+# **/node_modules
 .pnp
 .pnp.js
 .pnpm-store/

.env.example

@@ -1,8 +1,7 @@
 ########################################################################
-# ------------ MANDATORY (CHANGE ACCORDING TO YOUR SETUP) ------------#
+# ------------ MANDATORY (CHANGE ACCORDING TO YOUR SETUP) ------------ #
 ########################################################################
 
-
 ############
 #  BASICS  #
 ############
@@ -51,13 +50,25 @@ SMTP_SECURE_ENABLED=0
 SMTP_USER=smtpUser
 SMTP_PASSWORD=smtpPassword
 
-
 ########################################################################
 # ------------------------------ OPTIONAL -----------------------------#
 ########################################################################
 
 # Uncomment the variables you would like to use and customize the values.
 
+##############
+# S3 STORAGE #
+##############
+
+# S3 Storage is required for the file uplaod in serverless environments like Vercel
+S3_ACCESS_KEY=
+S3_SECRET_KEY=
+S3_REGION=
+S3_BUCKET_NAME=
+# Configure a third party S3 compatible storage service endpoint like StorJ leave empty if you use Amazon S3
+# e.g., https://gateway.storjshare.io
+S3_ENDPOINT_URL=
+
 #####################
 # Disable Features  #
 #####################
@@ -71,6 +82,9 @@ PASSWORD_RESET_DISABLED=1
 # Signup. Disable the ability for new users to create an account.
 # SIGNUP_DISABLED=1
 
+# Email login. Disable the ability for users to login with email.
+# EMAIL_AUTH_DISABLED=1
+
 # Team Invite. Disable the ability for invited users to create an account.
 # INVITE_DISABLED=1
 
@@ -84,21 +98,25 @@ TERMS_URL=
 IMPRINT_URL=
 
 # Configure Github Login
-GITHUB_AUTH_ENABLED=0
 GITHUB_ID=
 GITHUB_SECRET=
 
 # Configure Google Login
-GOOGLE_AUTH_ENABLED=0
 GOOGLE_CLIENT_ID=
 GOOGLE_CLIENT_SECRET=
 
 # Configure Azure Active Directory Login
-AZUREAD_AUTH_ENABLED=0
 AZUREAD_CLIENT_ID=
 AZUREAD_CLIENT_SECRET=
 AZUREAD_TENANT_ID=
 
+# OpenID Connect (OIDC) configuration
+# OIDC_CLIENT_ID=
+# OIDC_CLIENT_SECRET=
+# OIDC_ISSUER=
+# OIDC_DISPLAY_NAME=
+# OIDC_SIGNING_ALGORITHM=
+
 # Cron Secret
 CRON_SECRET=
 
@@ -118,12 +136,12 @@ NEXT_PUBLIC_FORMBRICKS_API_HOST=
 NEXT_PUBLIC_FORMBRICKS_ENVIRONMENT_ID=
 NEXT_PUBLIC_FORMBRICKS_ONBOARDING_SURVEY_ID=
 
-# Oauth credentials for Google sheet integration 
+# Oauth credentials for Google sheet integration
 GOOGLE_SHEETS_CLIENT_ID=
 GOOGLE_SHEETS_CLIENT_SECRET=
 GOOGLE_SHEETS_REDIRECT_URL=
 
-# Oauth credentials for Airtable integration 
+# Oauth credentials for Airtable integration
 AIRTABLE_CLIENT_ID=
 
 # Enterprise License Key
@@ -137,3 +155,10 @@ ENTERPRISE_LICENSE_KEY=
 
 # set to 1 to skip onboarding for new users
 # ONBOARDING_DISABLED=1
+
+# Send new users to customer.io
+# CUSTOMER_IO_API_KEY=
+# CUSTOMER_IO_SITE_ID=
+
+# Ignore Rate Limiting across the Formbricks app
+# RATE_LIMITING_DISABLED=1

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -42,7 +42,6 @@ body:
         - First time: Please read our [introductory blog post](https://formbricks.com/blog/join-the-formtribe)
         - All UI components are in the package `formbricks/ui`
         - Run `pnpm go` to find a demo app to test in-app surveys at `localhost:3002`
-        - Everything is type-safe
-        - We use **chatGPT** to help refactor code. Use our [Formbricks ✨ megaprompt ✨](https://github.com/formbricks/formbricks/blob/main/megaprompt.md) to create the right 
-          context before you write your prompt.
+        - Everything is type-safe.
+        - We use **chatGPT** to help refactor code.
         - Anything unclear? [Ask in Discord](https://formbricks.com/discord)

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,3 +1,5 @@
+<!-- We require pull request titles to follow the Conventional Commits specification ( https://www.conventionalcommits.org/en/v1.0.0/#summary ). Please make sure your title follow these conventions -->
+
 ## What does this PR do?
 
 <!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. -->
@@ -8,18 +10,6 @@ Fixes # (issue)
  Loom Video: https://www.loom.com/
 -->
 
-## Type of change
-
-<!-- Please mark the relevant points by using [x] -->
-
-- [ ] Bug fix (non-breaking change which fixes an issue)
-- [ ] Chore (refactoring code, technical debt, workflow improvements)
-- [ ] Enhancement (small improvements)
-- [ ] New feature (non-breaking change which adds functionality)
-- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
-- [ ] This change adds a new database migration
-- [ ] This change requires a documentation update
-
 ## How should this be tested?
 
 <!-- Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration -->
@@ -42,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://formbricks.com/clmyhzfrymr4ko00hycsg1tvx) Without it we wont be able to merge it 🙏
 
 ### Appreciated
 

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

@@ -0,0 +1,53 @@
+name: Build & Cache Web App
+
+runs:
+  using: "composite"
+  steps:
+    - name: Checkout repo
+      uses: actions/checkout@v3
+
+    - name: Cache Build
+      uses: actions/cache@v3
+      id: cache-build
+      env:
+        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 }}-${{ env.key-3 }}
+
+    - name: Setup Node.js 20.x
+      uses: actions/setup-node@v3
+      with:
+        node-version: 20.x
+      if: steps.cache-build.outputs.cache-hit != 'true'
+
+    - name: Install pnpm
+      uses: pnpm/action-setup@v2
+      if: steps.cache-build.outputs.cache-hit != 'true'
+
+    - name: Install dependencies
+      run: pnpm install --config.platform=linux --config.architecture=x64
+      if: steps.cache-build.outputs.cache-hit != 'true'
+      shell: bash
+
+    - name: create .env
+      run: cp .env.example .env
+      shell: bash
+
+    - name: Generate Random ENCRYPTION_KEY
+      run: |
+        SECRET=$(openssl rand -hex 32)
+        echo "ENCRYPTION_KEY=$SECRET" >> $GITHUB_ENV
+      shell: bash
+
+    - run: |
+        pnpm build --filter=web...
+
+      if: steps.cache-build.outputs.cache-hit != 'true'
+      shell: bash

.github/actions/dangerous-git-checkout/action.yml

@@ -0,0 +1,10 @@
+name: Dangerous git Checkout
+description: "Git Checkout from PR code so we can run checks from forks"
+runs:
+  using: "composite"
+  steps:
+    - name: Checkout repo
+      uses: actions/checkout@v3
+      with:
+        ref: ${{ github.event.pull_request.head.sha }}
+        fetch-depth: 2

.github/workflows/build-formbricks-com.yml

@@ -1,4 +1,4 @@
-name: Build
+name: Build formbricks-com
 on:
   workflow_call:
 jobs:
@@ -11,10 +11,10 @@ jobs:
       - name: Checkout repo
         uses: actions/checkout@v3
 
-      - name: Setup Node.js 18.x
+      - name: Setup Node.js 20.x
         uses: actions/setup-node@v3
         with:
-          node-version: 18.x
+          node-version: 20.x
 
       - name: Install pnpm
         uses: pnpm/action-setup@v2

.github/workflows/build-web.yml

@@ -1,4 +1,4 @@
-name: Build
+name: Build web
 on:
   workflow_call:
 jobs:
@@ -8,13 +8,13 @@ jobs:
     timeout-minutes: 30
 
     steps:
-      - name: Checkout repo
-        uses: actions/checkout@v3
+      - uses: actions/checkout@v3
+      - uses: ./.github/actions/dangerous-git-checkout
 
-      - name: Setup Node.js 18.x
+      - name: Setup Node.js 20.x
         uses: actions/setup-node@v3
         with:
-          node-version: 18.x
+          node-version: 20.x
 
       - name: Install pnpm
         uses: pnpm/action-setup@v2
@@ -25,7 +25,7 @@ jobs:
       - name: create .env
         run: cp .env.example .env
 
-      - name: Generate Random NEXTAUTH_SECRET
+      - name: Generate Random ENCRYPTION_KEY
         run: |
           SECRET=$(openssl rand -hex 32)
           echo "ENCRYPTION_KEY=$SECRET" >> $GITHUB_ENV

.github/workflows/cron-reportUsageToStripe.yml

@@ -4,8 +4,8 @@ on:
   # "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 22:00 UTC every day of every month.
-    - cron: "0 22 * * *"
+    # This will run the job at 20:00 UTC every day of every month.
+    - cron: "0 20 * * *"
 jobs:
   cron-reportUsageToStripe:
     env:

.github/workflows/e2e.yml

@@ -0,0 +1,75 @@
+name: E2E Tests
+on:
+  workflow_call:
+  workflow_dispatch:
+jobs:
+  build:
+    name: Run E2E Tests
+    runs-on: ubuntu-latest
+    timeout-minutes: 60
+    steps:
+      - uses: actions/checkout@v3
+      - uses: ./.github/actions/dangerous-git-checkout
+
+      - name: Build & Cache Web Binaries
+        uses: ./.github/actions/cache-build-web
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v2
+
+      - name: Install dependencies
+        run: pnpm install
+
+      - name: Start PostgreSQL
+        run: |
+          cd packages/database && pnpm db:up &
+          for attempt in {1..20}; do
+            if nc -zv localhost 5432; then
+              echo "Ready"
+              break
+            fi
+            echo "Waiting..."
+            sleep 5
+          done
+          pnpm db:migrate:dev
+      - name: Serve packages for lazy loading
+        run: |
+          cd packages/surveys && pnpm serve &
+
+      - name: Run App
+        run: |
+          NODE_ENV=test pnpm start --filter=web &
+          for attempt in {1..20}; do
+            if [ $(curl -o /dev/null -s -w "%{http_code}" http://localhost:3000/health) -eq 200 ]; then
+              echo "Ready"
+              break
+            fi
+            echo "Waiting..."
+            sleep 10
+          done
+
+      - name: Test Serve endpoints
+        run: |
+          curl -s http://localhost:3003
+
+      - name: Cache Playwright
+        uses: actions/cache@v3
+        id: playwright-cache
+        with:
+          path: ~/.cache/ms-playwright
+          key: ${{ runner.os }}-playwright-${{ hashFiles('pnpm-lock.yaml') }}
+
+      - name: Install Playwright
+        if: steps.playwright-cache.outputs.cache-hit != 'true'
+        run: pnpm exec playwright install --with-deps
+
+      - name: Run E2E Tests
+        run: |
+          pnpm test:e2e
+
+      - uses: actions/upload-artifact@v3
+        if: always()
+        with:
+          name: playwright-report
+          path: playwright-report/
+          retention-days: 30

.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/lint.yml

@@ -8,8 +8,8 @@ jobs:
     timeout-minutes: 15
 
     steps:
-      - name: Checkout repo
-        uses: actions/checkout@v3
+      - uses: actions/checkout@v3
+      - uses: ./.github/actions/dangerous-git-checkout
 
       - name: Setup Node.js 18.x
         uses: actions/setup-node@v3

.github/workflows/playwright.yml

@@ -1,40 +0,0 @@
-name: E2E Tests
-on:
-  workflow_call:
-jobs:
-  build:
-    name: Run E2E Tests
-    runs-on: ubuntu-latest
-    timeout-minutes: 60
-
-    steps:
-      - uses: actions/checkout@v3
-
-      - uses: actions/setup-node@v3
-        with:
-          node-version: 20
-
-      - name: Install Docker Compose
-        run: sudo apt-get update && sudo apt-get install -y docker-compose
-
-      - name: Install dependencies
-        run: npm install -g pnpm && pnpm install
-
-      - name: Build Formricks JS package
-        run: pnpm build --filter=js
-
-      - name: Build Formbricks Image & Run
-        run: docker-compose up -d
-
-      - name: Install Playwright Browsers
-        run: pnpm exec playwright install --with-deps
-
-      - name: Run Playwright tests
-        run: pnpm test:e2e
-
-      - uses: actions/upload-artifact@v3
-        if: always()
-        with:
-          name: playwright-report
-          path: playwright-report/
-          retention-days: 30

.github/workflows/pr.yml

@@ -12,24 +12,49 @@ concurrency:
   cancel-in-progress: true
 
 jobs:
+  changes:
+    name: Detect changes
+    runs-on: ubuntu-latest
+    permissions:
+      pull-requests: read
+    outputs:
+      has-files-requiring-all-checks: ${{ steps.filter.outputs.has-files-requiring-all-checks }}
+    steps:
+      - uses: actions/checkout@v3
+      - uses: ./.github/actions/dangerous-git-checkout
+      - uses: dorny/paths-filter@v2
+        id: filter
+        with:
+          filters: |
+            has-files-requiring-all-checks:
+              - "!(**.md|.github/CODEOWNERS)"
+
   test:
     name: Run Tests
+    needs: [changes]
+    if: ${{ needs.changes.outputs.has-files-requiring-all-checks == 'true' }}
     uses: ./.github/workflows/test.yml
     secrets: inherit
 
   lint:
     name: Run Linters
+    needs: [changes]
+    if: ${{ needs.changes.outputs.has-files-requiring-all-checks == 'true' }}
     uses: ./.github/workflows/lint.yml
     secrets: inherit
 
   build:
     name: Build Formbricks-web
+    needs: [changes]
+    if: ${{ needs.changes.outputs.has-files-requiring-all-checks == 'true' }}
     uses: ./.github/workflows/build-web.yml
     secrets: inherit
 
   e2e-test:
     name: Run E2E Tests
-    uses: ./.github/workflows/playwright.yml
+    needs: [changes]
+    if: ${{ needs.changes.outputs.has-files-requiring-all-checks == 'true' }}
+    uses: ./.github/workflows/e2e.yml
     secrets: inherit
 
   required:

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

@@ -0,0 +1,70 @@
+name: Docker for Data Migrations
+
+# 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:
+  workflow_dispatch:
+  push:
+    tags:
+      - "v*"
+
+env:
+  # Use docker.io for Docker Hub if empty
+  REGISTRY: ghcr.io
+  IMAGE_NAME: formbricks/data-migrations
+  DATABASE_URL: "postgresql://postgres:postgres@postgres:5432/formbricks?schema=public"
+
+jobs:
+  build-and-push:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write
+      # This is used to complete the identity challenge
+      # with sigstore/fulcio when running outside of PRs.
+      id-token: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v3
+
+      - name: Install cosign
+        if: github.event_name != 'pull_request'
+        uses: sigstore/cosign-installer@6e04d228eb30da1757ee4e1dd75a0ec73a653e06 #v3.1.1
+        with:
+          cosign-release: "v2.1.1"
+
+      - name: Log in to GitHub Container Registry
+        uses: docker/login-action@v3
+        with:
+          registry: ${{ env.REGISTRY }}
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Extract Docker metadata
+        id: meta
+        uses: docker/metadata-action@v5
+        with:
+          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
+          tags: |
+            type=ref,event=tag
+            type=raw,value=${{ github.ref_name }}
+
+      - name: Build and push Docker image
+        uses: docker/build-push-action@v3
+        with:
+          context: .
+          file: ./packages/database/Dockerfile
+          push: true
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
+          build-args: |
+            DATABASE_URL=${{ env.DATABASE_URL }}
+
+      - name: Sign the published Docker image
+        if: ${{ github.event_name != 'pull_request' }}
+        run: |
+          cosign sign --yes ghcr.io/${{ env.IMAGE_NAME }}:${{ github.ref_name }}

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

@@ -44,6 +44,9 @@ jobs:
       - name: Checkout repository
         uses: actions/checkout@v3
 
+      - name: Set up Depot CLI
+        uses: depot/setup-action@v1
+
       # Install the cosign tool except on PR
       # https://github.com/sigstore/cosign-installer
       - name: Install cosign
@@ -52,17 +55,6 @@ jobs:
         with:
           cosign-release: "v2.1.1"
 
-        # Add support for more platforms with QEMU (optional)
-        # https://github.com/docker/setup-qemu-action
-      - name: Set up QEMU
-        uses: docker/setup-qemu-action@v3
-
-      # Set up BuildKit Docker container builder to be able to build
-      # multi-platform images and export cache
-      # https://github.com/docker/setup-buildx-action
-      - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@v3 # v3.0.0
-
       # Login against a Docker registry except on PR
       # https://github.com/docker/login-action
       - name: Log into registry ${{ env.REGISTRY }}
@@ -85,11 +77,13 @@ jobs:
       # https://github.com/docker/build-push-action
       - name: Build and push Docker image
         id: build-and-push
-        uses: docker/build-push-action@v5 # v5.0.0
+        uses: depot/build-push-action@v1
         with:
+          project: tw0fqmsx3c
+          token: ${{ secrets.DEPOT_PROJECT_TOKEN }}
           context: .
           file: ./apps/web/Dockerfile
-          # platforms: linux/amd64,linux/arm64
+          platforms: linux/amd64,linux/arm64
           push: ${{ github.event_name != 'pull_request' }}
           tags: ${{ steps.meta.outputs.tags }}
           labels: ${{ steps.meta.outputs.labels }}

.github/workflows/test.yml

@@ -7,18 +7,14 @@ jobs:
     runs-on: ubuntu-latest
     timeout-minutes: 15
 
-    env:
-      TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
-      TURBO_TEAM: ${{ secrets.TURBO_TEAM }}
-
     steps:
-      - name: Checkout repo
-        uses: actions/checkout@v3
+      - uses: actions/checkout@v3
+      - uses: ./.github/actions/dangerous-git-checkout
 
-      - name: Setup Node.js 18.x
+      - name: Setup Node.js 20.x
         uses: actions/setup-node@v3
         with:
-          node-version: 18.x
+          node-version: 20.x
 
       - name: Install pnpm
         uses: pnpm/action-setup@v2
@@ -34,8 +30,5 @@ jobs:
           SECRET=$(openssl rand -hex 32)
           echo "ENCRYPTION_KEY=$SECRET" >> $GITHUB_ENV
 
-      - name: Build formbricks-js dependencies
-        run: pnpm build --filter=js
-
       - name: Test
         run: pnpm test

.gitignore

@@ -51,3 +51,6 @@ Zone.Identifier
 /playwright-report/
 /blob-report/
 /playwright/.cache/
+
+# uploads
+packages/lib/uploads

README.md

@@ -1,50 +1,46 @@
-<div  id="top"></div>
+<div id="top"></div>
 
-<p  align="center">
+<p align="center">
 
-<a  href="https://formbricks.com">
+<a href="https://formbricks.com">
 
-<img  width="120"  alt="Open Source Privacy First Experience Management Solution Qualtrics Alternative Logo"  src="https://github.com/formbricks/formbricks/assets/72809645/0086704f-bee7-4d38-9cc8-fa42ee59e004">
+<img width="120" alt="Open Source Privacy First Experience Management Solution Qualtrics Alternative Logo" src="https://github.com/formbricks/formbricks/assets/72809645/0086704f-bee7-4d38-9cc8-fa42ee59e004">
 
 </a>
 
-<h3  align="center">Formbricks</h3>
+<h3 align="center">Formbricks</h3>
 
-<p  align="center">
+<p align="center">
 Harvest user-insights, build irresistible experiences.
-<br  />
-<a  href="https://formbricks.com/">Website</a> | <a  href="https://formbricks.com/discord">Join Discord community</a>
+<br />
+<a href="https://formbricks.com/">Website</a> | <a href="https://formbricks.com/discord">Join Discord community</a>
 </p>
 </p>
 
-<p  align="center">
-<a  href="https://github.com/formbricks/formbricks/blob/main/LICENSE"><img  src="https://img.shields.io/badge/License-AGPL-purple"  alt="License"></a> <a  href="https://formbricks.com/discord"><img  src="https://img.shields.io/discord/979077669410979880?label=Discord&logo=discord&logoColor=%23fff"  alt="Join Formbricks Discord"></a> <a  href="https://github.com/formbricks/formbricks/stargazers"><img  src="https://img.shields.io/github/stars/formbricks/formbricks?logo=github"  alt="Github Stars"></a>
-<a  href="https://news.ycombinator.com/item?id=32303986"><img  src="https://img.shields.io/badge/Hacker%20News-122-%23FF6600"  alt="Hacker News"></a>
-<a  href="[https://www.producthunt.com/products/formbricks](https://www.producthunt.com/posts/formbricks)"><img  src="https://img.shields.io/badge/Product%20Hunt-455-orange?logo=producthunt&logoColor=%23fff"  alt="Product Hunt"></a>
-<a  href="https://github.blog/2023-04-12-github-accelerator-our-first-cohort-and-whats-next/"><img  src="https://img.shields.io/badge/2023-blue?logo=github&label=Github%20Accelerator"  alt="Github Accelerator"></a>
-<a  href="https://github.com/formbricks/formbricks/issues?q=is:issue+is:open+label:%22%F0%9F%99%8B%F0%9F%8F%BB%E2%80%8D%E2%99%82%EF%B8%8Fhelp+wanted%22"><img  src="https://img.shields.io/badge/Help%20Wanted-Contribute-blue"></a>
+<p align="center">
+<a href="https://github.com/formbricks/formbricks/blob/main/LICENSE"><img src="https://img.shields.io/badge/License-AGPL-purple" alt="License"></a> <a href="https://formbricks.com/discord"><img src="https://img.shields.io/discord/979077669410979880?label=Discord&logo=discord&logoColor=%23fff" alt="Join Formbricks Discord"></a> <a href="https://github.com/formbricks/formbricks/stargazers"><img src="https://img.shields.io/github/stars/formbricks/formbricks?logo=github" alt="Github Stars"></a>
+<a href="https://news.ycombinator.com/item?id=32303986"><img src="https://img.shields.io/badge/Hacker%20News-122-%23FF6600" alt="Hacker News"></a>
+<a href="[https://www.producthunt.com/products/formbricks](https://www.producthunt.com/posts/formbricks)"><img src="https://img.shields.io/badge/Product%20Hunt-455-orange?logo=producthunt&logoColor=%23fff" alt="Product Hunt"></a>
+<a href="https://github.blog/2023-04-12-github-accelerator-our-first-cohort-and-whats-next/"><img src="https://img.shields.io/badge/2023-blue?logo=github&label=Github%20Accelerator" alt="Github Accelerator"></a>
+<a href="https://github.com/formbricks/formbricks/issues?q=is:issue+is:open+label:%22%F0%9F%99%8B%F0%9F%8F%BB%E2%80%8D%E2%99%82%EF%B8%8Fhelp+wanted%22"><img src="https://img.shields.io/badge/Help%20Wanted-Contribute-blue"></a>
 </p>
 
 <br/>
 
 <div style="background-color:#f8fafc; border-radius:5px;">
-<p  align="center">
-<i>Trusted by</i>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-<a  href="https://flixbus.com"><img  src="https://github.com/formbricks/formbricks/assets/72809645/d6c91d89-7633-4845-ae1e-03bbd2ce0946"  height="35px"></a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-<a  href="https://github.com/calcom/cal.com/"><img  src="https://github.com/formbricks/formbricks/assets/675065/1a8763cf-f47e-4960-90f6-334f6dc12a17#gh-light-mode-only"  height="20px"></a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-<a  href="https://github.com/CrowdDotDev/crowd.dev"><img  src="https://github.com/formbricks/formbricks/assets/675065/59b1a4d4-25e4-4ef3-b0bf-4426446fbfd0#gh-light-mode-only"  height="20px"></a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-<a  href="https://neverinstall.com/"><img  src="https://github.com/formbricks/formbricks/assets/675065/72e5e37b-8ef7-4340-b06e-f1d12a05330f#gh-light-mode-only"  height="20px"></a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-<a  href="https://clovyr.io/"><img  src="https://github.com/formbricks/formbricks/assets/675065/9291c8df-9aac-423a-a430-a9a581240075"  height="20px"></a>
+<p align="center">
+<i>Trusted by</i><br/>
+  <img width="867" alt="clients-hi-res" src="https://github.com/formbricks/formbricks/assets/72809645/924d3693-f66a-4063-bb31-6e5789a8175a">
 </p>
 <div>
 
-<p  align="center">
-<a  href="https://trendshift.io/repositories/2570"  target="_blank"><img  src="https://trendshift.io/api/badge/repositories/2570"  alt="Trendshift Badge for formbricks/formbricks"  style="width: 250px; height: 55px;"  width="250"  height="55"/></a>
+<p align="center">
+<a href="https://trendshift.io/repositories/2570" target="_blank"><img src="https://trendshift.io/api/badge/repositories/2570" alt="Trendshift Badge for formbricks/formbricks" style="width: 250px; height: 55px;" width="250" height="55"/></a>
 </p>
 
 ## ✨ About Formbricks
 
-<img  width="1527"  alt="formbricks-sneak"  src="https://github-production-user-asset-6210df.s3.amazonaws.com/675065/249441967-ccb89ea3-82b4-4bf2-8d2c-528721ec313b.png">
+<img width="1527" alt="formbricks-sneak" src="https://github-production-user-asset-6210df.s3.amazonaws.com/675065/249441967-ccb89ea3-82b4-4bf2-8d2c-528721ec313b.png">
 
 Formbricks provides a free and open source surveying platform. Gather feedback at every point in the user journey with beautiful in-app, website, link and email surveys. Build on top of Formbricks or leverage prebuilt data analysis capabilities.
 
@@ -70,11 +66,11 @@ Formbricks is both a free and open source survey platform - and a privacy-first
 
 - [Contact](#contact-us)
 
-- [License](#license)
-
 - [Security](#security)
 
-<a  id="features"></a>
+- [License](#license)
+
+<a id="features"></a>
 
 ### Features
 
@@ -108,26 +104,26 @@ Formbricks is both a free and open source survey platform - and a privacy-first
 
 - 🧘‍♂️ [Zod](https://zod.dev/)
 
-<a  id="getting-started"></a>
+- 🐛 [Vitest](https://vitest.dev/)
+
+<a id="getting-started"></a>
 
 ## 🚀 Getting started
 
 We've got several options depending on your need to help you quickly get started with Formbricks.
 
-<a  id="cloud-version"></a>
+<a id="cloud-version"></a>
 
 ### ☁️ Cloud Version
 
 Formbricks has a hosted cloud offering with a generous free plan to get you up and running as quickly as possible. To get started, please visit [formbricks.com](https://app.formbricks.com/auth/signup).
 
-<a  id="self-hosted-version"></a>
+<a id="self-hosted-version"></a>
 
 ### 🐳 Self-hosting Formbricks
 
 Formbricks is available Open-Source under AGPLv3 license. You can host Formbricks on your own servers using Docker without a subscription.
 
-(In the future we may develop additional features that aren't in the free Open-Source version).
-
 If you opt for self-hosting Formbricks, here are a few options to consider:
 
 #### Docker
@@ -142,11 +138,11 @@ 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)
 
-<a  id="development"></a>
+<a id="development"></a>
 
-### 👨‍💻 Development
+## 👨‍💻 Development
 
-#### Prerequisites
+### Prerequisites
 
 Here is what you need to be able to run Formbricks:
 
@@ -156,11 +152,11 @@ Here is what you need to be able to run Formbricks:
 
 - [Docker](https://www.docker.com/) - to run PostgreSQL and MailHog
 
-#### Local Setup
+### Local Setup
 
 To get started locally, we've got a [guide to help you](https://formbricks.com/docs/contributing/setup).
 
-#### Gitpod Setup
+### Gitpod Setup
 
 1. Click the button below to open this project in Gitpod.
 
@@ -168,7 +164,7 @@ To get started locally, we've got a [guide to help you](https://formbricks.com/d
 
 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/formbricks/formbricks)
 
-<a  id="contribution"></a>
+<a id="contribution"></a>
 
 ## ✍️ Contribution
 
@@ -186,30 +182,46 @@ Please check out [our contribution guide](https://formbricks.com/docs/contributi
 
 ## All Thanks To Our Contributors
 
-<a  href="https://github.com/formbricks/formbricks/graphs/contributors">
+<a href="https://github.com/formbricks/formbricks/graphs/contributors">
 
-<img  src="https://contrib.rocks/image?repo=formbricks/formbricks"  />
+<img src="https://contrib.rocks/image?repo=formbricks/formbricks" />
 
 </a>
 
-<a  id="contact-us"></a>
+<a id="contact-us"></a>
 
 ## 📆 Contact us
 
 Let's have a chat about your survey needs and get you started.
 
-<a  href="https://cal.com/johannes/onboarding?utm_source=banner&utm_campaign=oss"><img  alt="Book us with Cal.com"  src="https://cal.com/book-with-cal-dark.svg"  /></a>
+<a href="https://cal.com/johannes/onboarding?utm_source=banner&utm_campaign=oss"><img alt="Book us with Cal.com" src="https://cal.com/book-with-cal-dark.svg" /></a>
 
-<a  id="license"></a>
+<a id="license"></a>
 
-## ⚖️ License
-
-Distributed under the AGPLv3 License. See [`LICENSE`](./LICENSE) for more information.
-
-<a  id="security"></a>
+<a id="security"></a>
 
 ## 🔒 Security
 
 We take security very seriously. If you come across any security vulnerabilities, please disclose them by sending an email to security@formbricks.com. We appreciate your help in making our platform as secure as possible and are committed to working with you to resolve any issues quickly and efficiently. See [`SECURITY.md`](./SECURITY.md) for more information.
 
-<p  align="right"><a  href="#top">🔼 Back to top</a></p>
+<a id="license"></a>
+
+## 👩‍⚖️ License
+
+### The AGPL Formbricks Core
+
+The Formbricks core application is licensed under the [AGPLv3 Open Source License](https://github.com/formbricks/formbricks/blob/main/LICENSE). The core application is fully functional and includes everything you need to design & run link surveys, website surveys and in-app surveys. You can use the software for free for personal and commercial use. You're also allowed to create and distribute modified versions as long as you document the changes you make incl. date. The AGPL license requires you to publish your modified version under the AGPLv3 license as well.
+
+### The Enterprise Edition
+
+Additional to the AGPL licensed Formbricks core, this repository contains code licensed under an Enterprise license. The [code](https://github.com/formbricks/formbricks/tree/main/packages/ee) and [license](https://github.com/formbricks/formbricks/blob/main/packages/ee/LICENSE) for the enterprise functionality can be found in the `/packages/ee` folder of this repository. 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/enterprise) to unlock it.
+
+### White-Labeling Formbricks and Other Licensing Needs
+
+If you have other licensing requirements such as White-Labeling please [send us an email](mailto:hola@formbricks.com).
+
+### Why charge for Enterprise Features?
+
+The Enterprise Edition and White-Label Licenses allow us to fund the development of Formbricks sustainably. It guarantees that the open-source surveying infrastructure we're building will be around for decades to come.
+
+<p align="right"><a href="#top">🔼 Back to top</a></p>

apps/demo/package.json

@@ -13,7 +13,7 @@
   "dependencies": {
     "@formbricks/js": "workspace:*",
     "@heroicons/react": "^2.1.1",
-    "next": "14.0.4",
+    "next": "14.1.0",
     "react": "18.2.0",
     "react-dom": "18.2.0"
   },

apps/demo/pages/_document.tsx

@@ -2,7 +2,7 @@ import { Head, Html, Main, NextScript } from "next/document";
 
 export default function Document() {
   return (
-    <Html lang="en" className="h-full bg-gray-50">
+    <Html lang="en" className="h-full bg-slate-50">
       <Head />
       <body className="h-full">
         <Main />

apps/demo/pages/app/index.tsx

@@ -23,13 +23,12 @@ export default function AppPage({}) {
   useEffect(() => {
     if (process.env.NEXT_PUBLIC_FORMBRICKS_ENVIRONMENT_ID && process.env.NEXT_PUBLIC_FORMBRICKS_API_HOST) {
       const isUserId = window.location.href.includes("userId=true");
-      const userId = isUserId ? "THIS-IS-A-VERY-LONG-USER-ID-FOR-TESTING" : undefined;
       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,
-        debug: true,
         attributes,
       });
       window.formbricks = formbricks;
@@ -100,22 +99,22 @@ export default function AppPage({}) {
         </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-gray-600 dark:bg-gray-800">
+          <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-gray-300">
-              On formbricks.reset() a few things happen: <strong>New person is created</strong> and{" "}
-              <strong>surveys & no-code actions are pulled from Formbricks:</strong>.
+            <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-gray-700 dark:hover:bg-gray-600"
+              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={() => {
                 formbricks.reset();
               }}>
               Reset
             </button>
-            <p className="text-xs text-slate-700 dark:text-gray-300">
+            <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>
@@ -124,7 +123,7 @@ export default function AppPage({}) {
           <div className="p-6">
             <div>
               <button
-                className="mb-4 rounded-lg bg-slate-800 px-6 py-3 text-white hover:bg-slate-700 dark:bg-gray-700 dark:hover:bg-gray-600"
+                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={() => {
                   formbricks.track("Code Action");
                 }}>
@@ -132,7 +131,7 @@ export default function AppPage({}) {
               </button>
             </div>
             <div>
-              <p className="text-xs text-slate-700 dark:text-gray-300">
+              <p className="text-xs text-slate-700 dark:text-slate-300">
                 This button sends a{" "}
                 <a href="https://formbricks.com/docs/actions/code" className="underline" target="_blank">
                   Code Action
@@ -143,12 +142,12 @@ export default function AppPage({}) {
           </div>
           <div className="p-6">
             <div>
-              <button className="mb-4 rounded-lg bg-slate-800 px-6 py-3 text-white hover:bg-slate-700  dark:bg-gray-700 dark:hover:bg-gray-600">
+              <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">
                 No-Code Action
               </button>
             </div>
             <div>
-              <p className="text-xs text-slate-700 dark:text-gray-300">
+              <p className="text-xs text-slate-700 dark:text-slate-300">
                 This button sends a{" "}
                 <a
                   href="https://formbricks.com/docs/actions/no-code"
@@ -172,12 +171,12 @@ export default function AppPage({}) {
                 onClick={() => {
                   formbricks.setAttribute("Plan", "Free");
                 }}
-                className="mb-4 rounded-lg bg-slate-800 px-6 py-3 text-white hover:bg-slate-700  dark:bg-gray-700 dark:hover:bg-gray-600">
+                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;
               </button>
             </div>
             <div>
-              <p className="text-xs text-slate-700 dark:text-gray-300">
+              <p className="text-xs text-slate-700 dark:text-slate-300">
                 This button sets the{" "}
                 <a
                   href="https://formbricks.com/docs/attributes/custom-attributes"
@@ -195,12 +194,12 @@ export default function AppPage({}) {
                 onClick={() => {
                   formbricks.setAttribute("Plan", "Paid");
                 }}
-                className="mb-4 rounded-lg bg-slate-800 px-6 py-3 text-white hover:bg-slate-700  dark:bg-gray-700 dark:hover:bg-gray-600">
+                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;
               </button>
             </div>
             <div>
-              <p className="text-xs text-slate-700 dark:text-gray-300">
+              <p className="text-xs text-slate-700 dark:text-slate-300">
                 This button sets the{" "}
                 <a
                   href="https://formbricks.com/docs/attributes/custom-attributes"
@@ -218,12 +217,12 @@ export default function AppPage({}) {
                 onClick={() => {
                   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-gray-700 dark:hover:bg-gray-600">
+                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
               </button>
             </div>
             <div>
-              <p className="text-xs text-slate-700 dark:text-gray-300">
+              <p className="text-xs text-slate-700 dark:text-slate-300">
                 This button sets the{" "}
                 <a
                   href="https://formbricks.com/docs/attributes/identify-users"
@@ -242,7 +241,7 @@ export default function AppPage({}) {
                   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-gray-700 dark:hover:bg-gray-600">
+                  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>
@@ -252,13 +251,13 @@ export default function AppPage({}) {
                   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-gray-700 dark:hover:bg-gray-600">
+                  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-gray-300">
+              <p className="text-xs text-slate-700 dark:text-slate-300">
                 This button activates/deactivates{" "}
                 <a
                   href="https://formbricks.com/docs/attributes/identify-users"

apps/formbricks-com/app/docs/actions/code/page.mdx

@@ -1,37 +0,0 @@
-export const metadata = {
-  title: "Implementing Code Actions in Formbricks | Real-time User Action Tracking",
-  description:
-    "Dive into the world of Formbricks' code actions. Learn how to seamlessly integrate formbricks.track() method into your codebase, enabling real-time tracking of user actions like button clicks, visiting a specific URL. Up your survey game with precise and exact triggers.",
-};
-
-#### Actions
-
-# Code Actions
-
-Actions can also be set in the codebase to trigger surveys. Please add the code action first in the Formbricks web interface to be able to configure your surveys to use this action.
-
-After that you can fire an action using `formbricks.track()`
-
-<Col>
-<CodeGroup title="Track an action">
-
-```javascript
-formbricks.track("Action Name");
-```
-
-</CodeGroup>
-</Col>
-Here is an example of how to fire an action when a user clicks a button:
-<Col>
-<CodeGroup title="Track Button Click">
-
-```javascript
-const handleClick = () => {
-  formbricks.track("Button Clicked");
-};
-
-return <button onClick={handleClick}>Click Me</button>;
-```
-
-</CodeGroup>
-</Col>

apps/formbricks-com/app/docs/actions/no-code/page.mdx

@@ -1,30 +0,0 @@
-export const metadata = {
-  title: "Implementing No-Code Actions in Formbricks | Real-time User Action Tracking",
-  description:
-    "Discover the power of Formbricks' No-Code Actions. Easily set up triggers based on Page URL, innerText, and CSS Selectors without touching a line of code. Inccrease user engagement and get insights at precise moments in the user journey.",
-};
-
-#### Actions
-
-# No-Code Actions
-
-No-Code actions can be set up within Formbricks with just a few clicks. There are three types of No-Code actions:
-
-## Page URL Action
-
-The page URL action is triggered, when a user visits a specific page in your application. There are several match conditions:
-
-- `exactMatch`: The URL should exactly match the provided string.
-- `contains`: The URL should contain the specified string as a substring.
-- `startsWith`: The URL should start with the specified string.
-- `endsWith`: The URL should end with the specified string.
-- `notMatch`: The URL should not match the specified condition.
-- `notContains`: The URL should not contain the specified string as a substring.
-
-## innerText Action
-
-The innerText action checks if the `innerText` of a clicked HTML element matches a specific text, e.g. the label of a button. Display a survey on any button click!
-
-## CSS Selector Action
-
-The CSS Selector action checks if the provided CSS selector matches the selector of a clicked HTML element. The CSS selector can be a class, id or any other CSS selector within your website. Display a survey on any element click!

apps/formbricks-com/app/docs/actions/why/page.mdx

@@ -1,23 +0,0 @@
-export const metadata = {
-  title: "Using Actions in Formbricks | Fine-tuning User Moments",
-  description:
-    "Dive deep into how actions in Formbricks help products and teams to engage users at precise moments in their journey. Discover the power of actions, from coding to no-code setups, to refine user targeting and generate richer, more detailed user insights.",
-};
-
-#### Actions
-
-# What are actions and why are they useful?
-
-You want to understand what your users think and feel during specific moments in the user journey. To be able to ask at exactly the right point in time, you need actions.
-
-## What are actions?
-
-Actions are a little notification sent from your application to Formbricks. You decide which actions are sent either in your [Code](/docs/actions/code) or by setting up a [No-Code](/docs/actions/no-code) action within Formbricks.
-
-## How do actions work?
-
-When a predefined action happens in your app, the Formbricks widget notices. This action can then trigger a survey to be shown to the user and is stored in the database.
-
-## Why are actions useful?
-
-Actions help you to display your surveys at the right time. Later on, you will be able to segment your users based on the actions they have triggered in the past. This way, you can create much more granular user segments, e.g. only target users that already have used a specific feature.

apps/formbricks-com/app/docs/api/client/actions/page.mdx

@@ -1,7 +1,7 @@
 import { Fence } from "@/components/shared/Fence";
 
 export const metadata = {
-  title: "Formbricks Responses API Documentation - Manage Your Survey Data Seamlessly",
+  title: "Formbricks Actions API Documentation - Manage Your Survey Data Seamlessly",
   description:
     "Unlock the full potential of Formbricks' Client Actions API. Create Actions right from the API.",
 };
@@ -13,8 +13,8 @@ export const metadata = {
 The Public Client API is designed for the JavaScript SDK and does not require authentication. It's primarily used for creating persons, sessions, and responses within the Formbricks platform. This API is ideal for client-side interactions, as it doesn't expose sensitive information.
 
 This API can be used to:
-- [Add Action for User](#add-action-for-user)
 
+- [Add Action for User](#add-action-for-user)
 
 ---
 
@@ -45,8 +45,7 @@ Adds an Actions for a given User by their User ID
     curl --location --request POST 'https://app.formbricks.com/api/v1/client/<environment-id>/actions' \
     --data-raw '{
         "userId": "1",
-        "name": "new_action_v2",
-        "properties":{}
+        "name": "new_action_v2"
 
     }'
     ```
@@ -54,8 +53,7 @@ Adds an Actions for a given User by their User ID
     ```json {{ title: 'Example Request Body' }}
     {
         "userId": "1",
-        "name": "new_action_v3",
-        "properties":{}
+        "name": "new_action_v3"
     }
     ```
 
@@ -85,4 +83,3 @@ Adds an Actions for a given User by their User ID
 </Row>
 
 ---
-

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

@@ -1,14 +1,16 @@
 import { Fence } from "@/components/shared/Fence";
-import {generateManagementApiMetadata} from "@/lib/utils"
+import { generateManagementApiMetadata } from "@/lib/utils";
 
-export const metadata = generateManagementApiMetadata("Responses",["Fetch","Delete"])
+export const metadata = generateManagementApiMetadata("Responses", ["Fetch", "Delete"]);
 
 #### Management API
 
 # Responses API
 
 This set of API can be used to
+
 - [List Responses](#list-all-responses)
+- [List all Responses by surveyId](#list-all-responses-by-survey-id)
 - [Get Response](#get-response-by-id)
 - [Delete Response](#delete-a-response)
 
@@ -107,6 +109,97 @@ This set of API can be used to
 
 ---
 
+## List all Responses by surveyId {{ tag: 'GET', label: '/api/v1/management/responses?surveyId=<survey-Id>' }}
+
+<Row>
+  <Col>
+
+    Retrieve all the responses received in your survey.
+
+    ### Mandatory Headers
+
+    <Properties>
+      <Property name="x-Api-Key" type="string">
+        Your Formbricks API key.
+      </Property>
+    </Properties>
+
+  </Col>
+  <Col sticky>
+
+    <CodeGroup title="Request" tag="GET" label="/api/v1/management/responses?surveyId=<survey-Id>">
+
+    ```bash {{ title: 'cURL' }}
+    curl --location \
+    'https://app.formbricks.com/api/v1/management/responses?surveyId=<survey-Id>' \
+    --header \
+    'x-api-key: <your-api-key>'
+    ```
+
+    </CodeGroup>
+
+    <CodeGroup title="Response">
+
+    ```json {{title:'200 Success'}}
+    {
+      "data":[
+        {
+            "id": "cln8k0tqv00pcz87no4qrw333",
+            "createdAt": "2023-10-02T07:13:20.023Z",
+            "updatedAt": "2023-10-02T07:13:20.023Z",
+            "surveyId": "cln8k0tqu00p7z87nqr4thi3k",
+            "finished": true,
+            "data": {
+                "interview-prompt": "clicked"
+            },
+            "meta": {
+                "userAgent": {
+                    "os": "MacOS",
+                    "browser": "Chrome"
+                }
+            },
+            "personAttributes": null,
+            "person": {
+                "id": "e0x4i5tvsp8puxfztyrwykvn",
+                "attributes": {
+                    "userId": "CYO675",
+                    "email": "ravi@netflix.com",
+                    "Name": "Ravi Kumar",
+                    "Role": "Manager",
+                    "Company": "Netflix",
+                    "Experience": "6 years",
+                    "Usage Frequency": "Monthly",
+                    "Company Size": "4610 employees",
+                    "Product Satisfaction Score": "43",
+                    "Recommendation Likelihood": "4"
+                },
+                "environmentId": "cln8k0t47000fz87njmmu2bck",
+                "createdAt": "2023-10-02T07:13:19.444Z",
+                "updatedAt": "2023-10-02T07:13:19.444Z"
+            },
+            "notes": [],
+            "tags": []
+        },
+      ]
+    }
+    ```
+
+    ```json {{ title: '401 Not Authenticated' }}
+    {
+      "code": "not_authenticated",
+      "message": "Not authenticated",
+      "details": {
+        "x-Api-Key": "Header not provided or API Key invalid"
+        }
+    }
+    ```
+    </CodeGroup>
+
+  </Col>
+</Row>
+
+---
+
 ## Get Response by ID {{ tag: 'GET', label: '/api/v1/management/responses/<response-id>' }}
 
 <Row>

apps/formbricks-com/app/docs/attributes/custom-attributes/page.mdx

@@ -1,57 +0,0 @@
-export const metadata = {
-  title: "Guide for Setting Custom Attributes | Formbricks Documentation",
-  description:
-    "Learn how to set attributes in code using setAttribute function. Enhance user segmentation, target surveys effectively, and gather valuable insights for better decisions. Easily send user-specific details for better survey segmentation and gain deeper insights.",
-};
-
-#### Attributes
-
-# Setting attributes with code
-
-One way to send attributes to Formbricks is in your code. In Formbricks, there are two special attributes for [user identification](/docs/attributes/identify-users)(user ID & email) and custom attributes. An example:
-
-## Setting during Initialization
-
-It's recommended to set custom user attributes directly during the initialization of Formbricks for better user identification.
-
-<Col>
-<CodeGroup title="Set custom attributes during initialization">
-
-```javascript
-formbricks.init({
-  environmentId: "<environment-id>",
-  apiHost: "<api-host>",
-  userId: "<user_id>",
-  attributes: {
-    plan: "free",
-  },
-});
-```
-
-</CodeGroup>
-</Col>
-
-## Setting independently
-
-You can use the setAttribute function to set any custom attribute for the user (e.g. name, plan, etc.) anywhere in the user journey. Formbricks maintains a state of the current user inside the browser and makes sure attributes aren't sent to the backend twice.
-
-<Col>
-<CodeGroup title="Setting Plan to Pro">
-
-```javascript
-formbricks.setAttribute("Plan", "Pro");
-```
-
-</CodeGroup>
-</Col>
-Generally speaking, the setAttribute function works like this:
-<Col>
-<CodeGroup title="Setting Custom Attributes">
-
-```javascript
-formbricks.setAttribute("attribute_key", "attribute_value");
-```
-
-</CodeGroup>
-</Col>
-Where `attributeName` is the name of the attribute you want to set, and `attributeValue` is the value of the attribute you want to set.

apps/formbricks-com/app/docs/attributes/why/page.mdx

@@ -1,23 +0,0 @@
-export const metadata = {
-  title: "Understanding User Attributes in Formbricks Surveys",
-  description:
-    "Dive into the importance of attributes in surveys. Learn how key-value pairs can significantly improve survey targeting, enhance feedback quality, and guide data-driven decisions with Formbricks.",
-};
-
-#### Attributes
-
-# What are attributes and why are they useful?
-
-Surveying your user base without segmentation leads to weak results and survey fatigue. Attributes help you segment your users into groups.
-
-## What are attributes?
-
-Attributes are key-value pairs that you can set for each person individually. For example, the attribute "Plan" can be set to "Free" or "Paid".
-
-## How do attributes work?
-
-Attributes are sent from your application to Formbricks and are associated with the current user. We store it in our database and allow you to use it the next time you create a survey.
-
-## Why are attributes useful?
-
-Attributes help show surveys to the right group of people. For example, you can show a survey to all users who have a "Plan" attribute set to "Paid".

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

@@ -1,18 +1,19 @@
-import Image from "next/image";
 import DemoPreview from "@/components/dummyUI/DemoPreview";
+import Image from "next/image";
 
-import CreateChurnFlow from "./create-cancel-flow.webp";
 import ChangeText from "./change-text.webp";
-import TriggerInnerText from "./trigger-inner-text.webp";
-import TriggerCSS from "./trigger-css-selector.webp";
-import TriggerPageUrl from "./trigger-page-url.webp";
-import RecontactOptions from "./recontact-options.webp";
+import CreateChurnFlow from "./create-cancel-flow.webp";
 import PublishSurvey from "./publish-survey.webp";
+import RecontactOptions from "./recontact-options.webp";
 import SelectAction from "./select-action.webp";
+import TriggerCSS from "./trigger-css-selector.webp";
+import TriggerInnerText from "./trigger-inner-text.webp";
+import TriggerPageUrl from "./trigger-page-url.webp";
 
 export const metadata = {
   title: "Mastering Churn Surveys with Formbricks | Essential Tips & Steps",
-  description: "Learn how to effectively utilize Formbricks' Churn Surveys to gain deeper insights into user departures. Dive into a step-by-step guide to craft, trigger, and optimize your churn surveys, ensuring you capture invaluable feedback at critical junctures",
+  description:
+    "Learn how to effectively utilize Formbricks' Churn Surveys to gain deeper insights into user departures. Dive into a step-by-step guide to craft, trigger, and optimize your churn surveys, ensuring you capture invaluable feedback at critical junctures",
 };
 
 #### Best Practices
@@ -39,15 +40,16 @@ The Churn Survey is among the most effective ways to identify weaknesses in your
 
 To run the Churn Survey in your app you want to proceed as follows:
 
-1. Create new Churn Survey at [app.formbricks.com](http://app.formbricks.com/)
+1. Create new Churn Survey at [app.formbricks.com](https://app.formbricks.com/)
 2. Set up the user action to display survey at right point in time
 3. Choose correct recontact options to never miss a feedback
 4. Prevent that churn!
 
 <Note>
-  ## 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)
+  ## 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>
 
 ### 1. Create new Churn Survey
@@ -60,7 +62,7 @@ Click on "Create Survey" and choose the template “Churn Survey”:
   src={CreateChurnFlow}
   alt="Create churn survey by template"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 ### 2. Update questions (if you like)
@@ -71,7 +73,7 @@ You’re free to update the question and answer options. However, based on our e
   src={ChangeText}
   alt="Change text content"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 _Want to change the button color? You can do so in the product settings._
@@ -92,7 +94,7 @@ To create the trigger for your Churn Survey, you have two options to choose from
   src={TriggerInnerText}
   alt="Set the trigger by inner Text"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 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:
@@ -101,7 +103,7 @@ To create the trigger for your Churn Survey, you have two options to choose from
   src={TriggerCSS}
   alt="Set the trigger by CSS Selector"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 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:
@@ -110,7 +112,7 @@ To create the trigger for your Churn Survey, you have two options to choose from
   src={TriggerPageUrl}
   alt="Set the trigger by page URL"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 Whenever a user visits this page, matches the filter conditions above and the recontact options (below) the survey will be displayed ✅
@@ -119,9 +121,9 @@ Here is our complete [Actions manual](/docs/actions/why) covering [Code](/docs/a
 
 <Note>
   ## 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 🤷
+  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
@@ -130,7 +132,7 @@ Here is our complete [Actions manual](/docs/actions/why) covering [Code](/docs/a
   src={SelectAction}
   alt="Select feedback button action"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 ### 6. Last step: Set Recontact Options correctly
@@ -141,7 +143,7 @@ Lastly, scroll down to “Recontact Options”. Here you have to choose the corr
   src={RecontactOptions}
   alt="Set recontact options"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 These settings make sure the survey is always displayed, when a user wants to Cancel their subscription.
@@ -152,13 +154,14 @@ These settings make sure the survey is always displayed, when a user wants to Ca
   src={PublishSurvey}
   alt="Publish survey"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  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 Churn Survey in your app. Please follow [this
-  tutorial (Step 4 onwards)](/docs/getting-started/quickstart-in-app-survey) to install the widget.
+  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/feature-chaser/page.mdx

@@ -11,7 +11,8 @@ import SelectAction from "./select-action.webp";
 
 export const metadata = {
   title: "Setting Up Feature Chaser Surveys with Formbricks: A Comprehensive Guide",
-  description: "Learn how to harness the power of Formbricks to gather targeted user feedback on specific features. Dive deep into creating, triggering, and publishing the Feature Chaser survey to enhance your product with actionable insights for specific users.",
+  description:
+    "Learn how to harness the power of Formbricks to gather targeted user feedback on specific features. Dive deep into creating, triggering, and publishing the Feature Chaser survey to enhance your product with actionable insights for specific users.",
 };
 
 #### Best Practices
@@ -38,13 +39,14 @@ Product analytics never tell you why a feature is used - and why not. Following
 
 To run the Feature Chaser survey in your app you want to proceed as follows:
 
-1. Create new Feature Chaser survey at [app.formbricks.com](http://app.formbricks.com/)
+1. Create new Feature Chaser survey at [app.formbricks.com](https://app.formbricks.com/)
 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 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)
+  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>
 
 ### 1. Create new Feature Chaser
@@ -57,7 +59,7 @@ Click on "Create Survey" and choose the template “Feature Chaser”:
   src={CreateSurvey}
   alt="Create survey by template"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 ### 2. Update questions
@@ -68,7 +70,7 @@ The questions you want to ask are dependent on your feature and can be very spec
   src={ChangeText}
   alt="Change text content"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 Save, and move over to where the magic happens: The “Audience” tab.
@@ -87,7 +89,7 @@ There are two ways to track a button:
   src={ActionText}
   alt="Set the trigger by inner Text"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 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:
@@ -96,7 +98,7 @@ There are two ways to track a button:
   src={ActionCSS}
   alt="Set the trigger by CSS Selector"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 Please follow our [Actions manual](/docs/actions/why) for an in-depth description of how Actions work.
@@ -107,7 +109,7 @@ Please follow our [Actions manual](/docs/actions/why) for an in-depth descriptio
   src={SelectAction}
   alt="Select PMF trigger button action"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 ### 5. Last step: Set Recontact Options correctly
@@ -118,17 +120,18 @@ Lastly, scroll down to “Recontact Options”. Here you have full freedom to de
   src={RecontactOptions}
   alt="Set recontact options"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 ### 7. Congrats! You’re ready to publish your survey 💃
 
-<Image src={Publish} alt="Publish survey" quality="100" className="rounded-lg max-w-full 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 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 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/improve-email-content/page.mdx

@@ -0,0 +1,113 @@
+import DemoPreview from "@/components/dummyUI/DemoPreview";
+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:
+    "Measuring the content quality of both transactional and marketing email is a key element for improving customer communication.",
+};
+
+#### 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.
+
+## Preview
+
+<DemoPreview template="Improve Newsletter Content" />
+
+## Formbricks Approach
+
+- Embed the survey into your email so it’s part of the newsletter.
+- Use link prefilling to store the answer users clicked on in the email.
+- Dynamic user identification to append reader's email for personalized profiles and follow ups.
+
+## Installation
+
+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. 
+
+### 1. Create new 'Improve Newsletter Content' Survey
+
+If you don't have an account yet, create one at [app.formbricks.com](https://app.formbricks.com/auth/signup)
+
+Then, create a new survey and look for the "Improve Newsletter Content" template:
+
+<Image
+  src={NewsletterSurvey}
+  alt="Create Improve Newsletter Content by template"
+  quality="100"
+  className="rounded-lg max-w-full sm:max-w-3xl"
+/>
+
+### 2. Customize Survey questions
+
+Customize survey questions, emojis or stars however you like:
+
+<Image
+  src={NewsletterSurveyEditor}
+  alt="Edit Improve Newsletter Content template"
+  quality="100"
+  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:
+
+<Image
+  src={NewsletterSurveyType}
+  alt="Choose survey type"
+  quality="100"
+  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.
+
+<Image
+  src={NewsletterSurveyEmbedPrompt}
+  alt="Embed newsletter survey"
+  quality="100"
+  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.
+
+### 5. Copy code to embed the survey in your newsletter
+
+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:
+
+<Image
+  src={NewsletterSurveyEmbedCode}
+  alt="Embed survey code"
+  quality="100"
+  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 
+
+<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).
+</Note>
+
+### &nbsp;
+
+# That’s it! 🎉

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

@@ -11,7 +11,8 @@ import SelectAction from "./select-action.webp";
 
 export const metadata = {
   title: "Boost Your Trial Conversion Rates with Formbricks: Comprehensive Guide",
-  description: "Unlock the secret to converting more trial users into paying customers using Formbricks. Understand insights behind trial cancellations and tailor your offering to fit user needs. Dive into our step-by-step tutorial and improve your conversion strategy today",
+  description:
+    "Unlock the secret to converting more trial users into paying customers using Formbricks. Understand insights behind trial cancellations and tailor your offering to fit user needs. Dive into our step-by-step tutorial and improve your conversion strategy today",
 };
 
 #### Best Practices
@@ -37,14 +38,15 @@ The better you understand why free users don’t convert to paid users, the high
 
 To display the Trial Conversion Survey in your app you want to proceed as follows:
 
-1. Create new Trial Conversion Survey at [app.formbricks.com](http://app.formbricks.com/)
+1. Create new Trial Conversion Survey at [app.formbricks.com](https://app.formbricks.com/)
 2. Set up the user action to display survey at right point in time
 3. Print that 💸
 
 <Note>
-  ## 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)
+  ## 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>
 
 ### 1. Create new Trial Conversion Survey
@@ -57,7 +59,7 @@ Click on "Create Survey" and choose the template “Improve Trial Conversion”:
   src={CreateSurvey}
   alt="Create survey by template"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 ### 2. Update questions (if you like)
@@ -68,7 +70,7 @@ You’re free to update the questions and answer options. However, based on our
   src={ChangeText}
   alt="Change text content"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 _Want to change the button color? You can do so in the product settings!_
@@ -79,7 +81,8 @@ Save, and move over to the “Audience” tab.
 
 <Note>
   ## Filter by attribute coming soon 
-  We're working on pre-segmenting users by attributes. We will update this manual in the next days.
+  We're working on pre-segmenting users by attributes. We will update this
+  manual in the next days.
 </Note>
 
 Pre-segmentation isn't relevant for this survey because you likely want to solve all people who cancel their trial. You probably have a specific user action e.g. clicking on "Cancel Trial" you can use to only display the survey to users trialing your product.
@@ -94,7 +97,7 @@ How you trigger your survey depends on your product. There are two options:
   src={ActionPageurl}
   alt="Change text content"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 Whenever a user visits this page, the survey will be displayed ✅
@@ -105,7 +108,7 @@ Whenever a user visits this page, the survey will be displayed ✅
   src={ActionText}
   alt="Change text content"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 Please have a look at our complete [Actions manual](/docs/actions/why) if you have questions.
@@ -116,7 +119,7 @@ Please have a look at our complete [Actions manual](/docs/actions/why) if you ha
   src={SelectAction}
   alt="Select feedback button action"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 ### 6. Last step: Set Recontact Options correctly
@@ -127,17 +130,18 @@ Lastly, scroll down to “Recontact Options”. Here you have to choose the corr
   src={RecontactOptions}
   alt="Set recontact options"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 ### 7. Congrats! You’re ready to publish your survey 💃
 
-<Image src={Publish} alt="Publish survey" quality="100" className="rounded-lg max-w-full 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 in your app. Please follow [this
-  tutorial (Step 4 onwards)](/docs/getting-started/quickstart-in-app-survey) to install the widget.
+  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

@@ -14,7 +14,8 @@ import SelectAction from "./select-action.webp";
 
 export const metadata = {
   title: "Maximize User Interview Participation with In-app Interview Prompts",
-  description: "Engage with your power users seamlessly using Formbricks' In-app Interview Prompt. Ditch traditional email invites and experience way more more respondents. Dive into our comprehensive guide on setting up auto-scheduled interviews today and enhance your user understanding",
+  description:
+    "Engage with your power users seamlessly using Formbricks' In-app Interview Prompt. Ditch traditional email invites and experience way more more respondents. Dive into our comprehensive guide on setting up auto-scheduled interviews today and enhance your user understanding",
 };
 
 #### Best Practices
@@ -42,14 +43,15 @@ Product analytics and in-app surveys are incomplete without user interviews. Set
 
 To display an Interview Prompt in your app you want to proceed as follows:
 
-1. Create new Interview Prompt at [app.formbricks.com](http://app.formbricks.com/)
+1. Create new Interview Prompt at [app.formbricks.com](https://app.formbricks.com/)
 2. Adjust content and settings
 3. That’s it! 🎉
 
 <Note>
-  ## 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)
+  ## 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>
 
 ### 1. Create new Interview Prompt
@@ -62,7 +64,7 @@ Click on "Create Survey" and choose the template “Interview Prompt”:
   src={CreatePrompt}
   alt="Create interview prompt by template"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 ### 2. Update prompt and CTA
@@ -73,7 +75,7 @@ Update the prompt, description and button text to match your products tonality.
   src={ChangeText}
   alt="Change text content"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 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!
@@ -82,7 +84,7 @@ In the button settings you have to make sure it is set to “External URL”. In
   src={InterviewExample}
   alt="Add CSS action"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 Save, and move over to the “Audience” tab.
@@ -91,7 +93,8 @@ Save, and move over to the “Audience” tab.
 
 <Note>
   ## Filter by attribute coming soon 
-  We're working on pre-segmenting users by attributes. We will update this manual in the next few days.
+  We're working on pre-segmenting users by attributes. We will update this
+  manual in the next few days.
 </Note>
 
 Once you clicked over to the “Audience” tab you can change the settings. In the **Who To Send** card, select “Filter audience by attribute”. This allows you to only show the prompt to a specific segment of your user base.
@@ -104,12 +107,13 @@ 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:
 
-<Image src={AddAction} alt="Add action" quality="100" className="rounded-lg max-w-full 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 `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>
 
 Generally, we have two types of user actions: Page views and clicks. The Interview Prompt, you’ll likely want to display it on a page visit since you already filter who sees the prompt by attributes.
@@ -120,18 +124,18 @@ Generally, we have two types of user actions: Page views and clicks. The Intervi
   src={ActionPageurl}
   alt="Add page URL action"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 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">
-  <Image src={ActionCSS} alt="Add CSS action" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
+  <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"
-    className="rounded-lg max-w-full sm:max-w-3xl"
+    className="max-w-full rounded-lg sm:max-w-3xl"
   />
 </div>
 
@@ -141,7 +145,7 @@ Generally, we have two types of user actions: Page views and clicks. The Intervi
   src={SelectAction}
   alt="Select feedback button action"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 ### 6. Set Recontact Options correctly
@@ -152,17 +156,18 @@ Scroll down to “Recontact Options”. Here you have to choose the correct sett
   src={RecontactOptions}
   alt="Set recontact options"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 ### 7. Congrats! You’re ready to publish your survey 💃 🤸
 
-<Image src={Publish} alt="Publish survey" quality="100" className="rounded-lg max-w-full 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 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>
 
 ###

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

@@ -11,7 +11,8 @@ import SelectAction from "./select-action.webp";
 
 export const metadata = {
   title: "How to Set Up a Product-Market Fit Survey Using Formbricks - Step-by-Step Guide",
-  description: "Learn to leverage Formbricks to create and implement a Product-Market Fit survey in your web app. Follow our detailed step-by-step guide to measure and understand your PMF effectively. Ensure high data quality, efficient triggers, and actionable insights.",
+  description:
+    "Learn to leverage Formbricks to create and implement a Product-Market Fit survey in your web app. Follow our detailed step-by-step guide to measure and understand your PMF effectively. Ensure high data quality, efficient triggers, and actionable insights.",
 };
 
 #### Best Practices
@@ -36,14 +37,15 @@ Measuring and understanding your PMF is essential to build a large, successful b
 
 To display the Product-Market Fit survey in your app you want to proceed as follows:
 
-1. Create new Product-Market Fit survey at [app.formbricks.com](http://app.formbricks.com/)
+1. Create new Product-Market Fit survey at [app.formbricks.com](https://app.formbricks.com/)
 2. Setup pre-segmentation to assure high data quality
 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 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)
+  ## 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>
 
 ### 1. Create new PMF survey
@@ -56,7 +58,7 @@ Click on "Create Survey" and choose one of the PMF survey templates. The first o
   src={CreateSurvey}
   alt="Create survey by template"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 ### 2. Update questions (if you like)
@@ -67,7 +69,7 @@ You’re free to update the question and answer options. However, based on our e
   src={ChangeText}
   alt="Change text content"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 _Want to change the button color? You can do so in the product settings!_
@@ -77,8 +79,9 @@ 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 manual in the next days.
+  ## Filter by attribute coming soon
+   We're working on pre-segmenting users by attributes. We will update this
+  manual in the next days.
 </Note>
 
 To run this survey properly, you should pre-segment your user base. As touched upon earlier: if you ask every user you’ll get lots of opinions which are often misleading. You only want to gather feedback from people who invested the time to get to know and use your product:
@@ -96,25 +99,31 @@ This way you make sure that you separate potentially misleading opinions from va
 ### 4. Set up a trigger for the Product-Market Fit survey:
 
 You need a trigger to display the survey but in this case, the filtering does all the work. It’s up to you to decide to display the survey after the user viewed a specific subpage (pageURL) or after clicking an element. Have a look at the [Actions manual](/docs/actions/why) if you are not sure how to set them up:
+
 <Col>
-<div>
-  <Image src={ActionCSS} alt="Add CSS action" quality="100" className="rounded-lg max-w-full sm:max-w-3xl" />
-  <Image
-    src={ActionPageurl}
-    alt="Add inner text action"
-    quality="100"
-    className="rounded-lg max-w-full sm:max-w-3xl"
-  />
-</div>
+  <div>
+    <Image
+      src={ActionCSS}
+      alt="Add CSS action"
+      quality="100"
+      className="max-w-full rounded-lg sm:max-w-3xl"
+    />
+    <Image
+      src={ActionPageurl}
+      alt="Add inner text action"
+      quality="100"
+      className="max-w-full rounded-lg sm:max-w-3xl"
+    />
+  </div>
 </Col>
 ### 5. Select Action in the “When to ask” card
 <Col>
-<Image
-  src={SelectAction}
-  alt="Select PMF trigger button action"
-  quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
-/>
+  <Image
+    src={SelectAction}
+    alt="Select PMF trigger button action"
+    quality="100"
+    className="max-w-full rounded-lg sm:max-w-3xl"
+  />
 </Col>
 ### 6. Last step: Set Recontact Options correctly
 
@@ -124,17 +133,18 @@ Lastly, scroll down to “Recontact Options”. Here you have to choose the corr
   src={RecontactOptions}
   alt="Set recontact options"
   quality="100"
-  className="rounded-lg max-w-full sm:max-w-3xl"
+  className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
 ### 7. Congrats! You’re ready to publish your survey 💃
 
-<Image src={Publish} alt="Publish survey" quality="100" className="rounded-lg max-w-full 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 in your app. Please follow [this
-  tutorial (Step 4 onwards)](/docs/getting-started/quickstart-in-app-survey) to install the widget.
+  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/how-we-code/page.mdx

@@ -1,4 +1,5 @@
 import Image from "next/image";
+
 import CorsHandling from "./cors-handling-in-api.webp";
 
 export const metadata = {
@@ -25,7 +26,7 @@ Thank you for choosing to contribute to Formbricks. Before you start, please fam
 - Constants should be in the packages folder
 - Types should be in the packages folder
 - How we handle Pull Requests
-- Read environment variables from `.env.mjs`
+- Read server-side environment variables from `constants.ts`
 
 ---
 
@@ -83,9 +84,9 @@ You should store constants in `packages/lib/constants`
 
 You should store type in `packages/types`
 
-## Read environment variables from `.env.mjs`
+## Read server-side environment variables from `constants.ts`
 
-Environment variables (`process.env`) shouldn’t be accessed directly but be added in the `.env.mjs` and should be accessed from here. This practice helps us ensure that the variables are typesafe.
+Server-side environment variables (`process.env`) shouldn’t be accessed directly but included into the `constants.ts` file and read from there. This way we can assure they are used only on the server side and are also type-safe.
 
 ## How we handle Pull Requests
 

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

@@ -42,6 +42,4 @@ If you are at all unsure, just raise it as an enhancement issue first and tell u
 
 To be able to keep working on Formbricks over the coming years, we need to collect a CLA from all relevant contributors.
 
-Please note that we can only get your contribution merged when we have a CLA signed by you.
-
-To access the CLA form, please click [here](https://formbricks.com/clmyhzfrymr4ko00hycsg1tvx)
+Once you open a PR, you will get a message from the CLA bot to fill out the form. Please note that we can only get your contribution merged when we have a CLA signed by you.

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

@@ -6,12 +6,9 @@ import GitpodPorts from "./gitpod/ports.webp";
 import GitpodPreparing from "./gitpod/preparing.webp";
 import GitpodRunning from "./gitpod/running.webp";
 
-import GithubCodespaceEnvFile from "./github-codespaces/env.webp";
 import GithubCodespaceLoading from "./github-codespaces/loading.webp";
 import GithubCodespaceNew from "./github-codespaces/new.webp";
 import GithubCodespacePorts from "./github-codespaces/ports.webp";
-import GithubCodespaceRun from "./github-codespaces/run.webp";
-import GithubCodespaceTerminal from "./github-codespaces/terminal.webp";
 
 export const metadata = {
   title: "Formbricks Development Setup: Complete Guide to Local Environment Configuration for Dev",
@@ -38,7 +35,7 @@ This will open a fully configured workspace in your browser with all the necessa
 
 ### [Github Codespaces](#Github-codespaces)
 
-This will open a Github VSCode Interface on the cloud for you. This setup will have the Formbricks codebase and all the dependencies installed. Click the button below to configure your instance and open the project in Github Codespaces. For a detailed guide, visit the [Github Codespaces Setup Guide](#github-codespaces-guide) section below.
+This will open a Github VSCode Interface on the cloud for you. This setup will have the Formbricks codebase, all the dependencies installed & Formbricks running. Click the button below to configure your instance and open the project in Github Codespaces. For a detailed guide, visit the [Github Codespaces Setup Guide](#github-codespaces-guide) section below.
 
 [![Open in Github Codespaces](https://img.shields.io/badge/Open%20in-Github%20Codespaces-blue?logo=Github)](https://Github.com/codespaces/new?machine=standardLinux32gb&repo=500289888&ref=main&devcontainer_path=.devcontainer%2Fdevcontainer.json&location=EastUs2)
 
@@ -66,7 +63,7 @@ This will install the Formbricks codebase and all the dependencies on your local
         1. Wait for the web and demo apps to launch on Gitpod. This automatically opens the `apps/demo/.env` file. Utilize dynamic localhost URLs (e.g., `localhost:3000` for signup and `localhost:8025` for email confirmation) to configure `NEXT_PUBLIC_FORMBRICKS_ENVIRONMENT_ID`. After creating your account and finding the `ID` in the URL at `localhost:3000`, replace `YOUR_ENVIRONMENT_ID` in the `.env` file located in `app/demo`.
 
     **Web Component Initialization:**
-     - we initialize the @formbricks/web component during prebuilds. This involves:
+     - We initialize the @formbricks/web component during prebuilds. This involves:
         1. Installing build dependencies for the `@formbricks/web#go` task from turbo.json in prebuilds to save time.
         2. Starting PostgreSQL and Mailhog containers for running migrations in prebuilds.
         3. To prevent the "Init" task from running indefinitely due to prebuild rules, a cleanup `docker compose down` step i.e. `db:down` is added to `turbo.json`. This step is designed to halt the execution of containers that are currently running.
@@ -96,8 +93,8 @@ After clicking the one-click setup button, Gitpod will open a new tab or window.
 
 ### 2. Authorizing in Gitpod
 
-<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
+<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
@@ -162,7 +159,7 @@ Here are the ports and corresponding URLs for the services within your Gitpod en
 
 - **Port 1025**:
 
-  - **Service**: SMPT server
+  - **Service**: SMTP server
   - **Description**: SMTP Server for sending and receiving email messages. This server is responsible for handling email communication.
 
 - **Port 8025**:
@@ -225,44 +222,7 @@ These URLs and port numbers represent various services and endpoints within your
 
 3. Once the Codespace is loaded, you will be redirected to the VSCode editor. You can start working on your project in this environment.
 
-4. Make the changes you want to, and now, to run the app, we first need to configure the .env file. Copy the .env.example and edit the variables as mentioned in the file itself.
-
-<Image
-  src={GithubCodespaceEnvFile}
-  alt="Github Codespace Env File"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-5. Once you have configured the .env, it's now time to run the app and see the changes. Lets open the terminal first
-
-<Image
-  src={GithubCodespaceTerminal}
-  alt="Github Codespace Open Terminal"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-6. Now, run the following command to run the app
-
-<Col>
-<CodeGroup title="Run the entire Formbricks Stack">
-
-```bash
-pnpm dev
-```
-
-</CodeGroup>
-</Col>
-
-<Image
-  src={GithubCodespaceRun}
-  alt="Run on Github Codespace"
-  quality="100"
-  className="max-w-full rounded-lg sm:max-w-3xl"
-/>
-
-7. Monitor the logs in the terminal and once you see the following, you are good to go!
+4. Monitor the logs in the terminal and once you see the following, you are good to go!
 
 <Col>
 <CodeGroup title="The WebApp is running">
@@ -280,7 +240,7 @@ pnpm dev
 </CodeGroup>
 </Col>
 
-8. 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!
+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!
 
 <Image
   src={GithubCodespacePorts}
@@ -344,7 +304,7 @@ cp .env.example .env
    </CodeGroup>
 </Col>
 
-4. Generate & set some secret values mandatory for the ENCRYPTION_KEY & NEXTAUTH_SECRET in the .env file. You can use the following command to generate the random string of required length:
+4. Generate & set some secret values mandatory for the `ENCRYPTION_KEY` & `NEXTAUTH_SECRET` in the .env file. You can use the following command to generate the random string of required length:
 
 <Col>
    <CodeGroup title="Set value of ENCRYPTION_KEY">
@@ -370,8 +330,8 @@ pnpm go
 </Col>
    This starts the Formbricks main app (plus all its dependencies) as well as the following services using Docker:
 
-- a `postgres` container for hosting your database,
-- a `mailhog` container that acts as a mock SMTP server and shows received mails in a web UI (forwarded to your host's `localhost:8025`)
+- A `postgres` container for hosting your database,
+- A `mailhog` container that acts as a mock SMTP server and shows received mails in a web UI (forwarded to your host's `localhost:8025`)
 - Demo App at [http://localhost:3002](http://localhost:3002)
 - Landing Page at [http://localhost:3001](http://localhost:3001)
 
@@ -401,4 +361,4 @@ pnpm build
 
 ---
 
-Still can’t figure it out? Join our [Discord](https://discord.com/invite/3YFcABF2Ts)!
+Can’t figure it out? Join our [Discord](https://discord.com/invite/3YFcABF2Ts)!

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

@@ -1,9 +1,10 @@
 import { Libraries } from "@/components/docs/Libraries";
 import Image from "next/image";
+
 import SetupChecklist from "./env-id.webp";
-import WidgetNotConnected from "./widget-not-connected.webp";
-import WidgetConnected from "./widget-connected.webp";
 import ReactApp from "./react-in-app-survey-app-popup-form.webp";
+import WidgetConnected from "./widget-connected.webp";
+import WidgetNotConnected from "./widget-not-connected.webp";
 
 export const metadata = {
   title: "Integrate Formbricks: Comprehensive Framework Guide & Integration Tutorial",
@@ -45,8 +46,8 @@ All you need to do is copy a `<script>` tag to your HTML head, and that’s abou
 ```html {{ title: 'index.html' }}
 <!-- START Formbricks Surveys -->
 <script type="text/javascript">
-    !function(){var t=document.createElement("script");t.type="text/javascript",t.async=!0,t.src="https://unpkg.com/@formbricks/js@^1.4.0/dist/index.umd.js";var e=document.getElementsByTagName("script")[0];e.parentNode.insertBefore(t,e),setTimeout(function(){window.formbricks.init({environmentId: "<your-environment-id>", apiHost: "<api-host>"})},500)}();
-    </script>
+!function(){var t=document.createElement("script");t.type="text/javascript",t.async=!0,t.src="https://unpkg.com/@formbricks/js@^1.6.0/dist/index.umd.js";var e=document.getElementsByTagName("script")[0];e.parentNode.insertBefore(t,e),setTimeout(function(){window.formbricks.init({environmentId: "<your-environment-id>", apiHost: "<api-host>"})},500)}();
+</script>
 <!-- END Formbricks Surveys -->
 ```
 </CodeGroup>
@@ -222,9 +223,10 @@ Refer to our [Example NextJS App Directory project](https://github.com/formbrick
 
 ```tsx {{ title: 'Typescript' }}
 // other import
-import formbricks from "@formbricks/js";
-import { useEffect } from "react";
 import { useRouter } from "next/router";
+import { useEffect } from "react";
+
+import formbricks from "@formbricks/js";
 
 if (typeof window !== "undefined") {
   formbricks.init({
@@ -386,6 +388,92 @@ To this:
   className="max-w-full rounded-lg sm:max-w-3xl"
 />
 
+## Debugging Formbricks Integration
+
+Enabling Formbricks debug mode in your browser is a useful troubleshooting step for identifying and resolving complex issues. This section outlines how to activate debug mode, covers common use cases, and provides insights into specific debug log messages.
+
+### Activate Debug Mode
+
+To activate Formbricks debug mode:
+
+1. **In Your Integration Code:**
+
+   - 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:**
+
+   - Open your browser's developer tools by pressing `F12` or right-clicking and selecting "Inspect."
+   - Navigate to the "Console" tab to view Formbricks debugging information.
+
+     **How to Open Browser Console:**
+
+     - **Google Chrome:** Press `F12` or right-click, select "Inspect," and go to the "Console" tab.
+     - **Firefox:** Press `F12` or right-click, select "Inspect Element," and go to the "Console" tab.
+     - **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 functionality.
+- Identifying integration issues.
+- Troubleshooting unexpected behavior.
+
+### Debug Log Messages
+
+Specific debug log messages may provide insights into:
+
+- API calls and responses.
+- 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
+
+You can overwrite the default CSS styles for the in-app surveys by adding the following CSS to your global CSS file (eg. `globals.css`):
+
+Make sure that you do not change the CSS variable names as they are used by Formbricks to identify the CSS variables. You can change the values to your liking. We have filled in some sample values for you to change according to your desired appearance.
+
+<Col>
+<CodeGroup title="Overwrite Formbricks CSS">
+
+```css
+/* Formbricks CSS */
+--fb-brand-color: red;
+--fb-brand-text-color: white;
+--fb-border-color: green;
+--fb-border-color-highlight: rgb(13, 13, 12);
+--fb-focus-color: red;
+--fb-heading-color: yellow;
+--fb-subheading-color: green;
+--fb-info-text-color: orange;
+--fb-signature-text-color: blue;
+--fb-survey-background-color: black;
+--fb-accent-background-color: rgb(13, 13, 12);
+--fb-accent-background-color-selected: red;
+--fb-placeholder-color: white;
+--fb-shadow-color: var(--fb-brand-color);
+--fb-rating-fill: rgb(13, 13, 12);
+--fb-rating-hover: green;
+--fb-back-btn-border: blue;
+--fb-submit-btn-border: transparent;
+--fb-rating-selected: black;
+```
+
+</CodeGroup>
+</Col>
+
+We have an example of this in our [Demo project](https://github.com/formbricks/formbricks/blob/main/apps/demo/styles/globals.css.) here.
+
 **Can’t figure it out? [Join our Discord!](https://formbricks.com/discord)**
 
 ---

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

@@ -0,0 +1,73 @@
+export const metadata = {
+  title: "Using Actions in Formbricks | Fine-tuning User Moments",
+  description:
+    "Dive deep into how actions in Formbricks help products and teams to engage users at precise moments in their journey. Discover the power of actions, from coding to no-code setups, to refine user targeting and generate richer, more detailed user insights.",
+};
+
+#### In-App Surveys
+
+# Actions
+
+You want to understand what your users think and feel during specific moments in the user journey. To be able to ask at exactly the right point in time, you need actions.
+
+## How do Actions work?
+
+Actions are a little notification sent from your application to Formbricks. When a predefined action happens in your app, the Formbricks widget notices. This action can then trigger a survey to be shown to the user and is stored in the database.
+You decide which actions are sent either in your [Code](#code-actions) or by setting up a [No-Code](#no-code-actions) action within Formbricks.
+
+### Why are actions useful?
+
+Actions help you to display your surveys at the right time. Later on, you will be able to segment your users based on the actions they have triggered in the past. This way, you can create much more granular user segments, e.g. only target users that already have used a specific feature.
+
+## No-Code Actions
+
+No-Code actions can be set up within Formbricks with just a few clicks. There are three types of No-Code actions:
+
+1. **Page URL Action**
+
+The page URL action is triggered, when a user visits a specific page in your application. There are several match conditions:
+
+- `exactMatch`: The URL should exactly match the provided string.
+- `contains`: The URL should contain the specified string as a substring.
+- `startsWith`: The URL should start with the specified string.
+- `endsWith`: The URL should end with the specified string.
+- `notMatch`: The URL should not match the specified condition.
+- `notContains`: The URL should not contain the specified string as a substring.
+
+2. **innerText Action**
+
+The innerText action checks if the `innerText` of a clicked HTML element matches a specific text, e.g. the label of a button. Display a survey on any button click!
+
+3. **CSS Selector Action**
+
+The CSS Selector action checks if the provided CSS selector matches the selector of a clicked HTML element. The CSS selector can be a class, id or any other CSS selector within your website. Display a survey on any element click!
+
+## Code Actions
+
+Actions can also be set in the codebase to trigger surveys. Please add the code action first in the Formbricks web interface to be able to configure your surveys to use this action.
+
+After that you can fire an action using `formbricks.track()`
+
+<Col>
+<CodeGroup title="Track an action">
+
+```javascript
+formbricks.track("Action Name");
+```
+
+</CodeGroup>
+</Col>
+Here is an example of how to fire an action when a user clicks a button:
+<Col>
+<CodeGroup title="Track Button Click">
+
+```javascript
+const handleClick = () => {
+  formbricks.track("Button Clicked");
+};
+
+return <button onClick={handleClick}>Click Me</button>;
+```
+
+</CodeGroup>
+</Col>

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

@@ -1,18 +1,28 @@
 export const metadata = {
-  title: "User Identification in Formbricks | Enhancing Survey Feedback",
+  title: "Understanding User Attributes in Formbricks Surveys",
   description:
-    "A comprehensive guide on identifying users in Formbricks without compromising privacy. Learn how to set User ID, email, and custom attributes to optimize survey targeting, recontact users, and control survey intervals, all while respecting user anonymity.",
+    "Dive into the importance of attributes in surveys. Learn how key-value pairs can significantly improve survey targeting, enhance feedback quality, and guide data-driven decisions with Formbricks.",
 };
 
-#### Attributes
+#### In-App Surveys
 
-# Identifying Users
+# Attributes
 
-At Formbricks, we value user privacy. By default, Formbricks doesn't collect or store any personal information from your users. However, we understand that it can be helpful for you to know which user submitted the feedback and also functionality like recontacting users and controlling the waiting period between surveys requires identifying the users. That's why we provide a way for you to share existing user data from your app, so you can view it in our dashboard.
+Surveying your user base without segmentation leads to weak results and survey fatigue. Attributes help you segment your users into groups.
 
-If you would like to use the User Identification feature of Formbricks, target surveys to specific user segments and see more information about the user who responded to a survey, you can identify users by setting a User ID, email, and custom attributes. This guide will walk you through how to do that.
+## How do Attributes work?
 
-## Setting User ID
+Attributes are **key-value pairs** that you can set for each person individually.
+Attributes are sent from your application to Formbricks and are associated with the current user. We store it in our database and allow you to use it the next time you create a survey. They help show surveys to the right group of people.
+
+<Note>
+    At Formbricks, we value user privacy. By default, Formbricks doesn't collect or store any personal information from your users.
+</Note>
+
+## Identifying Users
+To use the User Identification feature of Formbricks, target surveys to specific user segments and see more information about the user who responded to a survey, you can identify users by setting a User ID, email, and custom attributes. Below is how to do that.
+
+### Setting User ID
 
 To enable the User identification feature you need to set the `userId` in the init() call of Formbricks. Only when the `userId` is set the person will be visible in the Formbricks dashboard. The `userId` can be any string and it's best to use the default identifier you use in your app (e.g. unique id from database or the email address if it's unique) but you can also anonymize these as long as they are unique for every user.
 
@@ -30,7 +40,7 @@ formbricks.init({
 </CodeGroup>
 </Col>
 
-## Enhanced Initialization with User Attributes
+### Enhanced Initialization with User Attributes
 
 In addition to setting the `userId`, Formbricks allows you to set user attributes right at the initialization. This ensures that your user data is seamlessly integrated from the start. Here's how you can include user attributes in the `init()` function:
 
@@ -52,7 +62,7 @@ formbricks.init({
 </CodeGroup>
 </Col>
 
-## Setting User Email
+### Setting User Email
 
 The `userId` is the main identifier used in Formbricks and user identification is only enabled when it is set. In addition to the userId you can also set attributes that describes the user better. The email address can be set using the setEmail function:
 
@@ -65,7 +75,8 @@ formbricks.setEmail("user@example.com");
 
 </CodeGroup>
 </Col>
-### Setting Custom User Attributes
+
+## Setting Custom User Attributes
 
 You can use the setAttribute function to set any custom attribute for the user (e.g. name, plan, etc.):
 
@@ -78,6 +89,20 @@ formbricks.setAttribute("Plan", "free");
 
 </CodeGroup>
 </Col>
+
+Generally speaking, the setAttribute function works like this:
+<Col>
+<CodeGroup title="Setting Custom Attributes">
+
+```javascript
+formbricks.setAttribute("attribute_key", "attribute_value");
+```
+
+</CodeGroup>
+</Col>
+Where `attributeName` is the name of the attribute you want to set, and `attributeValue` is the value of the attribute you want to set.
+
+
 ### Logging Out Users
 
 When a user logs out of your webpage, make sure to log them out of Formbricks as well. This will prevent new activity from being associated with an incorrect user. Use the logout function:

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

@@ -0,0 +1,86 @@
+export const metadata = {
+  title: "Identifying Users in Formbricks In-App Surveys",
+  description:
+    "Dive into the importance of user identification in surveys. Boost your survey response rates and target the right users with Formbricks.",
+};
+
+#### In-App Surveys
+
+# User Identification
+
+User Identification helps you to not only segment your users but also to see more information about the user who responded to a survey. This helps you to target surveys to specific user segments and see more information about the user who responded to a survey.
+
+### Understanding Identified vs Unidentified Users
+
+In Formbricks, understanding the distinction between identified and unidentified users is crucial for effective survey segmentation and targeted feedback collection.
+
+| Feature                                                  | Unidentified Users | Identified Users |
+| -------------------------------------------------------- | ------------------ | ---------------- |
+| Show surveys based on **trigger** actions                | ✅                 | ✅               |
+| Set **recontact details** to avoid survey fatique        | ✅                 | ✅               |
+| Target a subset of users using **attributes & segments** | ❌                 | ✅               |
+| Collect **user information** in Formbricks               | ❌                 | ✅               |
+| Track **custom attributes**                              | ❌                 | ✅               |
+| Counts towards your **monthly tacked user (MTU)** limit  | ❌                 | ✅               |
+| Recommended for **public-facing websites**               | ✅                 | ❌               |
+| Recommended for **web apps after login**                 | ❌                 | ✅               |
+
+## Unidentified Users
+
+Unidentified users are those without a specific userId set. Surveys can still be presented to these users based on trigger actions, but without the granularity of user-specific targeting.
+
+This method is recommended for public-facing websites where users are not required to log in.
+
+<Col>
+<CodeGroup title="Initialization without a user ID">
+
+```javascript
+formbricks.init({
+  environmentId: "<environment-id>",
+  apiHost: "<api-host>",
+});
+```
+
+</CodeGroup>
+</Col>
+
+## Identified Users
+
+Identified users are those for whom specific information has been set, notably the userId. This identification allows for more precise targeting of surveys and a deeper understanding of the feedback provided. When enabled, all information specified by you and all actions are sent to Formbricks.
+
+This method is recommended for applications where users are required to log in and will often return.
+
+**Setting the User ID:**
+To identify a user, set the `userId` in the Formbricks initialization call. The userId should be a unique string, such as a database ID or an email address. This is essential for the user to be visible on the Formbricks dashboard.
+
+<Col>
+<CodeGroup title="Initialization with a user ID">
+
+```javascript
+formbricks.init({
+  environmentId: "<environment-id>",
+  apiHost: "<api-host>",
+  userId: "<user_id>",
+});
+```
+
+</CodeGroup>
+</Col>
+
+**Logging Out Users:**
+When a user logs out of your application, ensure they are also logged out of Formbricks. This prevents the association of their activities with the wrong user profile.
+
+<Col>
+<CodeGroup title="Logging out User">
+
+```javascript
+formbricks.logout();
+```
+
+</CodeGroup>
+</Col>
+
+<Note>
+  To set other custom attributes for a user, view our <a href="/docs/in-app-surveys/attributes">Attributes</a>{" "}
+  documentation.
+</Note>

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

@@ -123,6 +123,7 @@ We will first create a Google Cloud Project and then enable the Google Sheets AP
     - `GOOGLE_SHEETS_CLIENT_ID` - Client ID
     - `GOOGLE_SHEETS_CLIENT_SECRET` - Client Secret
 16. Also use the **same Authorized redirect URI** in the `GOOGLE_SHEETS_REDIRECT_URL` environment variable.
+17. One last that we need to do is to **enable the Google Drive API** for the project. For that, go to the "**APIs & Services**" section and click on the "**Enable APIs and Services**" button and search for "**Google Drive API**" and enable it.
 
 ### By now, your environment variables should include the below ones as well:
 

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

@@ -0,0 +1,133 @@
+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";
+
+export const metadata = {
+  title: "Run targeted surveys on your WordPress page",
+  description:
+    "Target specific visitors with a survey on your WordPress page using Formbricks for free. Show survey on specific page or on button click.",
+};
+
+#### WordPress
+
+# Connect Formbricks with your WordPress page
+
+If you want to run a targeted survey on your WordPress website, Formbricks is the way to go! With our generous free plan and open source tech, you get everything you need to get started and keep full control over your data.
+
+## TLDR
+
+1. Install the Formbricks WordPress plugin
+2. Create a [free Formbricks account](https://app.formbricks.com/auth/signup)
+3. Find and copy the `environment id`
+4. Copy the environment id into the right field in the plugin settings
+5. Create survey on trigger “New Session” to test it
+
+## Step 1: Install the Formbricks WordPress plugin
+
+As long as the Formbricks plugin is in review, please download it from our [GitHub repository directly.](https://github.com/formbricks/wordpress)
+
+<Image
+  src={Img1}
+  alt="Run targeted website survye on any WordPress site"
+  quality="100"
+  className="max-w-full rounded-lg sm:max-w-3xl"
+/>
+
+## Step 2: Create a Formbricks Account
+
+This is super straight forward: Go to [app.formbricks.com/auth/signup](https://app.formbricks.com/auth/signup), create the account, verify your email and you’re in!
+
+When you see this screen, you’re there:
+
+<Image
+  src={Img2}
+  alt="Free HotJar survey alternative open source"
+  quality="100"
+  className="max-w-full rounded-lg sm:max-w-3xl"
+/>
+
+## Step 3: Find and copy the environmentId
+
+Go to Settings > Setup Checklist where you’ll find your environmentId:
+
+<Image
+  src={Img3}
+  alt="Run targeted surveys for free on WordPress pages"
+  quality="100"
+  className="max-w-full rounded-lg sm:max-w-3xl"
+/>
+
+## Step 4: Copy the environmentId to the WordPress Plugin Settings
+
+In your WordPress instance, go to the Formbricks Plugin settings and copy the environmentId in the correct field:
+
+<Image
+  src={Img5}
+  alt="Free and open source HotJar survey on WordPress page"
+  quality="100"
+  className="max-w-full rounded-lg sm:max-w-3xl"
+/>
+
+Then click the button at the bottom to see if the connection worked.
+
+<Note>If you don’t use our Cloud, you also have to update the API Host</Note>
+
+Great!
+
+## Step 5: Create survey on trigger “New Session”
+
+Now that all is setup, we create a survey to display an example survey. Pick any template here:
+
+<Image
+  src={Img2}
+  alt="Free HotJar survey alternative open source"
+  quality="100"
+  className="max-w-full rounded-lg sm:max-w-3xl"
+/>
+
+Keep the content for now, click on the Settings tab:
+
+<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
+
+<Image
+  src={Img6}
+  alt="Open Source survey on targeted website wordpress"
+  quality="100"
+  className="max-w-full rounded-lg sm:max-w-3xl"
+/>
+
+When you see this page, you did it!
+
+<Image
+  src={Img7}
+  alt="Run free an open source targeted survey on any page"
+  quality="100"
+  className="max-w-full rounded-lg sm:max-w-3xl"
+/>
+
+## Step 6: Reload your page to check out your survey 🤓
+
+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)

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

@@ -0,0 +1,97 @@
+import Image from "next/image";
+
+import FilledHiddenFields from "./filled-hidden-fields.webp";
+import HiddenFieldResponses from "./hidden-field-responses.webp";
+import HiddenFields from "./hidden-fields.webp";
+import InputHiddenFields from "./input-hidden-fields.webp";
+import SettingsPage from "./settings.webp";
+
+export const metadata = {
+  title: "Hidden Fields",
+  description: "Add hidden fields to your surveys to capture additional data without requiring user inputs!",
+};
+
+#### Link Surveys
+
+# Hidden Fields
+
+Hidden fields are a powerful feature in Formbricks that allows you to add data to a submission without asking the user to type it in. This feature is especially useful when you already have information about a user that you want to use in the analysis of the survey results (e.g. `payment plan` or `email`)
+
+## How to Add Hidden Fields
+
+### Enable them in the Survey Builder
+
+1. Edit the survey you want to add hidden fields to & open it's settings, make sure it's selected as a **Link Survey**.
+
+<Image
+  src={SettingsPage}
+  alt="Select the Survey Type as Link Survey"
+  quality="100"
+  className="max-w-full rounded-lg sm:max-w-3xl"
+/>
+
+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.
+
+<Image
+  src={HiddenFields}
+  alt="Enable Hidden Fields"
+  quality="100"
+  className="max-w-full rounded-lg sm:max-w-3xl"
+/>
+
+3. Now click on it to add a new hidden field ID. You can add as many hidden fields as you want.
+
+<Image
+  src={InputHiddenFields}
+  alt="Add Hidden Fields"
+  quality="100"
+  className="max-w-full rounded-lg sm:max-w-3xl"
+/>
+
+<Image
+  src={FilledHiddenFields}
+  alt="Filled Hidden Fields"
+  quality="100"
+  className="max-w-full rounded-lg sm:max-w-3xl"
+/>
+
+### Set Single Hidden Field
+
+<Col>
+<CodeGroup title="Example Screen from which the User filled it">
+
+```sh
+https://formbricks.com/clin3dxja02k8l80hpwmx4bjy?screen=pricing
+```
+
+</CodeGroup>
+</Col>
+
+### Set Multiple Hidden Fields
+
+<Col>
+<CodeGroup title="Example Screen from which the User filled it">
+
+```sh
+https://formbricks.com/clin3dxja02k8l80hpwmx4bjy?screen=landing_page&job=Founder
+```
+
+</CodeGroup>
+</Col>
+
+## View Hidden Fields in Responses
+
+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.
+
+<Image
+  src={HiddenFieldResponses}
+  alt="Hidden Field Responses"
+  quality="100"
+  className="max-w-full rounded-lg sm:max-w-3xl"
+/>
+
+## Use Cases
+
+- **Tracking Source**: You can add a hidden field to track the source of the survey. For a detailed guide on Source Tracking, check out the [Source Tracking](/docs/link-surveys/source-tracking) guide.
+- **User Metadata**: You can add hidden fields to capture user metadata such as user ID, email, or any other user-specific information.
+- **Survey Metadata**: You can add hidden fields to capture other metadata, e.g. the screen from which the survey was filled, or any other app specific information.

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

@@ -0,0 +1,88 @@
+import Image from "next/image";
+
+import HomePage from "./home-page.webp";
+import SurveyQuestions from "./survey-questions.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",
+  description:
+    "Formbricks is the easiest way to create and manage link surveys. This quickstart guide will show you how to create your first link survey in under 5 minutes.",
+};
+
+#### Getting Started
+
+# Quickstart
+
+Link Surveys make it easy for your users to give you feedback. They are a great way to get feedback from your users, without interrupting their workflow. This quickstart guide will show you how to create your first link survey in under 5 minutes.
+
+## Create a free Formbricks Cloud account
+
+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:
+
+<Image
+  src={HomePage}
+  alt="Choose a link survey template"
+  quality="100"
+  className="max-w-full rounded-lg sm:max-w-3xl "
+/>
+
+Choose one of the pre-created templates to get started. We’ll choose the **Product Market Fit** template for this quickstart guide.
+
+## Create your first survey
+
+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.
+
+<Image
+  src={SurveyQuestions}
+  alt="Survey Editor opens up in the Formbricks App"
+  quality="100"
+  className="max-w-full rounded-lg sm:max-w-3xl"
+/>
+
+Click on the **Settings** tab to edit the survey settings.
+
+## Configure your survey settings
+
+Formbricks packs a lot of useful functionality out of the box. You can:
+
+- 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!
+
+<Image
+  src={SurveyResponseOptions}
+  alt="Survey response configuration for link survey"
+  quality="100"
+  className="max-w-full rounded-lg sm:max-w-3xl"
+/>
+
+## Style your survey
+
+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.
+
+<Image
+  src={SurveySettings}
+  alt="UI & View configuration for link survey"
+  quality="100"
+  className="max-w-full rounded-lg sm:max-w-3xl"
+/>
+
+## Publish your survey
+
+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.
+
+<Image
+  src={SurveyPublished}
+  alt="Survey published successfully and received link to share with users"
+  quality="100"
+  className="max-w-full rounded-lg sm:max-w-3xl"
+/>
+
+## Share your survey
+
+Congratulations! Your survey is now published and ready to be shared with your users. You can share the survey link via email, SMS, or any other channel.

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

@@ -0,0 +1,70 @@
+import Image from "next/image";
+
+import ShareLink from "./share-link.webp";
+import ViewResponse from "./view-response.webp";
+
+export const metadata = {
+  title: "Source Tracking",
+  description: "Track the source of your users in an easy & compliant way!",
+};
+
+#### Link Surveys
+
+# Source Tracking
+
+Understand the source a survey respondent comes from when responding to your survey - all while keeping data privacy standards high!
+
+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>
+
+## Purpose
+
+Source tracking for link surveys is essential when you:
+
+- Want to analyze the origin of your survey respondents.
+- Aim to ensure compliance with tracking and data collection regulations.
+
+## Code Example
+<Col>
+<CodeGroup title="Example Source as Google">
+
+```sh
+https://formbricks.com/clin3dxja02k8l80hpwmx4bjy?source=Google
+```
+
+</CodeGroup>
+</Col>
+
+## How it Works
+
+To track the source of users in your link surveys effectively, follow these steps:
+
+1. **Generate Survey URL**: Create a Link Survey and get the sharable link. Append `?source=YourSouce` to the link to reference it with your campaigns and sources.
+
+<Col>
+<CodeGroup title="Example Source as Google">
+
+```sh
+https://formbricks.com/clin3dxja02k8l80hpwmx4bjy?source=Google
+```
+
+</CodeGroup>
+</Col>
+
+2. **Collect Data**: When users access the survey through these links, the URL parameters will capture the source information from which they were shared.
+
+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.
+
+<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/self-hosting/docker/page.mdx

@@ -10,7 +10,7 @@ export const metadata = {
 
 Quickly set up and start using Formbricks without getting into the technicalities of the build process. You'll be using an image that we've already built for you. The pre-built image is ready-to-run, and it only requires minimal configuration on your part. This approach is perfect for getting a functional instance of Formbricks up and running with minimal hassle. It's as easy as downloading the Docker image and firing up the container.
 
-This is ideal for those who are testing Formbricks or want to run it with minimal to no modifications. For this we use the [public Docker image](https://hub.docker.com/r/formbricks/formbricks) and a simple docker-compose file.
+This is ideal for those who are testing Formbricks or want to run it with minimal to no modifications. For this we use the [public Docker image](https://github.com/formbricks/formbricks/pkgs/container/formbricks) and a simple docker-compose file.
 
 ### Requirements
 
@@ -201,69 +201,10 @@ formbricks-quickstart-formbricks-1  | Listening on port 3000 url: http://<random
 You can close the logs again with `CTRL + C`.
 
 <Note>
-## Customizing the Build Time variables
+## Customizing environment variables
 
-To edit any of the variables that start with `NEXT_PUBLIC_`, you need to rebuild the Formbricks Docker Image!
+To edit any of the available environment variables, check out our [Configure](/docs/self-hosting/external-auth-providers) section!
 
 </Note>
 
-## Important Run-time Variables
-
-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                                                | `postgresql://postgres:postgres@postgres:5432/formbricks?schema=public` |
-| NEXTAUTH_SECRET             | Secret for NextAuth, used for session signing and 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`                                                 |
-| 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                                                |                                                                         |
-| PASSWORD_RESET_DISABLED     | Disables password reset functionality if set to `1`.                                    | optional                                                |                                                                         |
-| EMAIL_VERIFICATION_DISABLED | Disables email verification 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_AUTH_ENABLED         | Enables GitHub login if set to `1`.                                                     | optional                                                |                                                                         |
-| GOOGLE_AUTH_ENABLED         | Enables Google login if set to `1`.                                                     | optional                                                |                                                                         |
-| 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                                                |                                                                         |
-
-## Build-time Variables
-
-These variables must be provided at the time of the docker build and would require rebuilding the image.
-
-| Variable                                           | Description                                                     | Required | Default |
-| -------------------------------------------------- | --------------------------------------------------------------- | -------- | ------- |
-| NEXT_PUBLIC_FORMBRICKS_API_HOST                    | Host for the Formbricks API.                                    | optional |         |
-| NEXT_PUBLIC_FORMBRICKS_ENVIRONMENT_ID              | If you already have a preset environment ID of the environment. | optional |         |
-| NEXT_PUBLIC_FORMBRICKS_ONBOARDING_SURVEY_ID        | If you already have an onboarding survey ID to show new users.  | optional |         |
-| NEXT_PUBLIC_POSTHOG_API_KEY                        | API key for PostHog analytics.                                  | optional |         |
-| NEXT_PUBLIC_POSTHOG_API_HOST                       | Host for PostHog analytics.                                     | optional |         |
-| NEXT_PUBLIC_SENTRY_DSN                             | DSN for Sentry error tracking.                                  | optional |         |
-| NEXT_PUBLIC_DOCSEARCH_APP_ID                       | ID of the DocSearch application.                                | optional |         |
-| NEXT_PUBLIC_DOCSEARCH_API_KEY                      | API key of the DocSearch application.                           | optional |         |
-| NEXT_PUBLIC_DOCSEARCH_INDEX_NAME                   | Name of the DocSearch index.                                    | optional |         |
-| NEXT_PUBLIC_FORMBRICKS_COM_ENVIRONMENT_ID          | Environment ID for Formbricks (if you already have one)         | optional |         |
-| NEXT_PUBLIC_FORMBRICKS_COM_DOCS_FEEDBACK_SURVEY_ID | Survey ID for the feedback survey on the docs site.             | optional |         |
-| NEXT_PUBLIC_FORMBRICKS_COM_API_HOST                | Host for the Formbricks API.                                    | optional |         |
-
 Still facing issues? [Join our Discord!](https://formbricks.com/discord) and we'd be glad to assist you!

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

@@ -0,0 +1,26 @@
+export const metadata = {
+  title: "Enterprise License to unlock advanced functionality",
+  description:
+    "Request a self-hosting licenses to unlock advanced enterprise functionality",
+};
+
+#### Self-Hosting
+
+# Enterprise License Request (Beta)
+
+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.
+
+**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' }}>
+  <iframe
+    src="https://app.formbricks.com/s/clrf4z8zg1u3912250j7shqb5"
+    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

@@ -40,12 +40,11 @@ Integrating Google OAuth with your Formbricks instance allows users to log in us
    - Ensure to specify authorized JavaScript origins and authorized redirect URIs.
 
 <Col>
-<CodeGroup title="Configuration URLs">
-``` {{ title: 'Redirect & Origin URLs' }}
-Authorized JavaScript origins: {WEBAPP_URL}
-Authorized redirect URIs: {WEBAPP_URL}/api/auth/callback/google
-```
-</CodeGroup>
+  <CodeGroup title="Configuration URLs">
+    ``` {{ title: "Redirect & Origin URLs" }}
+    Authorized JavaScript origins: {WEBAPP_URL}
+    Authorized redirect URIs: {WEBAPP_URL}/api/auth/callback/google ```
+  </CodeGroup>
 </Col>
 
 5. **Update Environment Variables in Docker**:
@@ -58,14 +57,12 @@ Authorized redirect URIs: {WEBAPP_URL}/api/auth/callback/google
 
 ```sh {{ title: 'Shell commands' }}
 docker exec -it container_id /bin/bash
-export GOOGLE_AUTH_ENABLED=1
 export GOOGLE_CLIENT_ID=your-client-id-here
 export GOOGLE_CLIENT_SECRET=your-client-secret-here
 exit
 ```
 
 ```sh {{ title: 'env file' }}
-GOOGLE_AUTH_ENABLED=1
 GOOGLE_CLIENT_ID=your-client-id-here
 GOOGLE_CLIENT_SECRET=your-client-secret-here
 ```
@@ -78,3 +75,103 @@ GOOGLE_CLIENT_SECRET=your-client-secret-here
    - Once the environment variables have been updated, it's crucial to restart your Docker containers to apply the changes. This ensures that your Formbricks instance can utilize the new Google OAuth configuration for user authentication. Here's how you can do it:
    - 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:
+
+## 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.
+
+1. Configure your OIDC provider & get the following variables:
+   - `OIDC_CLIENT_ID`
+   - `OIDC_CLIENT_SECRET`
+   - `OIDC_ISSUER`
+   - `OIDC_SIGNING_ALGORITHM`
+
+<Note>
+Make sure the Redirect URI for your OIDC Client is set to `{WEBAPP_URL}/api/auth/callback/openid`.
+</Note>
+
+2. Update these environment variables in your `docker-compose.yml` or pass it directly to the running container.
+
+An example configuration for a FusionAuth OpenID Connect in Formbricks would look like:
+<Col>
+<CodeGroup title="Formbricks Env for FusionAuth OIDC">
+```yml {{ title: '.env' }}
+OIDC_CLIENT_ID=59cada54-56d4-4aa8-a5e7-5823bbe0e5b7
+OIDC_CLIENT_SECRET=4f4dwP0ZoOAqMW8fM9290A7uIS3E8Xg29xe1umhlB_s
+OIDC_ISSUER=http://localhost:9011
+OIDC_DISPLAY_NAME=FusionAuth
+OIDC_SIGNING_ALGORITHM=HS256
+```
+</CodeGroup>
+</Col>
+
+3. Set an environment variable `OIDC_DISPLAY_NAME` to the display name of your OIDC provider.
+
+4. Restart your Formbricks instance.
+
+5. You're all set! Users can now signup & log in using their OIDC credentials.
+
+## Important Run-time Variables
+
+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` |
+| 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
+
+These variables must be provided at the time of the docker build and would require rebuilding the image.
+
+| Variable                              | Description                                           | Required | Default |
+| ------------------------------------- | ----------------------------------------------------- | -------- | ------- |
+| NEXT_PUBLIC_FORMBRICKS_API_HOST       | Host for the Formbricks API to use inside Formbricks. | optional |         |
+| NEXT_PUBLIC_FORMBRICKS_ENVIRONMENT_ID | Formbricks environment ID for use inside Formbricks.  | optional |         |
+| NEXT_PUBLIC_POSTHOG_API_KEY           | API key to use PostHog analytics inside Formbricks.   | optional |         |
+| NEXT_PUBLIC_POSTHOG_API_HOST          | Host to use PostHog analytics inside Formbricks.      | optional |         |
+| NEXT_PUBLIC_SENTRY_DSN                | DSN for Sentry error tracking inside Formbricks.      | optional |         |
+
+Still facing issues? [Join our Discord!](https://formbricks.com/discord) and we'd be glad to assist you!

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

@@ -0,0 +1,27 @@
+export const metadata = {
+  title: "About the Formbricks Open-Source License",
+  description:
+    "The Formbricks core is available under the AGPLv3 license",
+};
+
+#### Self-Hosting
+
+# License
+
+## The AGPL Formbricks Core
+
+The Formbricks core application is licensed under the [AGPLv3 Open Source License](https://github.com/formbricks/formbricks/blob/main/LICENSE). The core application is fully functional and includes everything you need to design & run link surveys, website surveys and in-app surveys. You can use the software for free for personal and commercial use. You're also allowed to create and distribute modified versions as long as you document the changes you make incl. date. The AGPL license requires you to publish your modified version under the AGPLv3 license as well.
+
+## The Enterprise Edition
+
+Additional to the AGPL licensed Formbricks core, this repository contains code licensed under an Enterprise license. The [code](https://github.com/formbricks/formbricks/tree/main/packages/ee) and [license](https://github.com/formbricks/formbricks/blob/main/packages/ee/LICENSE) for the enterprise functionality can be found in the `/packages/ee` folder of this repository. 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/enterprise) to unlock it.
+
+## White-Labeling Formbricks and Other Licensing Needs
+
+If you have other licensing requirements such as White-Labeling please [send us an email](mailto:hola@formbricks.com).
+
+## Why charge for Enterprise Features?
+
+The Enterprise Edition and White-Label Licenses allow us to fund the development of Formbricks sustainably. It guarantees that the open-source surveying infrastructure we're building will be around for decades to come.
+
+**Having more questions?**: [Join our Discord!](https://formbricks.com/discord)

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

@@ -8,16 +8,101 @@ export const metadata = {
 
 # Migration Guide
 
-## v1.1 -> v1.2
+## v1.6
+
+Formbricks v1.6 comes with a big new features like Advanced Targeting & Segmentation of your end-users along with on-the-fly triggers for surveys and a ton of stability improvements & features. This also involves a few changes in our environment variables. This guide will help you migrate your existing Formbricks instance to v1.6 without any hassles or build errors.
+
+<Note>
+  This upgrade requires a **data migration**. Please make sure to backup your database before proceeding with
+  the upgrade. Follow the below steps thoroughly to upgrade your Formbricks instance to v1.6.
+</Note>
+
+### Steps to Migrate
+
+This guide is for users who are self-hosting Formbricks using our one-click setup. If you are using a different setup, you might adjust the commands accordingly.
+
+To run all these steps, please navigate to the `formbricks` folder where your `docker-compose.yml` file is located.
+
+1. **Backup your Database**: This is a crucial step. Please make sure to backup your database before proceeding with the upgrade. You can use the following command to backup your database:
+
+<Col>
+<CodeGroup title="Backup Postgres">
+
+```bash
+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>
+
+2. Stop the running Formbricks instance & remove the related containers:
+
+<Col>
+<CodeGroup title="Stop the containers">
+
+```bash
+docker-compose down
+```
+
+</CodeGroup>
+</Col>
+
+3. Restarting the containers will automatically pull the latest version of Formbricks:
+
+<Col>
+<CodeGroup title="Restart the containers">
+
+```bash
+docker-compose up -d
+```
+
+</CodeGroup>
+</Col>
+
+4. Now let's migrate the data to the latest schema:
+
+<Note>To find your Docker Network name for your Postgres Database, find it using `docker network ps`</Note>
+
+<Col>
+<CodeGroup title="Migrate the data">
+
+```bash
+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
+```
+
+</CodeGroup>
+</Col>
+
+The above command will migrate your data to the latest schema. This is a crucial step to migrate your existing data to the new structure. Only if the script runs successful, changes are made to the database. The script can safely run multiple times.
+
+5. That's it! Once the migration is complete, you can **now access your Formbricks instance** at the same URL as before.
+
+### In-App Surveys with @formbricks/js
+
+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
+
+| Environment Variable | Comments                                                                                                                                                        |
+| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| GITHUB_AUTH_ENABLED  | Was used to enable GitHub OAuth, but from v1.6, you can just set the `GITHUB_ID` and `GITHUB_SECRET` environment variables.                                     |
+| GOOGLE_AUTH_ENABLED  | Was used to enable Google OAuth, but from v1.6, you can just set the `GOOGLE_CLIENT_ID` and `GOOGLE_CLIENT_SECRET` environment variables.                       |
+| AZUREAD_AUTH_ENABLED | Was used to enable AzureAD OAuth, but from v1.6, you can just set the `AZUREAD_CLIENT_ID`, `AZUREAD_CLIENT_SECRET` & `AZUREAD_TENANT_ID` environment variables. |
+
+## v1.2
 
 Formbricks v1.2 ships a lot of features targeting our Link Surveys. We have also improved our security posture to be as robust as ever. However, it also comes with a few breaking changes specifically with the environment variables. This guide will help you migrate your existing Formbricks instance to v1.2 without any hassles or build errors.
 
 ### New Environment Variables
 
-| Environment Variable | Required | Recommended Generation         | Comments                                                    |
-| -------------------- | -------- | ------------------------------ | ----------------------------------------------------------- |
-| ENCRYPTION_KEY       | true     | `openssl rand -hex 32`         | Needed for 2 Factor Authentication                          |
-| SHORT_URL_BASE       | false    | `<your-short-base-url>`        | Needed if you want to enable shorter links for Link Surveys |
+| Environment Variable | Required | Recommended Generation  | Comments                                                    |
+| -------------------- | -------- | ----------------------- | ----------------------------------------------------------- |
+| ENCRYPTION_KEY       | true     | `openssl rand -hex 32`  | Needed for 2 Factor Authentication                          |
+| SHORT_URL_BASE       | false    | `<your-short-base-url>` | Needed if you want to enable shorter links for Link Surveys |
 
 ### Deprecated / Removed Environment Variables
 
@@ -25,7 +110,7 @@ Formbricks v1.2 ships a lot of features targeting our Link Surveys. We have also
 | -------------------- | ------------------------------------------------------------------------- |
 | SURVEY_BASE_URL      | The WEBAPP_URL is now used to determine the survey base url in all places |
 
-## v1.0 -> v1.1
+## v1.1
 
 Formbricks v1.1 includes a lot of new features and improvements. However, it also comes with a few breaking changes specifically with the environment variables. This guide will help you migrate your existing Formbricks instance to v1.1 without losing any data.
 
@@ -113,6 +198,9 @@ x-environment: &environment
     # Uncomment the below and set it to 1 to disable Signups
     # SIGNUP_DISABLED:
 
+    # Uncomment the below and set it to 1 to disable loging in with email
+    # EMAIL_AUTH_DISABLED:
+
     # Uncomment the below and set it to 1 to disable Invites
     # INVITE_DISABLED:
 
@@ -136,6 +224,7 @@ x-environment: &environment
     # GOOGLE_CLIENT_SECRET:
 
 ```
+
 </CodeGroup>
 </Col>
 Did we miss something? Are you still facing issues migrating your app? [Join our Discord!](https://formbricks.com/discord) We'd be happy to help!

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

@@ -10,8 +10,16 @@ export const metadata = {
 
 If you want to quickly set up a production instance of Formbricks on a server running Ubuntu, we've got you covered! This method utilizes a convenient shell script that takes care of everything, including Docker, Postgres DB, and SSL certificate configuration. The shell script will automatically install all the required dependencies and configure your server, making the process a breeze.
 
+<Note>
+   This setup installs **Traefik** to work as a **reverse proxy**. This configuration is crucial for directing incoming traffic to the correct container, allowing Formbricks to be accessible from the internet securely.
+   Traefik is chosen for its simplicity and automatic SSL management with Let's Encrypt.
+</Note>
+
+
 This is the quickest way to get Formbricks up and running on an Ubuntu server. The shell script will automatically install all the required dependencies and configure your server, making the process a breeze.
 
+If you want to run Formbricks on a different OS or have more control over the installation process, you can follow the [advanced installation guide](/docs/self-hosting/docker) with Docker.
+
 ### Requirements
 
 Before you proceed, make sure you have the following:
@@ -29,7 +37,7 @@ Copy and paste the following command into your terminal:
 <CodeGroup title="Single Command to deploy Formbricks">
 
 ```bash
-curl -fsSL https://raw.githubusercontent.com/formbricks/formbricks/main/docker/production.sh -o formbricks.sh && chmod +x formbricks.sh && ./formbricks.sh install
+curl -fsSL https://raw.githubusercontent.com/formbricks/formbricks/main/docker/formbricks.sh -o formbricks.sh && chmod +x formbricks.sh && ./formbricks.sh install
 ```
 
 </CodeGroup>
@@ -219,18 +227,16 @@ The script will automatically stop all the Formbricks related containers, remove
 
 ## Debugging
 
-If you encounter any issues, you can check the logs of the container with:
+If you encounter any issues, you can check the logs of the containers with:
 <Col>
 <CodeGroup title="Check logs of the container">
 
 ```bash
-cd formbricks && docker compose logs -f
+./formbricks.sh logs
 ```
 
 </CodeGroup>
 </Col>
-You can close the logs again with `CTRL + C`.
-
 
 ## Troubleshooting
 
@@ -244,4 +250,4 @@ If you encounter any issues, consider the following steps:
 
 - **Check Formbricks Logs**: Run `cd formbricks && docker compose logs` to check the logs of the Formbricks stack.
 
-**Still can’t figure it out?**: [Join our Discord!](https://formbricks.com/discord)
+**Can’t figure it out?**: [Join our Discord!](https://formbricks.com/discord)

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

@@ -5,7 +5,7 @@ import { useRouter } from "next/router";
 
 import { Button } from "@formbricks/ui/Button";
 
-import { FooterLogo } from "../../components/shared/Logo";
+import { FooterLogo } from "../shared/Logo";
 
 export default function HeaderLight() {
   const plausible = usePlausible();

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

@@ -1,5 +1,5 @@
-import Footer from "../../components/shared/Footer";
-import MetaInformation from "../../components/shared/MetaInformation";
+import Footer from "../shared/Footer";
+import MetaInformation from "../shared/MetaInformation";
 import HeaderLight from "./HeaderLight";
 
 interface LayoutProps {

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

@@ -23,7 +23,7 @@ const variantStyles = {
     "rounded-full bg-slate-900 py-1 px-3 text-white hover:bg-slate-700 dark:bg-teal-500 dark:text-white dark:hover:bg-teal-400",
   outline:
     "rounded-full py-1 px-3 text-slate-700 ring-1 ring-inset ring-slate-900/10 hover:bg-slate-900/2.5 hover:text-slate-900 dark:text-slate-400 dark:ring-white/10 dark:hover:bg-white/5 dark:hover:text-white",
-  text: "text-teal-500 hover:text-teal-700 dark:text-teal-400 dark:hover:text-teal-600",
+  text: "text-teal-500 hover:text-teal-700 dark:text-teal-400 dark:hover:text-teal-300",
 };
 
 type ButtonProps = {

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

@@ -42,7 +42,7 @@ export function Libraries() {
           <a
             key={library.name}
             href={library.href}
-            className="flex flex-row-reverse gap-6 rounded-2xl p-6 transition-all duration-100 ease-in-out hover:cursor-pointer hover:bg-slate-100/50">
+            className="flex flex-row-reverse gap-6 rounded-2xl p-6 transition-all duration-100 ease-in-out hover:cursor-pointer hover:bg-slate-100/50 dark:hover:bg-slate-800/50">
             <div className="flex-auto">
               <h3 className="text-sm font-semibold text-slate-900 dark:text-white">{library.name}</h3>
               <p className="mt-1 text-sm text-slate-600 dark:text-slate-400">{library.description}</p>

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

@@ -189,35 +189,25 @@ export const navigation: Array<NavGroup> = [
     ],
   },
   {
-    title: "Getting Started",
+    title: "In-App Surveys",
     links: [
-      { title: "Quickstart: In app", href: "/docs/getting-started/quickstart-in-app-survey" },
+      { title: "Quickstart", href: "/docs/getting-started/quickstart-in-app-survey" },
       { title: "Framework Guides", href: "/docs/getting-started/framework-guides" },
       { title: "Troubleshooting", href: "/docs/getting-started/troubleshooting" },
-    ],
-  },
-  {
-    title: "Attributes",
-    links: [
-      { title: "Why Attributes?", href: "/docs/attributes/why" },
-      { title: "Custom Attributes", href: "/docs/attributes/custom-attributes" },
-      { title: "Identify users", href: "/docs/attributes/identify-users" },
-    ],
-  },
-  {
-    title: "Actions",
-    links: [
-      { title: "Why Actions?", href: "/docs/actions/why" },
-      { title: "No-Code Actions", href: "/docs/actions/no-code" },
-      { title: "Code Actions", href: "/docs/actions/code" },
+      { 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: "Link Surveys",
     links: [
+      { title: "Quickstart", href: "/docs/link-surveys/quickstart" },
       { title: "Data Prefilling", href: "/docs/link-surveys/data-prefilling" },
       { title: "Identify Users", href: "/docs/link-surveys/user-identification" },
       { 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" },
     ],
   },
   {
@@ -230,6 +220,7 @@ export const navigation: Array<NavGroup> = [
       { title: "Feature Chaser", href: "/docs/best-practices/feature-chaser" },
       { title: "Feedback Box", href: "/docs/best-practices/feedback-box" },
       { title: "Docs Feedback", href: "/docs/best-practices/docs-feedback" },
+      { title: "Improve Email Content", href: "/docs/best-practices/improve-email-content" },
     ],
   },
   {
@@ -240,6 +231,7 @@ 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: "Wordpress", href: "/docs/integrations/wordpress" },
       { title: "Zapier", href: "/docs/integrations/zapier" },
     ],
   },
@@ -251,6 +243,8 @@ export const navigation: Array<NavGroup> = [
       { title: "Advanced Setup", href: "/docs/self-hosting/docker" },
       { title: "Configure", href: "/docs/self-hosting/external-auth-providers" },
       { title: "Migration Guide", href: "/docs/self-hosting/migration-guide" },
+      { title: "License", href: "/docs/self-hosting/license" },
+      { title: "Enterprise License", href: "/docs/self-hosting/enterprise" },
     ],
   },
   {
@@ -283,6 +277,7 @@ export const navigation: Array<NavGroup> = [
       { title: "Attribute Classes", href: "/docs/api/management/attribute-classes" },
       { title: "Me", href: "/docs/api/management/me" },
       { title: "People", href: "/docs/api/management/people" },
+      { title: "Responses", href: "/docs/api/management/responses" },
       { title: "Surveys", href: "/docs/api/management/surveys" },
       { title: "Webhooks", href: "/docs/api/management/webhooks" },
     ],

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

@@ -1,11 +1,10 @@
-/* import { cleanHtml } from "../../lib/cleanHtml"; */
-import { cleanHtml } from "@formbricks/lib/cleanHtml";
+import * as DOMPurify from "dompurify";
 
 export default function HtmlBody({ htmlString, questionId }: { htmlString: string; questionId: string }) {
   return (
     <label
       htmlFor={questionId}
       className="fb-block fb-font-normal fb-leading-6 text-sm text-slate-500 dark:text-slate-300"
-      dangerouslySetInnerHTML={{ __html: cleanHtml(htmlString) }}></label>
+      dangerouslySetInnerHTML={{ __html: DOMPurify.sanitize(htmlString) }}></label>
   );
 }

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

@@ -50,7 +50,7 @@ export default function NPSQuestion({ question, onSubmit, lastQuestion, brandCol
                   selectedChoice === number
                     ? "z-10  bg-slate-50  dark:bg-slate-500"
                     : "dark:bg-slate-700 dark:hover:bg-slate-500",
-                  "relative h-10 flex-1 cursor-pointer border bg-white text-center text-sm leading-10 text-slate-900 first:rounded-l-md last:rounded-r-md  hover:bg-gray-100 focus:outline-none dark:border-slate-600  dark:text-white "
+                  "relative h-10 flex-1 cursor-pointer border bg-white text-center text-sm leading-10 text-slate-900 first:rounded-l-md last:rounded-r-md  hover:bg-slate-100 focus:outline-none dark:border-slate-600  dark:text-white "
                 )}>
                 <input
                   type="radio"

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

@@ -56,7 +56,7 @@ export default function RatingQuestion({
                 className={cn(
                   selectedChoice === number
                     ? "z-10 border-slate-400 bg-slate-50"
-                    : "bg-white hover:bg-gray-100 dark:bg-slate-700 dark:hover:bg-slate-500",
+                    : "bg-white hover:bg-slate-100 dark:bg-slate-700 dark:hover:bg-slate-500",
                   "relative h-10 flex-1 cursor-pointer border border-slate-100 text-center text-sm leading-10 text-slate-800 first:rounded-l-md last:rounded-r-md  focus:outline-none dark:border-slate-500 dark:text-slate-200   "
                 )}>
                 <input

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

@@ -53,12 +53,11 @@ export default function TemplateList({ onTemplateClick, activeTemplate }: Templa
         {templates
           .filter((template) => selectedFilter === ALL_CATEGORY_NAME || template.category === selectedFilter)
           .map((template: TTemplate) => (
-            <button
-              type="button"
+            <div
+              key={template.name}
               onClick={() => {
                 onTemplateClick(template); // Pass the 'template' object instead of 'activeTemplate'
               }}
-              key={template.name}
               className={cn(
                 activeTemplate?.name === template.name && "ring-brand ring-2",
                 "duration-120  group  relative rounded-lg bg-white p-6 shadow transition-all duration-150 hover:scale-105 dark:bg-slate-700"
@@ -71,7 +70,7 @@ export default function TemplateList({ onTemplateClick, activeTemplate }: Templa
                 {template.name}
               </h3>
               <p className="text-left text-xs text-slate-600 dark:text-slate-400">{template.description}</p>
-            </button>
+            </div>
           ))}
       </div>
     </main>

apps/formbricks-com/components/dummyUI/templates.ts

@@ -14,6 +14,7 @@ import {
   DashboardIcon,
   DogChaserIcon,
   DoorIcon,
+  EmailIcon,
   FeedbackIcon,
   GaugeSpeedFastIcon,
   HeartCommentIcon,
@@ -1224,6 +1225,61 @@ export const templates: TTemplate[] = [
       },
     },
   },
+  {
+    name: "Improve Newsletter Content",
+    icon: EmailIcon,
+    category: "Growth",
+    description: "Find out how your subscribers like your newsletter content.",
+    objectives: ["increase_conversion", "sharpen_marketing_messaging"],
+    preset: {
+      name: "Improve Newsletter Content",
+      questions: [
+        {
+          id: createId(),
+          type: TSurveyQuestionType.Rating,
+          logic: [
+            { value: "5", condition: "equals", destination: "l2q1chqssong8n0xwaagyl8g" },
+            { value: "5", condition: "lessThan", destination: "k3s6gm5ivkc5crpycdbpzkpa" },
+          ],
+          range: 5,
+          scale: "smiley",
+          headline: "How would you rate this weeks newsletter?",
+          required: true,
+          subheader: "",
+          lowerLabel: "Meh",
+          upperLabel: "Great",
+        },
+        {
+          id: "k3s6gm5ivkc5crpycdbpzkpa",
+          type: TSurveyQuestionType.OpenText,
+          logic: [
+            { condition: "submitted", destination: "end" },
+            { condition: "skipped", destination: "end" },
+          ],
+          headline: "What would have made this weeks newsletter more helpful?",
+          required: false,
+          placeholder: "Type your answer here...",
+          inputType: "text",
+        },
+        {
+          id: "l2q1chqssong8n0xwaagyl8g",
+          html: '<p class="fb-editor-paragraph" dir="ltr"><span>Who thinks like you? You\'d do us a huge favor if you\'d share this weeks episode with your brain friend!</span></p>',
+          type: TSurveyQuestionType.CTA,
+          headline: "Thanks! ❤️ Spread the love with ONE friend.",
+          required: false,
+          buttonUrl: "https://formbricks.com",
+          buttonLabel: "Happy to help!",
+          buttonExternal: true,
+          dismissButtonLabel: "Find your own friends",
+        },
+      ],
+      welcomeCard: welcomeCardDefault,
+      thankYouCard: thankYouCardDefault,
+      hiddenFields: {
+        enabled: false,
+      },
+    },
+  },
 ];
 
 export const findTemplateByName = (name: string): TTemplate | undefined => {

apps/formbricks-com/components/home/Hero.tsx

@@ -5,6 +5,8 @@ import CrowdLogoLight from "@/images/clients/crowd-logo-light.svg";
 import FlixbusLogo from "@/images/clients/flixbus-white.svg";
 import NILogoDark from "@/images/clients/niLogoDark.svg";
 import NILogoLight from "@/images/clients/niLogoWhite.svg";
+import OptimoleLogo from "@/images/clients/optimole-logo.svg";
+import ThemeisleLogo from "@/images/clients/themeisle-logo.webp";
 import AnimationFallback from "@/public/animations/opensource-xm-platform-formbricks-fallback.png";
 import { ShieldCheckIcon, StarIcon } from "@heroicons/react/24/outline";
 import { usePlausible } from "next-plausible";
@@ -45,48 +47,42 @@ export const Hero: React.FC = ({}) => {
           </span>
         </p>
 
-        <div className="mx-auto mt-5 max-w-2xl items-center px-4 sm:flex sm:justify-center md:mt-6 md:space-x-8 md:px-0">
-          <div className="grid grid-cols-4 items-center gap-6 pt-2 md:gap-8">
+        <div className="mx-auto mt-5 max-w-3xl items-center px-4 sm:flex sm:justify-center md:mt-6 md:space-x-8 md:px-0">
+          <div className="grid grid-cols-6 items-center gap-6 pt-2 md:gap-8">
             <Image
               src={FlixbusLogo}
               alt="Flixbus Flix Flixtrain Logo"
-              className="rounded-lg pb-1 hover:opacity-100 md:opacity-50"
+              className="rounded-lg pb-1 "
               width={200}
             />
-            <Image
-              src={CalLogoLight}
-              alt="Cal Logo"
-              className="block rounded-lg hover:opacity-100 md:opacity-50 dark:hidden"
-              width={170}
-            />
-            <Image
-              src={CalLogoDark}
-              alt="Cal Logo"
-              className="hidden rounded-lg hover:opacity-100 md:opacity-50 dark:block"
-              width={170}
-            />
+            <Image src={CalLogoLight} alt="Cal Logo" className="block rounded-lg  dark:hidden" width={170} />
+            <Image src={CalLogoDark} alt="Cal Logo" className="hidden rounded-lg  dark:block" width={170} />
+            <Image src={ThemeisleLogo} alt="Neverinstall Logo" className="pb-1" width={200} />
+
             <Image
               src={CrowdLogoLight}
               alt="Crowd.dev Logo"
-              className="block rounded-lg pb-1 hover:opacity-100 md:opacity-50 dark:hidden"
+              className="block rounded-lg pb-1  dark:hidden"
               width={200}
             />
             <Image
               src={CrowdLogoDark}
               alt="Crowd.dev Logo"
-              className="hidden rounded-lg pb-1 hover:opacity-100 md:opacity-50 dark:block"
+              className="hidden rounded-lg pb-1  dark:block"
               width={200}
             />
+            <Image src={OptimoleLogo} alt="Neverinstall Logo" className="pb-1" width={200} />
+            <Image src={NILogoDark} alt="Neverinstall Logo" className="block pb-1  dark:hidden" width={200} />
             <Image
-              src={NILogoDark}
+              src={NILogoLight}
               alt="Neverinstall Logo"
-              className="block pb-1 hover:opacity-100 md:opacity-50 dark:hidden"
+              className="hidden  pb-1  dark:block"
               width={200}
             />
             <Image
               src={NILogoLight}
               alt="Neverinstall Logo"
-              className="hidden  pb-1 hover:opacity-100 md:opacity-50 dark:block"
+              className="hidden  pb-1  dark:block"
               width={200}
             />
           </div>

apps/formbricks-com/components/home/SetupTabs.tsx

@@ -1,3 +1,4 @@
+import jsPackageJson from "@/../../packages/js/package.json";
 import clsx from "clsx";
 import { useState } from "react";
 import { IoLogoHtml5, IoLogoNpm } from "react-icons/io5";
@@ -45,7 +46,7 @@ export const SetupInstructions: React.FC = ({}) => {
   return (
     <div>
       <TabBar tabs={tabs} activeId={activeTab} setActiveId={setActiveTab} />
-      <div className="h-80 max-w-lg px-4 sm:max-w-lg md:max-w-lg">
+      <div className="h-84 max-w-lg px-4 sm:max-w-lg md:max-w-lg">
         {activeTab === "npm" ? (
           <>
             <CodeBlock>npm install @formbricks/js</CodeBlock>
@@ -61,7 +62,19 @@ if (typeof window !== "undefined") {
           </>
         ) : activeTab === "html" ? (
           <CodeBlock>{`<script type="text/javascript">
-!function(){var t=document.createElement("script");t.type="text/javascript",t.async=!0,t.src="https://unpkg.com/@formbricks/js@^1.4.0/dist/index.umd.js";var e=document.getElementsByTagName("script")[0];e.parentNode.insertBefore(t,e),setTimeout(function(){window.formbricks.init("claDadXk29dak92dK9","https://app.formbricks.com")},500)}();
+
+    !function(){
+    var jsPackageJson = require('@/package.json'); // Make sure the path is correct
+    var t = document.createElement("script");
+    t.type = "text/javascript";
+    t.async = true;
+    t.src = "https://unpkg.com/@formbricks/js@^${jsPackageJson.version}/dist/index.umd.js";
+    var e = document.getElementsByTagName("script")[0];
+    e.parentNode.insertBefore(t, e);
+    setTimeout(function(){
+        window.formbricks.init("claDadXk29dak92dK9","https://app.formbricks.com")
+    }, 500);
+}();
 </script>`}</CodeBlock>
         ) : null}
       </div>

apps/formbricks-com/components/home/Steps.tsx

@@ -47,12 +47,7 @@ export const Steps: React.FC = () => {
           <div className="grid md:grid-cols-2 md:items-center md:gap-16">
             <div className="order-last w-full rounded-lg bg-slate-100 p-4 sm:py-8 md:order-first dark:bg-slate-800">
               <div className="flex h-40 items-center justify-center">
-                <Button
-                  variant="primary"
-                  className=""
-                  onClick={() => {
-                    setAddEventModalOpen(true);
-                  }}>
+                <Button variant="primary">
                   <CursorArrowRaysIcon className="mr-2 h-5 w-5 text-white" />
                   Add Action
                 </Button>

apps/formbricks-com/components/shared/AuthorBox.tsx

@@ -1,5 +1,6 @@
 import AuthorJohannes from "@/images/blog/johannes-co-founder-formbricks-small.jpg";
-import AuthorOla from "@/images/blog/ola-content-writer.png";
+import AuthorOla from "@/images/blog/ola-content-writer.jpg";
+import AuthorShubham from "@/images/blog/shubham-engineer.png";
 import Image from "next/image";
 
 interface AuthorBoxProps {
@@ -10,12 +11,18 @@ interface AuthorBoxProps {
   author: string;
 }
 
+const authorImages = {
+  Johannes: AuthorJohannes,
+  Ola: AuthorOla,
+  Shubham: AuthorShubham,
+};
+
 export default function AuthorBox({ name, title, date, duration, author }: AuthorBoxProps) {
   return (
     <div className="mb-8 flex items-center space-x-4 rounded-lg border border-slate-200 bg-slate-100 px-6 py-3 dark:border-slate-700 dark:bg-slate-800">
       <Image
         className="m-0 rounded-full"
-        src={author === "Johannes" ? AuthorJohannes : AuthorOla}
+        src={authorImages[author]}
         alt={name}
         width={45}
         height={45}

apps/formbricks-com/components/shared/BestPracticeNavigation.tsx

@@ -79,6 +79,15 @@ export default function BestPracticeNavigation() {
       description: "Give users the chance to share feedback in a single click.",
       category: "Boost Retention",
     },
+
+    {
+      name: "Improve Newsletter Content",
+      href: "/improve-newsletter-content",
+      status: true,
+      icon: FeedbackIcon,
+      description: "Improve your newsletter content by showing this survey to your readers.",
+      category: "Boost Retention",
+    },
   ];
 
   return (

apps/formbricks-com/components/shared/CodeBlock.tsx

@@ -13,7 +13,7 @@ const styles: Record<string, CSSProperties> = {
     marginTop: "1rem",
     borderRadius: "0.375rem",
     fontSize: "0.875rem",
-    fontWeight: "lighter",
+    fontWeight: "normal",
     color: "#e5e7eb",
   },
   pre: {
@@ -21,7 +21,7 @@ const styles: Record<string, CSSProperties> = {
   },
   code: {
     textShadow: "none",
-    color: "#fbbf24",
+    color: "#333333",
   },
 };
 

apps/formbricks-com/components/shared/LayoutMdx.tsx

@@ -60,7 +60,7 @@ export default function LayoutMdx({ meta, children }: Props) {
               )}
             </header>
           )}
-          <Prose className="prose-h2:text-2xl prose-li:text-base prose-h2:mt-4 prose-p:text-base  prose-p:mb-4 prose-h3:text-xl prose-a:text-slate-900 prose-a:hover:text-slate-900 prose-a:text-decoration-brand prose-a:not-italic ">
+          <Prose className="prose-h2:text-2xl prose-li:text-base prose-h2:mt-6 prose-p:text-base  prose-p:mb-4 prose-h3:text-xl prose-a:text-slate-900 prose-a:hover:text-slate-900 prose-a:text-decoration-brand prose-a:not-italic prose-ul:pl-12">
             {children}
           </Prose>
         </article>

apps/formbricks-com/components/shared/MetaInformation.tsx

@@ -1,4 +1,5 @@
 import Head from "next/head";
+import { useRouter } from "next/router";
 
 interface Props {
   title: string;
@@ -19,8 +20,10 @@ export default function MetaInformation({
   section,
   tags,
 }: Props) {
+  const router = useRouter();
   const pageTitle = `${title}`;
   const BASE_URL = `https://${process.env.VERCEL_URL}`;
+  const canonicalLink = `${BASE_URL}${router.asPath}`;
   return (
     <Head>
       <title>{pageTitle}</title>
@@ -30,7 +33,7 @@ export default function MetaInformation({
       <meta name="image" content={`https://${BASE_URL}/favicon.ico`} />
       <meta property="og:image" content={`https://${BASE_URL}/social-image.png`} />
       <link rel="icon" type="image/x-icon" href={`https://${BASE_URL}/favicon.ico`} />
-      <link rel="canonical" href="https://formbricks.com/" />
+      <link rel="canonical" href={canonicalLink} />
       <meta name="msapplication-TileColor" content="#00C4B8" />
       <meta name="msapplication-TileImage" content={`https://${BASE_URL}/favicon.ico`} />
       <meta property="og:image:alt" content="Open Source Experience Management, Privacy-first" />