diff --git a/apps/docs/app/global/custom-start-end-conditions/page.mdx b/apps/docs/app/global/custom-start-end-conditions/page.mdx deleted file mode 100644 index 3aa2d1d1d0..0000000000 --- a/apps/docs/app/global/custom-start-end-conditions/page.mdx +++ /dev/null @@ -1,68 +0,0 @@ -import { MdxImage } from "@/components/MdxImage"; - -import StepOne from "./images/StepOne.webp"; -import StepThree from "./images/StepThree.webp"; -import StepTwo from "./images/StepTwo.webp"; - -export const metadata = { - title: "Custom Start & End Conditions for Surveys", - description: - "Optimize your survey management with custom Start & End Conditions in Formbricks. This feature allows you to control exactly when your survey is available for responses and when it should close, making it ideal for time-sensitive or number-of-response-limited surveys.", -}; - -# Custom Start & End Conditions - -Optimize your survey management with custom Start & End Conditions in Formbricks. This feature allows you to control exactly when your survey is available for responses and when it should close, making it ideal for time-sensitive or number-of-response-limited surveys. - -Configure your surveys to open and close based on specific criteria. Here’s how to set up these conditions: - -### **Opening a Survey** - -**1. Schedule a Start Date:** - -- **How to Set**: Open the Survey Editor, switch to the Settings tab. Scroll down to Response Options, Toggle the “Release Survey on Date”. - - - -- **Details**: Choose the date and time when the survey should become available to respondents. All times follow UTC timezone. -- **Use Case**: This is useful for launching surveys in alignment with events, product releases, or specific marketing campaigns. - -### **Closing a Survey** - -**1. Limit by Number of Responses:** - -- **How to Set**: Open the Survey Editor, switch to the Settings tab. Scroll down to Response Options, Toggle the “Close survey on response limit”. - {" "} - -- **Details**: Set a specific number of responses after which the survey automatically closes. -- **Use Case**: Perfect for limited offers, exclusive surveys, or when you need a precise sample size for statistical significance. - -**2. Schedule an End Date:** - -- **How to Set**: Open the Survey Editor, switch to the Settings tab. Scroll down to Response Options, Toggle the “Close survey on date”. - - -- **Details**: Define a specific date and time for the survey to close. This also follows UTC timezone. - **Use -Case**: Essential for surveys linked to time-bound events or studies where data collection needs to end at a specific -point. - -### **Summary** - -Setting up Custom Start & End Conditions in Formbricks allows you to control the availability and duration of your surveys with precision. Whether you are conducting academic research, market analysis, or gathering event feedback, these settings help ensure that your data collection aligns perfectly with your objectives. - ---- diff --git a/apps/docs/app/global/custom-start-end-conditions/images/StepOne.webp b/apps/docs/app/global/limit-submissions/images/StepOne.webp similarity index 100% rename from apps/docs/app/global/custom-start-end-conditions/images/StepOne.webp rename to apps/docs/app/global/limit-submissions/images/StepOne.webp diff --git a/apps/docs/app/global/custom-start-end-conditions/images/StepThree.webp b/apps/docs/app/global/limit-submissions/images/StepThree.webp similarity index 100% rename from apps/docs/app/global/custom-start-end-conditions/images/StepThree.webp rename to apps/docs/app/global/limit-submissions/images/StepThree.webp diff --git a/apps/docs/app/global/custom-start-end-conditions/images/StepTwo.webp b/apps/docs/app/global/limit-submissions/images/StepTwo.webp similarity index 100% rename from apps/docs/app/global/custom-start-end-conditions/images/StepTwo.webp rename to apps/docs/app/global/limit-submissions/images/StepTwo.webp diff --git a/apps/docs/app/global/limit-submissions/page.mdx b/apps/docs/app/global/limit-submissions/page.mdx new file mode 100644 index 0000000000..1c2e698a78 --- /dev/null +++ b/apps/docs/app/global/limit-submissions/page.mdx @@ -0,0 +1,28 @@ +import { MdxImage } from "@/components/MdxImage"; + +import StepOne from "./images/StepOne.webp"; +import StepThree from "./images/StepThree.webp"; +import StepTwo from "./images/StepTwo.webp"; + +export const metadata = { + title: "Set a Maximum Number of Submissions for Surveys", + description: + "Limit the number of responses your survey can receive.", +}; + +# Limit by Number of Submissions + +Automatically close your survey after a specific number of responses with Formbricks. This feature is perfect for limited offers, exclusive surveys, or when you need a precise sample size for statistical significance. + +- **How to**: Open the Survey Editor, switch to the Settings tab. Scroll down to Response Options, Toggle the “Close survey on response limit”. + {" "} + +- **Details**: Set a specific number of responses after which the survey automatically closes. +- **Use Case**: Perfect for limited offers, exclusive surveys, or when you need a precise sample size for statistical significance. + +--- diff --git a/apps/docs/app/global/schedule-start-end-dates/images/StepOne.webp b/apps/docs/app/global/schedule-start-end-dates/images/StepOne.webp new file mode 100644 index 0000000000..1ceaa74231 Binary files /dev/null and b/apps/docs/app/global/schedule-start-end-dates/images/StepOne.webp differ diff --git a/apps/docs/app/global/schedule-start-end-dates/images/StepThree.webp b/apps/docs/app/global/schedule-start-end-dates/images/StepThree.webp new file mode 100644 index 0000000000..33f01ed624 Binary files /dev/null and b/apps/docs/app/global/schedule-start-end-dates/images/StepThree.webp differ diff --git a/apps/docs/app/global/schedule-start-end-dates/images/StepTwo.webp b/apps/docs/app/global/schedule-start-end-dates/images/StepTwo.webp new file mode 100644 index 0000000000..4dcbe47395 Binary files /dev/null and b/apps/docs/app/global/schedule-start-end-dates/images/StepTwo.webp differ diff --git a/apps/docs/app/global/schedule-start-end-dates/page.mdx b/apps/docs/app/global/schedule-start-end-dates/page.mdx new file mode 100644 index 0000000000..cc2663450d --- /dev/null +++ b/apps/docs/app/global/schedule-start-end-dates/page.mdx @@ -0,0 +1,51 @@ +import { MdxImage } from "@/components/MdxImage"; + +import StepOne from "./images/StepOne.webp"; +import StepThree from "./images/StepThree.webp"; +import StepTwo from "./images/StepTwo.webp"; + +export const metadata = { + title: "Schedule Start & End Dates for Surveys", + description: + "Automatically release and close surveys based on specific dates.", +}; + +# Schedule Start & End Dates + +Optimize your survey management with custom Start & End Conditions in Formbricks. This feature allows you to control exactly when your survey is available for responses and when it should close, making it ideal for time-sensitive or number-of-response-limited surveys. + +Configure your surveys to open and close based on specific criteria. Here’s how to set up these conditions: + +## **Schedule a Survey Release** + +- **How to**: Open the Survey Editor, switch to the Settings tab. Scroll down to Response Options, Toggle the “Release Survey on Date”. + + + +- **Details**: Choose the date and time when the survey should become available to respondents. All times follow UTC timezone. +- **Use Case**: This is useful for launching surveys in alignment with events, product releases, or specific marketing campaigns. + +## **Automatically Closing a Survey** + +- **How to**: Open the Survey Editor, switch to the Settings tab. Scroll down to Response Options, Toggle the “Close survey on date”. + + +- **Details**: Define a specific date and time for the survey to close. This also follows UTC timezone. - **Use +Case**: Essential for surveys linked to time-bound events or studies where data collection needs to end at a specific +point. + +### **Summary** + +Setting up Start & End Dates in Formbricks allows you to control the availability and duration of your surveys with precision. Whether you are conducting academic research, market analysis, or gathering event feedback, these settings help ensure that your data collection aligns perfectly with your objectives. + +--- diff --git a/apps/docs/components/Navigation.tsx b/apps/docs/components/Navigation.tsx index fc0059b858..6152a8f3fe 100644 --- a/apps/docs/components/Navigation.tsx +++ b/apps/docs/components/Navigation.tsx @@ -171,6 +171,13 @@ const NavigationGroup = ({ const isParentOpen = (title: string) => openGroups.includes(title); + const sortedLinks = group.links.map((link) => { + if (link.children) { + link.children.sort((a, b) => a.title.localeCompare(b.title)); + } + return link; + }); + return (
  • @@ -185,7 +192,7 @@ const NavigationGroup = ({ {isActiveGroup && }
      - {group.links.map((link) => ( + {sortedLinks.map((link) => ( {link.href ? ( = [ { title: "User Metadata", href: "/global/metadata" }, // global { title: "Custom Styling", href: "/global/overwrite-styling" }, // global { title: "Conditional Logic", href: "/global/conditional-logic" }, // global - { title: "Custom Start & End Conditions", href: "/global/custom-start-end-conditions" }, // global + { title: "Start & End Dates", href: "/global/custom-start-end-conditions" }, // global + { title: "Limit submissions", href: "/global/limit-submissions" }, // global { title: "Recall Functionality", href: "/global/recall" }, // global { title: "Partial Submissions", href: "/global/partial-submissions" }, // global ], @@ -63,7 +64,8 @@ export const navigation: Array = [ { title: "User Metadata", href: "/global/metadata" }, // global { title: "Custom Styling", href: "/global/overwrite-styling" }, // global { title: "Conditional Logic", href: "/global/conditional-logic" }, // global - { title: "Custom Start & End Conditions", href: "/global/custom-start-end-conditions" }, // global + { title: "Start & End Dates", href: "/global/custom-start-end-conditions" }, // global + { title: "Limit submissions", href: "/global/limit-submissions" }, // global { title: "Recall Functionality", href: "/global/recall" }, // global { title: "Partial Submissions", href: "/global/partial-submissions" }, // global ], @@ -89,7 +91,8 @@ export const navigation: Array = [ { title: "User Metadata", href: "/global/metadata" }, { title: "Custom Styling", href: "/global/overwrite-styling" }, // global { title: "Conditional Logic", href: "/global/conditional-logic" }, - { title: "Custom Start & End Conditions", href: "/global/custom-start-end-conditions" }, + { title: "Start & End Dates", href: "/global/custom-start-end-conditions" }, + { title: "Limit submissions", href: "/global/limit-submissions" }, // global { title: "Recall Functionality", href: "/global/recall" }, { title: "Verify Email before Survey", href: "/link-surveys/verify-email-before-survey" }, { title: "PIN Protected Surveys", href: "/link-surveys/pin-protected-surveys" }, diff --git a/apps/docs/next.config.mjs b/apps/docs/next.config.mjs index 8631631961..aea0d3af00 100644 --- a/apps/docs/next.config.mjs +++ b/apps/docs/next.config.mjs @@ -1,5 +1,4 @@ import nextMDX from "@next/mdx"; - import { recmaPlugins } from "./mdx/recma.mjs"; import { rehypePlugins } from "./mdx/rehype.mjs"; import { remarkPlugins } from "./mdx/remark.mjs"; @@ -105,17 +104,18 @@ const nextConfig = { destination: "/app-surveys/user-identification", permanent: true, }, + // Global Features + { + source: "/global/custom-start-end-conditions", + destination: "/global/schedule-start-end-dates", + permanent: true, + }, // Integrations { source: "/integrations/:path", destination: "/developer-docs/integrations/:path", permanent: true, }, - { - source: "/global/custom-styling", - destination: "/global/overwrite-styling", - permanent: true, - }, ]; }, };