Revamp introduction page with DevSecOps positioning

[d-bytebase]

Summary

• Restructured the what-is-bytebase.mdx introduction page to better position Bytebase as a DevSecOps control plane
• Emphasized two core value propositions: Productivity & Reliability, and Security & Compliance
• Retained product comparisons while improving their messaging

Changes Made

• Updated title to "Bytebase: The DevSecOps Control Plane for Your Databases"
• Reorganized content into two main workflow sections
• Refined comparison sections with stronger positioning against alternatives
• Maintained visual assets (comparison charts) to demonstrate market success

Test plan

• Review markdown formatting and structure
• Verify all links remain functional
• Confirm images are properly referenced
• Preview in Mintlify dev server to ensure proper rendering

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
bytebase-com	Ready	Preview	Comment	Aug 27, 2025 9:42am

[Copilot]

Pull Request Overview

This PR revamps the Bytebase introduction page to better position the product as a DevSecOps control plane for databases. The restructuring emphasizes two core value propositions while maintaining product comparison content.

• Reorganized content into two main workflow sections focused on productivity/reliability and security/compliance
• Updated the page title and messaging to emphasize DevSecOps positioning
• Streamlined comparison sections while retaining competitive differentiation

Comments suppressed due to low confidence (1)

mintlify/introduction/what-is-bytebase.mdx:51

• The CloudBeaver comparison link is retained but the corresponding section text was removed. Consider removing this link as well since the comparison context no longer exists in the document.

- [Bytebase vs. DBeaver](https://www.bytebase.com/blog/bytebase-vs-dbeaver/)

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[github-actions]

📝 Broken Links Check Report

Note: Entries under /api-reference/ are likely false positives and can be ignored.

The following is the output from the broken links check:

found 16 broken links in 9 files

integrations/api/audit-log.mdx
 ⎿  /api-reference/auditlogservice/post-v1auditlogs:search

integrations/api/authentication.mdx
 ⎿  /api-reference/authservice/post-v1authlogin

integrations/api/data-classification.mdx
 ⎿  /api-reference/settingservice/patch-v1settings
 ⎿  /api-reference/databaseservice/patch-v1instances-databases

integrations/api/issue.mdx
 ⎿  /api-reference/issueservice/post-v1projects-issues

integrations/api/permission.mdx
 ⎿  /api-reference/workspaceservice/get-v1workspaces-:getIamPolicy
 ⎿  /api-reference/projectservice/get-v1projects-:getIamPolicy
 ⎿  /api-reference/roleservice/get-v1roles
 ⎿  /api-reference/userservice/get-v1users
 ⎿  /api-reference/groupservice/get-v1groups

integrations/api/plan.mdx
 ⎿  /api-reference/planservice/post-v1projects-plans
 ⎿  /api-reference/sheetservice/post-v1projects-sheets

integrations/api/release.mdx
 ⎿  /api-reference/releaseservice/post-v1projects-releases

integrations/api/rollout.mdx
 ⎿  /api-reference/rolloutservice/post-v1projects-rollouts

integrations/api/sql-review.mdx
 ⎿  /api-reference/releaseservice/post-v1projects-releases:check
 ⎿  /api-reference/sqlservice/post-v1sqlcheck

[tianzhou]

I prefer to keep the image. It's quicker to consume and grasp the idea than to parse a lot of words at first sight.

[d-bytebase]

I prefer to keep the image. It's quicker to consume and grasp the idea than to parse a lot of words at first sight.

Images are great. But not the existing images, need to replace the image in the next PR.

[tianzhou]

Then let's keep the image for now and replace it in the next PR for review. The wording improvement is good. But the current images are intentionally made this way.

[tianzhou]

To provide more context about those 2 images in the first place:

1. The first one is to showcase Bytebase's strength (in particular, showcase the API part)
2. The 2nd one is to allow visitors to grasp the idea using tools they are familiar with quickly.

[tianzhou]

LGTM

[tianzhou]

nit: adjust the wording to avoid the line wrapping

[d-bytebase]

nit: adjust the wording to avoid the line wrapping

#849

Line wrapping isn't a problem when we have to reveal the full messaging. The real issue is that the excessive wording makes the "On this page" section look cluttered and awkward previously. Fixed.