Skip to content

Commit f997e0b

Browse files
feat: add developer persona callouts to Get Started module
- Per-page persona callout added to all 6 topic pages - Links to discover:roles-and-tasks.adoc for role definitions Co-authored-by: Cursor <cursoragent@cursor.com>
1 parent d472de7 commit f997e0b

6 files changed

Lines changed: 12 additions & 0 deletions

modules/get-started/pages/authenticating-to-a-git-server-from-a-workspace.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@
99

1010
pass:[<!-- vale RedHat.CaseSensitiveTerms = NO -->]
1111

12+
This page is for developers who create and use cloud development environments. To learn more about common roles and example tasks referenced in {prod-short} documentation, see xref:discover:roles-and-tasks.adoc[].
13+
1214
In a workspace, you can run Git commands that require user authentication like cloning a remote private Git repository or pushing to a remote public or private Git repository.
1315

1416
User authentication to a Git server from a workspace is configured by the administrator or, in some cases, by the individual user:

modules/get-started/pages/basic-actions-you-can-perform-on-a-workspace.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@
99

1010
You manage your workspaces and verify their current states in the *Workspaces* page (`pass:c,a,q[{prod-url}]/dashboard/#/workspaces`) of your {prod-short} dashboard.
1111

12+
This page is for developers who create and use cloud development environments. To learn more about common roles and example tasks referenced in {prod-short} documentation, see xref:discover:roles-and-tasks.adoc[].
13+
1214
After you start a new workspace, you can perform the following actions on it in the *Workspaces* page:
1315

1416
.Basic actions you can perform on a workspace

modules/get-started/pages/starting-a-workspace-from-a-git-repository-url.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,8 @@ Selecting a branch or a tag will add the reference parameter to the URL.
1515
For GitHub, you can also use a repository URL of a directory with a devfile, or a repository URL of the devfile.
1616
The name of the devfile must be `devfile.yaml` or `.devfile.yaml`.
1717
18+
This page is for developers who create and use cloud development environments. To learn more about common roles and example tasks referenced in {prod-short} documentation, see xref:discover:roles-and-tasks.adoc[].
19+
1820
This feature is not supported for other Git providers.
1921
====
2022

modules/get-started/pages/starting-a-workspace-from-a-raw-devfile-url.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@
99

1010
With {prod-short}, you can open a *devfile* URL in your browser to start a new workspace.
1111

12+
This page is for developers who create and use cloud development environments. To learn more about common roles and example tasks referenced in {prod-short} documentation, see xref:discover:roles-and-tasks.adoc[].
13+
1214
pass:[<!-- vale RedHat.Spelling = NO -->]
1315

1416
TIP: You can use the *Git Repo URL* field on the *Create Workspace* page of your {prod-short} dashboard to enter the URL of a *devfile* to start a new workspace.

modules/get-started/pages/using-a-git-provider-access-token.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@
99

1010
pass:[<!-- vale RedHat.CaseSensitiveTerms = NO -->]
1111

12+
This page is for developers who create and use cloud development environments. To learn more about common roles and example tasks referenced in {prod-short} documentation, see xref:discover:roles-and-tasks.adoc[].
13+
1214
OAuth for GitHub, GitLab, Bitbucket, or Microsoft Azure Repos needs to be xref:administration-guide:configuring-oauth-for-git-providers.adoc[configured by the administrator] of your organization's {prod-short} instance. If your administrator could not configure it for {prod-short} users, the workaround is for you to use a personal access token. You can configure personal access tokens on the *User Preferences* page of your {prod-short} dashboard: `pass:c,a,q[{prod-url}]/dashboard/#/user-preferences?tab=personal-access-tokens`, or apply it manually as a {kubernetes} Secret in the namespace.
1315

1416
Mounting your access token as a Secret enables the {prod-short} Server to access the remote repository that is cloned during workspace creation, including access to the repository's `/.che` and `/.vscode` folders.

modules/get-started/pages/your-first-workspace.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@
99
[role="_abstract"]
1010
When you open the {prod-short} URL for the first time, you go from login to coding in about three minutes. The following sections cover the login flow, first workspace creation, workspace tools, and common errors.
1111

12+
This page is for developers who create and use cloud development environments. To learn more about common roles and example tasks referenced in {prod-short} documentation, see xref:discover:roles-and-tasks.adoc[].
13+
1214
== From URL to code in four steps
1315

1416
When your administrator shares the {prod-short} dashboard URL, you go from login to coding in four steps:

0 commit comments

Comments
 (0)