Skip to content
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

Replace /workspaces → /projects as default landing page for both users and teams #6048

Merged
merged 2 commits into from
Oct 25, 2021

Conversation

jankeromnes
Copy link
Contributor

@jankeromnes jankeromnes commented Oct 5, 2021

Description

Related Issue(s)

Fixes #5050

How to test

  1. Visiting the dashboard should open the Projects page by default
  2. Switching to a team should open the Projects page by default

Release Notes

Replace /workspaces → /projects as default landing page for both users and teams

@jankeromnes
Copy link
Contributor Author

/approve

@gtsiolis
Copy link
Contributor

gtsiolis commented Oct 5, 2021

Looking at this ...when the build is finished! 👀

@gtsiolis gtsiolis added component: dashboard feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code user experience labels Oct 5, 2021
@jankeromnes
Copy link
Contributor Author

jankeromnes commented Oct 5, 2021

Thanks @gtsiolis!

I feel like the Projects page is missing some New Workspace buttons (or at least context menu option) to make it a great default landing page.

Currently, with this PR, the "shortest path to a workspace" is:

  1. Load Projects page
  2. Open Branches overview (and wait for half an eternity)
  3. Click on New Workspace

@jankeromnes
Copy link
Contributor Author

See also: #6047 (comment) (possibly related to this change)

@jankeromnes
Copy link
Contributor Author

jankeromnes commented Oct 6, 2021

Added a drive-by change: A New Workspace context menu option for all Projects cards.

Screenshot 2021-10-06 at 11 28 19

EDIT: Spliced this commit out into its own PR: #6185

@jankeromnes jankeromnes force-pushed the jx/projects-default-page branch 2 times, most recently from 36ff5e3 to f74bb72 Compare October 6, 2021 09:28
@jankeromnes jankeromnes removed the request for review from aledbf October 7, 2021 17:14
@jankeromnes
Copy link
Contributor Author

jankeromnes commented Oct 11, 2021

Still waiting for a review! 😊 🙏

/werft run

👍 started the job as gitpod-build-jx-projects-default-page.5

@laushinka
Copy link
Contributor

Thanks for this PR!
/lgtm

@roboquat
Copy link
Contributor

LGTM label has been added.

Git tree hash: d3412d2917956887e600fa9e04d78dfb26f6a610

Copy link
Contributor

@gtsiolis gtsiolis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had a draft review that I never submitted here. 😭

Thanks for the reminder, @jankeromnes! ⏰

thought(non-blocking): Overall, looks great and into the right direction. However, posting here for visibility that this change would change the existing onboarding flow and could slightly affect usage.

Approving to unblock merging but holding while @laushinka also looks at this[1]. 👀

/hold

@@ -395,7 +395,7 @@ export async function deployToDev(deploymentConfig: DeploymentConfig, workspaceF
werft.fail('deploy', err);
} finally {
// produce the result independently of Helm succeding, so that in case Helm fails we still have the URL.
exec(`werft log result -d "dev installation" -c github-check-preview-env url ${url}/workspaces/`);
exec(`werft log result -d "dev installation" -c github-check-preview-env url ${url}/projects`);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

praise: Nice one! 💯

@@ -395,7 +395,7 @@ export async function deployToDev(deploymentConfig: DeploymentConfig, workspaceF
werft.fail('deploy', err);
} finally {
// produce the result independently of Helm succeding, so that in case Helm fails we still have the URL.
exec(`werft log result -d "dev installation" -c github-check-preview-env url ${url}/workspaces/`);
exec(`werft log result -d "dev installation" -c github-check-preview-env url ${url}/projects`);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: Probably going with / this could also work, right?

customFontStyle: 'text-red-600 dark:text-red-400 hover:text-red-800 dark:hover:text-red-300',
onClick: () => onRemoveProject(p)
}]} />
<ContextMenu menuEntries={[
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue: This is out of the scope of these changes but do you think it'd be easy to add a hover state on the more action button as seen everywhere else?

Adding hover:bg-gray-200 dark:hover:bg-gray-700 rounded-md in the Context Menu component could suffice unless I'm missing something. What do you think? Feel free to open a follow up PR if needed.

const children = props.children || <svg className="w-8 h-8 p-1 text-gray-600 dark:text-gray-300" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><title>Actions</title><g fill="currentColor" transform="rotate(90 12 12)"><circle cx="1" cy="1" r="2" transform="translate(5 11)" /><circle cx="1" cy="1" r="2" transform="translate(11 11)" /><circle cx="1" cy="1" r="2" transform="translate(17 11)" /></g></svg>;

Copy link
Contributor Author

@jankeromnes jankeromnes Oct 13, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! Pushed a new drive-by commit to fix this. 🚀

EDIT: In #6185, that is.

}]} />
<ContextMenu menuEntries={[
{
title: "New Workspace",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

praise: YES!

@roboquat
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gtsiolis, jankeromnes, laushinka

Associated issue: #5050

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@laushinka
Copy link
Contributor

If I've added an lgtm, do I also have to add an approve tag?

@jankeromnes
Copy link
Contributor Author

jankeromnes commented Oct 11, 2021

If I've added an lgtm, do I also have to add an approve tag?

@laushinka no need 🙂 you can see in @roboquat's comment above that your "lgtm" also counted as an "approve":

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gtsiolis, jankeromnes, laushinka

If you're wondering why this PR isn't merged, that's because of the "do-not-merge/hold" label.

Before we remove that and merge this PR, I think we need more buy-in for the new default location, especially from product.

Relatedly, what do you think of this @jldec?

@jldec
Copy link
Contributor

jldec commented Oct 12, 2021

If this will make the "new project" onboarding flow the default first experience for new users, I would recommend holding this for now.

I think the new project flow is still a bit long and can be difficult to understand in places, especially for noobs like myself. See screenshots (internal only)

@stale
Copy link

stale bot commented Oct 23, 2021

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Oct 23, 2021
@jldec jldec added meta: never-stale This issue can never become stale and removed meta: stale This issue/PR is stale and will be closed soon labels Oct 25, 2021
@jldec
Copy link
Contributor

jldec commented Oct 25, 2021

I think we should move forward with this.

/unhold

@roboquat roboquat merged commit 8e9f612 into main Oct 25, 2021
@roboquat roboquat deleted the jx/projects-default-page branch October 25, 2021 09:14
@roboquat roboquat added deployed: webapp Meta team change is running in production deployed Change is completely running in production labels Oct 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved component: dashboard deployed: webapp Meta team change is running in production deployed Change is completely running in production feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. meta: never-stale This issue can never become stale release-note size/M team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code user experience
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Change default page to projects for personal accounts and teams
5 participants