From 77ab39573595294f320b848be3a949ee4a8cd489 Mon Sep 17 00:00:00 2001 From: Rizel Scarlett Date: Sun, 28 Sep 2025 23:53:56 -0400 Subject: [PATCH] Add .goosehints file to enforce lowercase branding in documentation (#4870) Co-authored-by: Angie Jones --- documentation/.goosehints | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 documentation/.goosehints diff --git a/documentation/.goosehints b/documentation/.goosehints new file mode 100644 index 0000000000..97e4cb047b --- /dev/null +++ b/documentation/.goosehints @@ -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".