Ensure that 'frontend' (noun and adjective) is used consistently#685
Merged
IEvangelist merged 4 commits intomicrosoft:mainfrom Apr 8, 2026
Merged
Conversation
…consistently as described in Microsoft style guide.
alistairmatthews
requested review from
IEvangelist,
JamesNK and
eerhardt
as code owners
Contributor
There was a problem hiding this comment.
Pull request overview
Updates Aspire.dev documentation/UI copy to follow Microsoft style guidance: use “front end” as a noun and “front-end” as an adjective, improving consistency across the site.
Changes:
- Replaces inconsistent “frontend/frontend” usages with “front end” or “front-end” depending on grammatical role.
- Updates various docs pages (what’s new, integrations, deployment, dashboard, get-started, architecture) and one UI tooltip string.
Reviewed changes
Copilot reviewed 27 out of 35 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| src/frontend/src/content/i18n/en.json | Updates tooltip wording to “front-end” adjective form. |
| src/frontend/src/content/docs/whats-new/aspire-9-5.mdx | Standardizes “front-end assets” wording in release notes. |
| src/frontend/src/content/docs/whats-new/aspire-9-3.mdx | Standardizes references to “front-end apps” and “front end” nouns. |
| src/frontend/src/content/docs/whats-new/aspire-13.mdx | Aligns starter-template and container-files wording with style guidance. |
| src/frontend/src/content/docs/whats-new/aspire-13-1.mdx | Standardizes “front-end” phrasing in headings and links. |
| src/frontend/src/content/docs/integrations/reverse-proxies/yarp.mdx | Updates “front-end applications” phrasing. |
| src/frontend/src/content/docs/integrations/frameworks/javascript.mdx | Standardizes “front end/front-end” wording in JavaScript integration docs. |
| src/frontend/src/content/docs/integrations/dotnet/project-resources.mdx | Updates image alt text to “front-end app” adjective form. |
| src/frontend/src/content/docs/integrations/devtools/k6.mdx | Updates “front-end performance metrics” phrasing. |
| src/frontend/src/content/docs/get-started/troubleshooting.mdx | Uses “front end” noun form in troubleshooting guidance. |
| src/frontend/src/content/docs/get-started/glossary.mdx | Updates glossary entry to “front-end service” adjective form. |
| src/frontend/src/content/docs/get-started/first-app-typescript-apphost.mdx | Standardizes “web front end” phrasing in starter walkthrough. |
| src/frontend/src/content/docs/get-started/first-app-csharp-apphost.mdx | Standardizes “web front end” phrasing in starter walkthrough. |
| src/frontend/src/content/docs/get-started/deploy-first-app-csharp.mdx | Updates diagram label to “Front-end container”. |
| src/frontend/src/content/docs/get-started/aspire-sdk-templates.mdx | Standardizes “front end/front-end application” template descriptions. |
| src/frontend/src/content/docs/get-started/app-host.mdx | Standardizes terminology in AppHost conceptual walkthrough and examples. |
| src/frontend/src/content/docs/get-started/add-aspire-existing-app-typescript-apphost.mdx | Standardizes JavaScript deployment note and references to “front end/front-end”. |
| src/frontend/src/content/docs/get-started/add-aspire-existing-app-csharp-apphost.mdx | Standardizes JavaScript deployment note references to “front end/front-end”. |
| src/frontend/src/content/docs/fundamentals/service-discovery.mdx | Uses “front end” noun form in conceptual explanation. |
| src/frontend/src/content/docs/fundamentals/networking-overview.mdx | Updates image alt text to “front-end app” adjective form. |
| src/frontend/src/content/docs/deployment/pipelines.mdx | Standardizes front-end related step descriptions. |
| src/frontend/src/content/docs/deployment/overview.mdx | Uses “front end” noun form in examples. |
| src/frontend/src/content/docs/deployment/javascript-apps.mdx | Standardizes terminology throughout deployment models. |
| src/frontend/src/content/docs/dashboard/standalone-for-python.mdx | Uses “React front end” noun form in tutorial intro. |
| src/frontend/src/content/docs/dashboard/security-considerations.mdx | Standardizes “front end” wording in security section. |
| src/frontend/src/content/docs/dashboard/overview.mdx | Standardizes terminology in overview text. |
| src/frontend/src/content/docs/dashboard/index.mdx | Uses “front-end performance data” adjective form in card description. |
| src/frontend/src/content/docs/dashboard/configuration.mdx | Standardizes “front end/front-end endpoint” wording in config docs. |
| src/frontend/src/content/docs/architecture/resource-model.mdx | Uses “front-end app” adjective form in architecture bullets. |
| src/frontend/src/content/docs/architecture/resource-hierarchies.mdx | Standardizes “front-end” adjective form in examples. |
| src/frontend/src/content/docs/app-host/migrate-from-docker-compose.mdx | Uses “front end/front-end” forms consistently in migration guidance. |
| src/frontend/src/content/docs/app-host/executable-resources.mdx | Standardizes “front-end development servers/applications” wording. |
| src/frontend/src/content/docs/app-host/container-files.mdx | Standardizes “front end/front-end assets” phrasing in container files guide. |
| src/frontend/src/content/docs/app-host/configuration.mdx | Updates “front-end browser token” wording in config table. |
| src/frontend/src/content/docs/app-host/certificate-configuration.mdx | Uses “front end” noun form in example text. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
src/frontend/src/content/docs/integrations/frameworks/javascript.mdx
Outdated
Show resolved
Hide resolved
Member
|
We discussed this a while back and landed on |
alistairmatthews
requested review from
aaronpowell,
davidfowl and
maddymontaquila
as code owners
Contributor
Author
Fair enough. All fixed. Did these differences between our style and Microsoft style get documented anywhere? |
alistairmatthews
changed the title
IEvangelist
approved these changes
Apr 8, 2026
Member
No, I don't think so. 😬 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Microsoft style guide says:
"It's OK to use these terms in content for a technical audience.
Two words as a noun. Hyphenate as an adjective."
front end, front-end
However, in Aspire.dev it's been decided to use "frontend" for both noun and adjective. This PR implements that guidance.
Fixes: #646