Databases Documentation#3072
Conversation
Split the Databases docs into a menu of database types. The /docs/products/databases overview becomes a menu (Appwrite databases: TablesDB, DocumentsDB, VectorsDB; Native databases: PostgreSQL, MySQL). Existing TablesDB content moves under /tablesdb with its full sidebar; DocumentsDB, VectorsDB, PostgreSQL, and MySQL get their own sections with placeholder overviews. Adds redirects for all moved pages.
Add DocumentsDB docs (concepts and journeys) under databases/documentsdb, move TablesDB within the databases section with redirects from the previous URLs, and align the backups and bulk operations pages.
Appwrite WebsiteProject ID: Website (appwrite/website)Project ID: Tip Environment variable changes require redeployment to take effect |
Greptile SummaryThis PR restructures the Appwrite Databases documentation by moving TablesDB under a new
Confidence Score: 5/5Safe to merge — all changed files are documentation content and routing config with no application logic changes. The changes are documentation pages, sidebar layouts, and redirect rules. The redirect coverage for old URLs is thorough, the deprecation banner logic is straightforward, and all new image files have matching cache entries. The two findings are cosmetic/navigational nits that do not break any routes. No files require special attention beyond the two minor inconsistencies flagged in tablesdb/legacy/+page.ts and vectorsdb/+layout.svelte. Important Files Changed
Reviews (2): Last reviewed commit: "Address review feedback on DocumentsDB d..." | Re-trigger Greptile |
| const parent: NavParent = { | ||
| href: '/docs/products/databases', | ||
| label: 'DocumentsDB' | ||
| }; |
There was a problem hiding this comment.
The
parent.label for DocumentsDB is set to 'DocumentsDB' but the parent.href points to /docs/products/databases (the Databases overview). The Sidebar renders this label as a visible section heading above a back-arrow link. Every other database sub-product layout — tablesdb, mysql, postgresql, vectorsdb — correctly uses label: 'Databases' for this same parent href, so DocumentsDB users would see a confusing "DOCUMENTSDB" label where they'd expect "DATABASES".
| const parent: NavParent = { | |
| href: '/docs/products/databases', | |
| label: 'DocumentsDB' | |
| }; | |
| const parent: NavParent = { | |
| href: '/docs/products/databases', | |
| label: 'Databases' | |
| }; |
| {% arrow_link href="/docs/products/databases/tablesdb/quick-start" %} | ||
| Quick start | ||
| {% /arrow_link %} No newline at end of file |
There was a problem hiding this comment.
The file is missing a trailing newline. Many editors and linters expect text files to end with a newline character.
| {% arrow_link href="/docs/products/databases/tablesdb/quick-start" %} | |
| Quick start | |
| {% /arrow_link %} | |
| {% arrow_link href="/docs/products/databases/tablesdb/quick-start" %} | |
| Quick start | |
| {% /arrow_link %} |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
|
WIP - console screenshots & import / export |


Summary