-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
RHDEVDOCS-3866 Merging the accessing perspectives sections #52924
Conversation
a236685
to
17fa090
Compare
🤖 Updated build preview is available at: Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/4362 |
@@ -27,3 +27,8 @@ The *Developer* perspective provides workflows specific to developer use cases, | |||
* Group components within an application and connect the components within and across applications. | |||
* Integrate serverless capabilities (Technology Preview). | |||
* Create workspaces to edit your application code using Eclipse Che. | |||
|
|||
You can use the *Topology* view to display the list of all the projects in your cluster. If you have no workloads or applications in the project, the *Topology* view displays the available options to create applications. If you have existing workloads, the *Topology* view graphically displays your workload nodes. |
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.
You can use the *Topology* view to display the list of all the projects in your cluster
this doesn't seem very right, topology view is meant to list all the applications/workloads
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.
@invincibleJai, this section's content is not created but only moved from Accessing the Developer Perspective to About Developer Perspective. Are you sure if you want to change this? If yes, I can rephrase the first line.
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.
@shreyasiddhartha can you point me to that?
as in this PR i see the reference of topology here which has been removed and here it makes sense as context is changed https://github.com/openshift/openshift-docs/pull/52924/files#diff-c2da23386f560a8b8887b75439ea41c909b6963a8115932738a09ec1c48794ecL18-L25
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.
Agree with Jai, also if its moved we should improve this anyway. The topology view is about showing workloads.
You want to change the first sentence to
You can use the *Topology* view to display the list of all the projects in your cluster. If you have no workloads or applications in the project, the *Topology* view displays the available options to create applications. If you have existing workloads, the *Topology* view graphically displays your workload nodes. | |
You can use the *Topology* view to display applications, components and workloads of your project. If you have no workloads in the project, the *Topology* view will show some links to create or import them. You can also use the *Quick Search* to import components directly. |
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.
yeah above suggestion looks good technically and depending on the context can add if no namespace/project is selected and the user goes to the developer perspective then the topology view shows the list of namespaces/projects if any exist.
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.
Thanks @jerolimov. The above suggestion looks good to me as well. I'm adding an additional serial comma before "and" in the suggested changes.
You can access the *Administrator* and *Developer* perspective from the web console as follows: | ||
|
||
.Prerequisites | ||
To access a perspective, ensure that you have logged in to the web console. Your default perspective is determined by your role. |
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.
not sure if we need to get into details of what these role is
@jerolimov WDYT?
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.
Yeah this might be interesting to some users, we've got this question also in the past from associates who uses the web console UI less often.
Maybe like this:
To access a perspective, ensure that you have logged in to the web console. Your default perspective is determined by your role. | |
To access a perspective, ensure that you have logged in to the web console. Your default perspective is automatically determined by the permission of the users. The *Administrator* perspective is selected for users with access to all projects, while the *Developer* perspective is selected for users with limited access to just their own projects. |
Wdyt @invincibleJai and @shreyasiddhartha ?
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.
Thanks @jerolimov , this looks better IMO
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.
Thank you @jerolimov. Additionally I'm removing "just" from from the suggested changes.
/cc @jerolimov |
|
||
. Use the perspective switcher to switch to the *Administrator* or *Developer* perspective. | ||
|
||
. Select an existing project from the list or use the *Project* drop-down list to create a new 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.
I don't understand what "from the list" means here. Esp. new users without access to any project (that is a common case!) will not have such a list. I want to suggest to focus here on the project dropdown:
. Select an existing project from the list or use the *Project* drop-down list to create a new project. | |
. Select an existing project from the *Project* drop-down list. You can also create a new project from this dropdown. |
Added some comments/recommendations to align the doc a little bit more for users that will use the Developer perspective the first time. This first usage experience might have changed in the Developer perspective over the last releases, step by step. Sanket will be the right person to give lgtm from the QE perspective. |
17fa090
to
53d616e
Compare
LGTM |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
RHDEVDOCS-3866: Doc updates-Update Developer Perspective content based on recognized user/Merging the accessing perspectives sections
OpenShift 4.11 Freeze
JIRA issues: RHDEVDOCS-3866
SME Review: @jerolimov
QE Review: @sanketpathak