-
Notifications
You must be signed in to change notification settings - Fork 2k
chore(docs): convert 'Turbo' into 'Turborepo' #10162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
if (product === "repo") { | ||
return `${title} | Turborepo`; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe worth keeping the | Turborepo in the title for tabs so you can quickly find your Turborepo docs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, good catch.
turbo: | ||
"Turbo is an incremental bundler and build system optimized for JavaScript and TypeScript, written in Rust.", | ||
"Turborepo is a build system optimized for JavaScript and TypeScript, written in Rust.", | ||
repo: "The build system that makes ship happen.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we still use both of these slogans in different places?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see only one other reference to "bundler" and its a keeper until I redesign the home page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, or did you mean more generally? We use both of these here and there but do need to audit/rework/pick one in time, yes.
Co-authored-by: Thomas Knickman <tom.knickman@vercel.com>
Co-authored-by: Thomas Knickman <tom.knickman@vercel.com>
@tknickman, thanks, go again! |
@@ -14,16 +13,13 @@ const client = algo( | |||
const index = client.initIndex(process.env.NEXT_PUBLIC_ALGOLIA_INDEX!); | |||
|
|||
export function SearchDialog(props: SharedProps): JSX.Element { | |||
const path = usePathname(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was this just unused?
|
||
## Teams | ||
|
||
**Core Team**: Turborepo and Turbopack teams at [Vercel](https://vercel.com) manage the direction of Turbo and leadership of the project. | ||
**Core Team**: Turborepo and Turbopack teams at [Vercel](https://vercel.com) manage the direction of Turborepo and leadership of the project. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to drop Turbopack mention?
Description
Swapping out places where things say "Turbo" to be "Turborepo" as we convert the site. When we say "Turbo", we mean
turbo
or "Turborepo".