Can this be used for snowflake databases? I was looking at supported engines at https://schemahero.io/databases/

On https://schemahero.io/tutorial/create-table/ :

We need a table that will hold all reservations. The table should look like this:

// pic

I'm assuming there's meant to be an actual image instead of the // pic placeholder :)

The current docs are a little difficult to navigate. If we moved to the mkdocs material theme, we could speed up the build process and flatten the navigation.

Other recent CNCF projects have adopted this, and it's not too different from what we have now.

Example:
https://docs.tinkerbell.org

The default choice to write and deploy database migrations in Kubernetes is to wrap them in a Job. This approach has some drawbacks, and SchemaHero docs could explain this to help show the value in the operator approach.

• Transparency in debugging
• Sequencing
• Tightly coupling database migrations with an app migration
• ???

Suggestion:
Add a CODEOWNERS file to get reviewers assigned. I've had a PR sitting for months. These are PRs that likely come from people trying to adopt SchemaHero and are trying to help others get past documentation blockers.

I've seen a dupe #73 of #56 get merged recently and I'm confused about how that happened.

Take care!

There is a typo for intructions at page - https://github.com/schemahero/schemahero-docs/blob/b60942fc58419629fbcb61c1d22f0c1eb7352385/docs/learn/comparisons/sequential-migrations.md

a developer writes intructions that will be executed

I can make a contribution for this tiny fix, can you share contribution guidelines?

Right now, docs are a little difficult to manage with the release cycle.

If the docs were merged into the schemahero repo, and published on tag/release, then we could more easily stage the docs.

What best practices or recommendations exist for this?