fix: Moved Integrations in Formbricks Docs to Core Features

[iamitpal]

What does this PR do?

This PR will Move Integrations in Formbricks Docs to Core Features

Fixes #3541

How should this be tested?

• Previously Integrations were part of the Developer Docs in the Formbricks Docs.
• Now they moved under Core Features

Checklist

Required

• [X] Filled out the "How to test" section in this PR
• [X] Read How we Code at Formbricks
• [X] Self-reviewed my own code
• [X] Commented on my code in hard-to-understand bits
• [X] Ran pnpm build
• [X] Checked for warnings, there are none
• [X] Removed all console.logs
• [X] Merged the latest changes from main onto my branch with git pull origin main
• [X] My changes don't cause any responsiveness issues
• [ ] First PR at Formbricks? Please sign the CLA! Without it we wont be able to merge it 🙏

Appreciated

• [ ] If a UI change was made: Added a screen recording or screenshots to this PR
• [ ] Updated the Formbricks Docs if changes were necessary

Summary by CodeRabbit

• New Features

  • Introduced a new "Integrations" section under "Core Features" in the documentation navigation, featuring links to various integration options including Airtable, Google Sheets, and more.

• Changes

  • Removed the "Integrations" section from the "Developer Docs" category, streamlining the documentation structure.

[vercel[bot]]

@iamitpal is attempting to deploy a commit to the formbricks Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai[bot]]

Walkthrough

The changes involve the relocation of the "Integrations" section from the "Developer Docs" category to the "Core Features" category within the navigation array of the apps/docs/lib/navigation.ts file. This update includes the addition of various integration options with hyperlinks to their documentation, while the previous section in the "Developer Docs" has been removed. The overall structure of the navigation remains unchanged apart from this adjustment.

Changes

File Path	Change Summary
apps/docs/lib/navigation.ts	- Removed "Integrations" section from "Developer Docs". - Added "Integrations" section to "Core Features" with links: "Overview", "Airtable", "Google Sheets", "Make", "n8n", "Notion", "Slack", "Wordpress", "Zapier".

Assessment against linked issues

Objective	Addressed	Explanation
Move Integrations to Core Features (#3541)	✅

Possibly related PRs

• #3365: Updates redirect links in the Developer documentation, relevant to the navigation structure changes.
• #3415: Modifies links related to Gitpod and GitHub Codespaces, aligning with the main PR's navigation updates.
• #3488: Focuses on the navigation component, directly related to the organization of navigation items in the main PR.

Suggested labels

🕹️ oss.gg, 🕹️ 50 points

Suggested reviewers

• gupta-piyush19
• mattinannt

🐇 In the docs, a change so bright,
Integrations now in plain sight.
From dev docs they took their flight,
To core features, what a delight!
With links to tools, oh what a sight!
Hop along, it's all done right! 🌟

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions[bot]]

Thank you for following the naming conventions for pull request titles! 🙏

[Dhruwang]

Hey @iamitpal , thanks for the PR but this has already been shipped 😊