docs(branding): rename Team360 to Team Health Check - #137
Conversation
Replace Team360 branding with Team Health Check across the project documentation, frontend metadata, backend documentation, Makefiles, Grafana dashboard titles, and UI fallback branding to reflect the new project identity. Changes include: - Update project documentation and architecture guides - Rename backend/frontend README titles - Update Makefile output messages - Rename Grafana dashboard titles and descriptions - Update frontend metadata and default application name
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
All reported issues were addressed across 13 files
Reply with feedback, questions, or to request a fix.
Fix all with cubic | Re-trigger cubic
Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com> Signed-off-by: Kavindu Sachinthe <kavix@yahoo.com>
|
Thanks @kavix, this is a well-scoped PR and the out-of-scope discipline is spot on: I verified the module path, image names, DB names, telemetry prefixes, and k8s resource names are all correctly left as One gap before merge. Checking out the head and grepping for
Optional, lower priority: the header comments on line 2 of With the README in particular, criterion "No user-visible string renders Team360" is not met yet. Once those are in I will approve the workflow run and merge. Thanks again! |
Updated all instances of 'Team360' to 'Team Health Check' for consistency throughout the README. Signed-off-by: Kavindu Sachinthe <kavix@yahoo.com>
Signed-off-by: Kavindu Sachinthe <kavix@yahoo.com>
Fix application name in start-dev.sh
Signed-off-by: Kavindu Sachinthe <kavix@yahoo.com>
Signed-off-by: Kavindu Sachinthe <kavix@yahoo.com>
Signed-off-by: Kavindu Sachinthe <kavix@yahoo.com>
Signed-off-by: Kavindu Sachinthe <kavix@yahoo.com>
Signed-off-by: Kavindu Sachinthe <kavix@yahoo.com>
Signed-off-by: Kavindu Sachinthe <kavix@yahoo.com>
Signed-off-by: Kavindu Sachinthe <kavix@yahoo.com>
Signed-off-by: Kavindu Sachinthe <kavix@yahoo.com>
Signed-off-by: Kavindu Sachinthe <kavix@yahoo.com>
|
Thanks for the detailed review, @ANIRUDH-333! I’ve addressed the remaining user-facing Team360 references:
I’ve kept the migration SQL comment unchanged as requested. Thanks again for catching these consistency issues. The changes should now satisfy the “No user-visible string renders Team360” requirement. Please take another look when you get a chance. |
There was a problem hiding this comment.
All reported issues were addressed across 9 files (changes from recent commits).
Tip: Review your code locally with the cubic CLI to iterate faster.
Fix all with cubic | Re-trigger cubic
|
@ANIRUDH-333 Can u Re-Review? |
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
Thanks for the follow-up, @kavix. I re-reviewed the current head ( The browser title, application header fallback, listed README/docs text, and the protected internal identifiers are handled correctly. However, the acceptance criterion “No user-visible string renders Team360” is still not satisfied. The following user-visible strings remain:
Also, Please do a complete repository-wide pass for |
|
Hi @kavix , I’m currently working on the documentation part for the PR. Instead of just creating Regarding this PR: #113, it’s not complete yet. I’m still working on it to ensure it meets the expected results and provides a better documentation experience for users. |
There was a problem hiding this comment.
3 issues found across 14 files (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="backend/infrastructure/email/templates.go">
<violation number="1" location="backend/infrastructure/email/templates.go:140">
P3: The footer now reads "Team Health Check — Team Health Check Platform", which is redundant after the rename (previously it read "Teams360 — Team Health Check Platform" as a product-name/dash/tagline pair). Simplify to just "Team Health Check Platform" to avoid an awkward duplicated product name in the rendered emails.</violation>
</file>
<file name="frontend/package.json">
<violation number="1" location="frontend/package.json:5">
P1: Adding `"type": "module"` makes the CommonJS `postcss.config.js` and `tailwind.config.js` be interpreted as ES modules. `require()` of them throws `ERR_REQUIRE_ESM` (verified), so PostCSS/Tailwind config loading during dev/build breaks and Tailwind utilities stop being generated on a fresh checkout. Rename these configs to `.cjs` (or `.mjs` with ESM exports), or drop `"type": "module"` from package.json.</violation>
<violation number="2" location="frontend/package.json:49">
P3: Adding happy-dom as the Vitest environment makes the still-declared `jsdom` devDependency unused. Consider dropping `jsdom` (and its types) to avoid a confusing duplicate DOM library in package.json.</violation>
</file>
Tip: Review your code locally with the cubic CLI to iterate faster.
Fix all with cubic | Re-trigger cubic
| "name": "team360-health-check", | ||
| "version": "0.1.0", | ||
| "private": true, | ||
| "type": "module", |
There was a problem hiding this comment.
P1: Adding "type": "module" makes the CommonJS postcss.config.js and tailwind.config.js be interpreted as ES modules. require() of them throws ERR_REQUIRE_ESM (verified), so PostCSS/Tailwind config loading during dev/build breaks and Tailwind utilities stop being generated on a fresh checkout. Rename these configs to .cjs (or .mjs with ESM exports), or drop "type": "module" from package.json.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At frontend/package.json, line 5:
<comment>Adding `"type": "module"` makes the CommonJS `postcss.config.js` and `tailwind.config.js` be interpreted as ES modules. `require()` of them throws `ERR_REQUIRE_ESM` (verified), so PostCSS/Tailwind config loading during dev/build breaks and Tailwind utilities stop being generated on a fresh checkout. Rename these configs to `.cjs` (or `.mjs` with ESM exports), or drop `"type": "module"` from package.json.</comment>
<file context>
@@ -2,6 +2,7 @@
"name": "team360-health-check",
"version": "0.1.0",
"private": true,
+ "type": "module",
"scripts": {
"dev": "next dev",
</file context>
| </td></tr> | ||
| <tr><td style="background:#F9FAFB;padding:16px 32px;text-align:center;"> | ||
| <p style="margin:0;color:#9CA3AF;font-size:11px;">Teams360 — Team Health Check Platform</p> | ||
| <p style="margin:0;color:#9CA3AF;font-size:11px;">Team Health Check — Team Health Check Platform</p> |
There was a problem hiding this comment.
P3: The footer now reads "Team Health Check — Team Health Check Platform", which is redundant after the rename (previously it read "Teams360 — Team Health Check Platform" as a product-name/dash/tagline pair). Simplify to just "Team Health Check Platform" to avoid an awkward duplicated product name in the rendered emails.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At backend/infrastructure/email/templates.go, line 140:
<comment>The footer now reads "Team Health Check — Team Health Check Platform", which is redundant after the rename (previously it read "Teams360 — Team Health Check Platform" as a product-name/dash/tagline pair). Simplify to just "Team Health Check Platform" to avoid an awkward duplicated product name in the rendered emails.</comment>
<file context>
@@ -137,7 +137,7 @@ func RenderIndividualSurveyEmail(data IndividualSurveyEmailData) string {
</td></tr>
<tr><td style="background:#F9FAFB;padding:16px 32px;text-align:center;">
- <p style="margin:0;color:#9CA3AF;font-size:11px;">Teams360 — Team Health Check Platform</p>
+ <p style="margin:0;color:#9CA3AF;font-size:11px;">Team Health Check — Team Health Check Platform</p>
</td></tr>
</table>
</file context>
| <p style="margin:0;color:#9CA3AF;font-size:11px;">Team Health Check — Team Health Check Platform</p> | |
| <p style="margin:0;color:#9CA3AF;font-size:11px;">Team Health Check Platform</p> |
| "autoprefixer": "^10.4.21", | ||
| "eslint": "^8.57.1", | ||
| "eslint-config-next": "^15.5.12", | ||
| "happy-dom": "^20.11.1", |
There was a problem hiding this comment.
P3: Adding happy-dom as the Vitest environment makes the still-declared jsdom devDependency unused. Consider dropping jsdom (and its types) to avoid a confusing duplicate DOM library in package.json.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At frontend/package.json, line 49:
<comment>Adding happy-dom as the Vitest environment makes the still-declared `jsdom` devDependency unused. Consider dropping `jsdom` (and its types) to avoid a confusing duplicate DOM library in package.json.</comment>
<file context>
@@ -45,6 +46,7 @@
"autoprefixer": "^10.4.21",
"eslint": "^8.57.1",
"eslint-config-next": "^15.5.12",
+ "happy-dom": "^20.11.1",
"jsdom": "^27.2.0",
"postcss": "^8.5.6",
</file context>
Summary
Closes #136
This PR updates user-facing branding from Team360 to Team Health Check across the application and documentation. It replaces the old product name in UI text, documentation, Makefile output, and Grafana dashboard metadata while intentionally preserving internal identifiers that must remain teams360 for compatibility.
Changes
Application UI
Documentation
Developer Experience
Observability
Out of Scope
Per the issue requirements, this PR does not rename internal identifiers or compatibility-sensitive resources, including:
Testing
Checklist
Closes #136.
Summary by cubic
Renamed all user-facing branding from Team360 to Team Health Check across the app, docs, emails, and tooling, per #136. Internal identifiers remain
teams360for compatibility (module path, images, DBs, telemetry prefixes, resource names).app_settings.company_namewith “My Company” as the default..env.example, and scripts; fixed the broken issue tracker link inCONTRIBUTING.md.happy-dom, added thehappy-domdev dependency, setfrontend/package.jsonto"type": "module", and added an integration test for organization settings fallback.Written for commit 99e853f. Summary will update on new commits.