[gjing1st]

What does this PR do?

Adds hertz-admin to the Bizdemo section.

About the project

hertz-admin is a production-ready Go backend scaffolding built on Hertz. Unlike the existing demo-oriented bizdemos, it targets the "start a real project" scenario: clone it and you can start writing business logic immediately without re-deciding project layout, error handling conventions, or auth wiring.

Key points:

• Architecture: follows the golang-standards/project-layout convention, with a one-way dependency chain router → controller → service → store → model (MCSS)

• Auth: three-level role model (login / admin / super admin) implemented as route-group middleware, with Bearer token

• Error handling: all errors converge into observable business error codes, decoupled from HTTP status codes

• Crypto: built-in SM3 (including HMAC-SM3 for password storage) and SM4 in CBC/ECB/CFB/OFB modes, plus SM4-GCM — aimed at Chinese regulated industries

• Versioning: follows the Kubernetes approach — git tag/commit is injected into the binary at build time and exposed via a /version endpoint

• Database adapters: MySQL, PostgreSQL, openGauss, KingbaseES, DM, SQLite and ClickHouse, all verified against real instances; only MySQL is enabled by default so drivers a project does not need never end up in the binary

• Ops: multi-arch Dockerfile, docker-compose, Kubernetes Deployment, Jenkinsfile

• Stack: Hertz v0.10.6, GORM, logrus + lumberjack, swag/Swagger

• Repository: https://github.com/gjing1st/hertz-admin

• License: Apache-2.0

• Actively maintained; last commit September 2026, currently on Hertz v0.10.6 and Go 1.27, complete vendor/ committed for offline/intranet builds

Happy to adjust the wording or the position in the list if needed. Thanks for the great work on Hertz!

[CLAassistant]

All committers have signed the CLA.

[gjing1st]

Hi @GuangmingLuo, sorry to bump this one.

This PR only adds a single link to the Bizdemo list — README.md and
README_CN.md, 2 lines total, and it has no conflicts.

The CLA check is green now. The typos and license-header workflows
haven't run yet — my guess is they're waiting for approval, since this is
my first contribution to this repo.

Whenever you get a moment, a quick look would be much appreciated. Happy
to adjust the wording, move the entry, or drop it entirely if it doesn't
fit the list's criteria.

Thanks!

[GuangmingLuo]

@gjing1st thanks, we won't add any more external examples, it's not necessary.