Gating | Create + Edit Group page

[zakhap]

Description

This form page is used both for creating and editing Groups information.

Requires: Groups API

DevLinks: https://www.figma.com/file/ePuGFatYQI6GL72i27sVwj/Gating?type=design&node-id=3-38&mode=design&t=YotqyxzZxIGCRSuK-0

Acceptance Criteria

Behaviors:

• Page has 2 modes, “create” + “edit”
  • “create”: for New Groups, no information filled out.
  • “edit”: requires an existing Group’s information + should pre-populate all fields. All information can be edited, including the adding, removal, and editing of Requirements. Pre-populating may be non-trivial for Requirements.
• Depending on the “Community’s Ecosystem” / “Community Type” / “Base”, different Requirements will be shown as options within the dropdown. For example, the “Cosmos Base Token” Requirement does not need to be shown to “Ethereum” Communities.
• Create Groups Form Page designs as provided in the Figma DevLink should be implemented to specification
• This is an admin-only page.
• There is a delete button for the entire Group. => opens confirmation modal (see devlink)

URLS:

• /scope/members/groups/create
• /scope/members/groups/edit

Additional context

[jnaviask]

@zakhap @jessmart1213 I suggest adding a big warning box of some sort to say that current group members will be cleared if requirements are edited for a group. This is because changing requirements mean we no longer know if an address which previously passed the set of requirements still passes given the new requirements, and also because we don't check all members upfront -- only when they visit the site. So, changing requirements clears the group.

[mzparacha]

Update the point label since it involves some more components to be created

[jnaviask]

@mzparacha let's make sure we get this page behind a feature flag so we can merge it while we work on the rest of the pages.

[mzparacha]

sure, sounds good @jnaviask

Just to confirm if we follow/use any labels for that?