Software: add GORM and SchemaBot (#171)

Two Go ecosystem tools with first-class MySQL support, not yet in the
catalog and not covered by the still-open resources/auto-2026-10-31 PR.


Claude-Session: https://claude.ai/code/session_011ngofHUCfJpcdn9R2VTQxL

Co-authored-by: Claude <[email protected]>

Author: Mazizova

content/resources/software/gorm/index.md

@@ -0,0 +1,21 @@
+---
+title: "GORM"
+link: "https://gorm.io"
+github: "go-gorm/gorm"
+description: "A full-featured ORM for Go, with first-class MySQL and MariaDB support through its official `gorm.io/driver/mysql` driver (built on go-sql-driver/mysql), alongside associations, hooks, transactions, auto-migrations, and a SQL builder."
+subcategories:
+  - Connectors & Drivers
+compatibility:
+  - MySQL
+  - MariaDB
+pricing:
+  - Open Source
+images:
+  - logo.png
+---
+
+GORM is a developer-friendly ORM for Go covering associations (has one, has many, belongs to, many-to-many, polymorphism), hooks for before/after create, save, update and delete, eager loading with `Preload` and `Joins`, transactions and nested transactions with save points, prepared-statement and dry-run modes, batch inserts, a SQL builder with upsert and locking support, composite primary keys, and auto-migrations.
+
+Its official `gorm.io/driver/mysql` driver connects through `go-sql-driver/mysql` and adds MySQL-specific configuration — default string sizing, datetime precision handling (including a flag for pre-5.6 MySQL, which lacks datetime precision), and dialect-specific DDL for `AutoMigrate`. A `DBResolver` plugin on top of the core library adds multiple-database support and read/write splitting.
+
+Maintained by the go-gorm organization as the actively developed successor to the original `jinzhu/gorm`, it's released under the MIT license and has around 39.7k stars on GitHub.

content/resources/software/gorm/logo.png

@@ -0,0 +1,24 @@
+---
+title: "SchemaBot"
+link: "https://github.com/block/schemabot"
+github: "block/schemabot"
+description: "A GitOps schema-migration tool from Block — SQL files in your repo are the source of truth, and SchemaBot plans and applies the diff against MySQL, Vitess on PlanetScale, or (early alpha) PostgreSQL through pull requests or a CLI."
+subcategories:
+  - Schema Management & Migration
+compatibility:
+  - MySQL
+  - Vitess
+deployment:
+  - Self-Hosted
+  - Kubernetes
+pricing:
+  - Open Source
+images:
+  - logo.png
+---
+
+SchemaBot is declarative and GitOps-driven: SQL files in a repository act as the shared source of truth across environments. It compares those files against a database's live schema, shows the exact diff, and applies the change through a pull-request workflow or a CLI — importing an existing database's schema into declarative files on first run rather than requiring it to be written out by hand.
+
+For MySQL, schema changes are generally available and run through [Spirit](https://github.com/block/spirit), using instant DDL where supported and an online copy when needed; Vitess on PlanetScale is also generally available, driven through PlanetScale deploy requests with per-shard progress. PostgreSQL support is an early alpha. The PR workflow supports configurable review gates, a promotion order across environments (e.g. staging before production), and lint checks that flag destructive changes before they can be applied.
+
+Block (formerly Square) runs SchemaBot for the majority of its own production schema changes, including MySQL tables spanning terabytes and Vitess databases with hundreds of shards. It's released under the Apache-2.0 license, and distributed as release binaries, a `ghcr.io/block/schemabot` container image, and a Helm chart.