We use certain words in a special way. This word list defines our terminology to make sure we all use the same words for the same things.
Writing about ourselves
We describe ourselves with a few different names depending on context, and we should use the right term at the right time.
- Sourcegraph: Main product. This name is always preferred unless you need to clarify between the 3 deployment methods for Sourcegraph below.
- Sourcegraph self-hosted: On-premises and self-managed version of Sourcegraph.
- Sourcegraph Cloud Dedicated, single-tenant Sourcegraph instances managed and provisioned by the Sourcegraph team. This was previously referred to as “managed instances.”
- Sourcegraph.com / “dotcom”: This is the service publicly available at sourcegraph.com. It can be used to search top open source repositories.
- Sourcegraph OSS: When referring to the build result of the open source repository.
- Sourcegraph integrations: The general term for our integrations. When referencing specific integrations:
- Sourcegraph(’s) Phabricator integration
- Sourcegraph(’s) GitHub integration
- Sourcegraph(’s) browser extensions
- Sourcegraph(’s) Chrome extension
- Sourcegraph(’s) Firefox add-on
- Code intelligence platform: Use when referring to our category or our entire suite of products and features.
You don’t need to use the full name of the product each time you refer to it, but don’t use a shortened name that could be confused with an official name.
Always title case our name. Don’t abbreviate or add a space to our name.
Only use we and our (as in “our GitHub integration”) in informal documents. In documentation or marketing material, depending on the context, just avoid it, or use “the” or “Sourcegraph”.
|Use this||Not this||Why?|
|admin or site admin||“administrator” or “site administrator”||More conversational, per Quinn|
|alerts||Sourcegraph sends an alert to a notifier that sends a notification to the user. If we’re talking about what the product does, it’s alerting. If we’re talking about what the user experiences, it’s notifier/notifying.|
|Big code||both capitalized|
|call site||callsite||Per Quinn|
|codebase||code base||Most commonly spelled as a single word.|
|code host||codehost||Per Quinn|
|code host connection||external service||Aligning terminology for clarity. Internally, we differentiate different ownership through the terms “user code host connections, “organization code host connections,” and “instance code host connections.”|
|configuration||config||“config” is OK in paths and navigation links|
|custom search pages||Custom search pages allow users to quickly search within a set of curated repositories, with data and interesting searches shared on that page. For example, “use this custom search page for Python 2-to-3 migration code”. When possible, use the more specific names Search scope page, a more specific name for a custom search page that describes search pages at /search/scope/SCOPENAME, or project search page, a more specific name for a custom search page that describes pages for projects. For example, the Kubernetes project search page to search across all Kubernetes code.|
|data structure||datastructure||Favoring common usage|
|docs||documentation||Our voice is conversational and plainspoken. “Documentation” is overly formal, while “docs” is the common term today.|
|email address||The two are both nouns, meaning different things.|
|field||Refers to the first part in the key:value pair|
|filter||Filter describes a parameter that can be added to a query to narrow down search results. A filter is always a parameter, but a parameter may not be a filter.|
|go to definition||jump to definition”, “jump-to-def”, or “j2d”|
|lifecycle||life cycle||Favoring common usage|
|macOS||OS X, OSX, MacOS, MacOSX|
|notifier||Sourcegraph sends an alert to a notifier that sends a notification to the user. If we’re talking about what the product does, it’s alerting. If we’re talking about what the user experiences, it’s notifier/notifying.|
|npm||NPM||Based on npm’s branding guidelines. For code, use |
|organization||“company” or “team” or “org”|
|open source||“open-source”, “Open Source”||Favoring common usage|
|parameter||Parameter describes a key:value pair to filter behavior or change search behavior.|
|PostgreSQL||Postgres, postgres, PgSQL, Postgresql, PostGres,||Proper name|
|repository||repo||We try to avoid abbreviations when possible. We habitually shorten words for concepts we work with every day until they become obvious to us, like repo, org, j2d, find-refs, PR, revs… but they aren’t obvious to outsiders, which can be confusing and result in a steeper learning curve for new users. In this spirit, we prefer “repository” and “repositories”.|
|saved searches||Saved searches describe complete searches that are used without needing to add more filters or expressions.|
|SCIP||Scip||It’s a recursive acronym for the SCIP Code Intelligence Protocol. The name may be all lowercase (|
|search expression||Search expression describes a valid piece of a search that can be suggested and combined with other expressions to drill down on results.|
|search scope||version context||Used to describe drilling down in a pre-configured scope of repositories across the entire Sourcegraph instance (this persists for navigation and usage outside of the query bar search).|
|set up (v)/setup (n)||Setup is a noun, set up is a verb (see notaverb.com/setup, although see note on descriptivism)|
|sign in||log in||Because it’s a better UX choice.|
|Sourcegraph||“sourcegraph”, “SourceGraph”, or “sg”|