Treasury Create Flow Improvements

[ori-near]

This ticket is to update some of the copy /UX on the Treasury Creation flow:

Confirm Wallet Screen (Step #1)

• Update copy to:

Confirm Your Wallet
This is the account that will be used to pay for creating the treasury and managing it initially. Ensure it has sufficient funds to cover the setup costs below.

Connected Wallet
This is your personal NEAR wallet used for setup. The treasury will have its own separate wallet.

Estimated One-Time Costs:
...
Continue

• Vertically align the user profile and username (e.g. I noticed that if user doesn't have a name it appear weird), hide the @ before the username, and increase font size slightly
• Make the continue button style and hover consistent with the next step

Current State:

Desired State:

Create Application Account (Step #2)

• Update copy to:

Create Treasury Accounts
Enter a name for your treasury. This will be used for both the application's URL and your treasury's Sputnik DAO account.

• Add input field label: Treasury Name
• Update input field placeholder text to: my-treasury (instead of app-account)
• Change tooltip for NEAR to: This NEAR account name will be used for the application’s URL and other management purposes, not the actual account where the funds will be held.
• Change tooltip for SputnikDAO Account: This is the name of your treasury's account on the Sputnik DAO platform, where your funds will be held.
• Change "Next" button to "Continue"
• Change warning message for already taken accounts from "Account near.near already been taken" to Account name already exists"
• If a user enters an account that is already taken (e.g. root) and then clears the form, the warning message should disappear

Current State:

Desired State:

Add Members (Step #3)

• Update copy to:

Add Members
Add members to your treasury and define their roles. You can also do this later.

• Under Account, vertically align the creator user profile and username

• Hide the @ before the username

• Creator should NOT be able to edit or delete themselves (e.g. remove pencil / trash actions) ... only subsequent users

• Change Permission Names (both in add members and edit members screens) from Create, Edit, Vote to: "Create Requests", "Manage Members", and "Vote" and ensure they map to the correct permissions (Update "Create requests" to "Create Requests" for consistency #283)

• Change "Next" button to "Continue"

Current State

Desired State

Summary (Step 4)

• Uppercase: Applicatiion Account Name
• Uppercase: Members and Permissions
• Ensure the permission labels match (e.g. Create Requests, Manage Members, Vote)

Other

• Uppercase button on top left: "Cancel Creation"

[ori-near]

@FREZZZBE FYI – I just tested the treasury creation flow and found a few issues (added in ticket above). I had a few thoughts I wanted to discuss with you. Can we discuss these in our 1:1 on Monday?

1. I noticed that the implementation didn't match your UX designs fully.

For example, in your designs you had two separate steps for creating application account and Sputnik DAO account:

But the implementation condensed those to two steps. I provided my solution above ... but want to make sure it's clear to you and see if you find anything else.

2. It seems like the buttons/hover are a bit inconsistent throughout the flow. From the back/next/continue to the add members, etc.

3. For adding members, I think we need to do a better job of explaining the permissions.