Skip to content

Commit 134e432

Browse files
d-bytebaseclaude
andauthored
refactor: improve introduction page heading readability (#849)
- Remove numbered prefixes from section headings to avoid line wrapping - Reorganize comparison sections under a unified "Compare" heading - Improve document structure and readability 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Claude <[email protected]>
1 parent e6743b6 commit 134e432

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

mintlify/introduction/what-is-bytebase.mdx

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Bytebase is the DevSecOps platform that sits between your team and your database
1010

1111
It's a unified platform specifically built for your **developer, security, DBA, and platform engineering teams** to collaborate. Its value becomes particularly critical as your organization grows, reducing the friction of managing a large number of databases and instances. Bytebase achieves this by consolidating two distinct workflows.
1212

13-
## 1. For Productivity & Reliability: Managing Schema Changes at Scale 🚀
13+
## Managing Schema Changes at Scale 🚀
1414

1515
This section covers how Bytebase makes all database changes safer and more efficient. By providing a structured process, it also enhances security by **eliminating the need for engineers to make direct changes against databases**. Bytebase supports two distinct workflows for schema changes:
1616

@@ -24,7 +24,7 @@ In addition to these workflows, the platform provides overarching capabilities f
2424

2525
**1-Click DML Rollback**: Provides streamlined, 1-click rollback for data changes (DML), allowing for instant recovery from unintended UPDATE or DELETE statements.
2626

27-
## 2. For Security & Compliance: Governing Data Access at Scale 🛡️
27+
## Governing Data Access at Scale 🛡️
2828

2929
This workflow governs how your database data is accessed, replacing the need for disparate SQL clients and shared credentials.
3030

@@ -38,7 +38,9 @@ In short, Bytebase unifies the process of **changing the database** with the **p
3838

3939
![venn](/content/docs/what-is-bytebase/venn.webp)
4040

41-
## How Bytebase Compares: Schema Migration Tools
41+
## Compare
42+
43+
### Schema Migration Tools
4244

4345
While Liquibase and Flyway are powerful command-line migration tools (think Git), Bytebase provides the complete platform experience (think GitHub/GitLab). It wraps these migration capabilities in a collaborative interface with approval workflows, audit trails, and enterprise controls. As the fastest-growing open source solution in this space, Bytebase has become the top choice for teams seeking a unified database DevSecOps platform.
4446

@@ -48,7 +50,7 @@ While Liquibase and Flyway are powerful command-line migration tools (think Git)
4850
- [Bytebase vs. Flyway](https://www.bytebase.com/blog/bytebase-vs-flyway/)
4951
- [Bytebase vs. schemachange](https://www.bytebase.com/blog/snowflake-schema-change/)
5052

51-
## How Bytebase Compares: SQL Clients
53+
### SQL Clients
5254

5355
Traditional SQL clients like DBeaver, DataGrip, and Navicat excel at individual database access but weren't built for team collaboration or enterprise security. Bytebase transforms SQL access from a personal tool into an enterprise-ready platform—providing not just query capabilities, but also role-based permissions, data masking, audit logging, and centralized governance that eliminates the need to share database credentials.
5456

0 commit comments

Comments
 (0)