Add .goosehints file to enforce lowercase branding in documentation (#4870)

Co-authored-by: Angie Jones <jones.angie@gmail.com>
This commit is contained in:
Rizel Scarlett 2025-09-28 23:53:56 -04:00 committed by GitHub
parent cbefc3b8bd
commit 77ab395735
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

21
documentation/.goosehints Normal file
View file

@ -0,0 +1,21 @@
# Documentation Style Guide
## Brand Guidelines
**IMPORTANT**: The product name "goose" should ALWAYS be written in lowercase "g" in all documentation, blog posts, and any content within this documentation directory.
- ✅ Correct: "goose", "using goose", "goose provides"
- ❌ Incorrect: "Goose", "using Goose", "Goose provides"
This is a brand guideline that must be strictly followed.
## Context
This rule applies to:
- All markdown files in `/docs/`
- All blog posts in `/blog/`
- README files
- Configuration files with user-facing text
- Any other documentation content
When editing or creating content in this documentation directory, always ensure "goose" uses a lowercase "g".