Skip to content

Add Giveth Dapp project-management user flows documentation#5502

Draft
alireza-sharifpour wants to merge 1 commit intomainfrom
codex/document-user-flows-for-project-management
Draft

Add Giveth Dapp project-management user flows documentation#5502
alireza-sharifpour wants to merge 1 commit intomainfrom
codex/document-user-flows-for-project-management

Conversation

@alireza-sharifpour
Copy link
Copy Markdown
Member

Motivation

  • Provide a single-source, product-style frontend UX reference that captures how the Giveth Dapp currently implements project-management workflows and edge cases.
  • Make it easier for engineers and designers to reason about routes, modal flows, validation, and ownership/access guards during feature work and QA.

Description

  • Add a new documentation file docs/giveth-dapp-project-management-user-flows.md that enumerates nine project-management experiences including Create Project, My Projects dashboard, Edit Project, Manage Recipient Addresses, Activate/Deactivate Project, Verification, and project update flows.
  • The document describes primary routes (for example /create and /verification/[slug]), happy-path steps, edge cases, validation rules, modal behaviors, local-storage resume semantics, and shared cross-flow product notes about access and optimistic vs refetch update patterns.

Testing

  • No automated tests were run for this docs-only change.

Codex Task

@vercel
Copy link
Copy Markdown

vercel bot commented Mar 18, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
giveth-dapps-v2 Ready Ready Preview, Comment Mar 18, 2026 9:50am

Request Review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c04d5105eb

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +256 to +260
- **Verification action hidden or disabled:** verification entry points are not always available. The action may be unavailable when:
- the project is already GIVbacks eligible,
- verification was already submitted,
- verification was rejected,
- the project is not active.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Remove the inactive-project restriction from dashboard verify flow

This bullet says the verify/resume entry point is unavailable when the project is not active, but the My Projects dropdown does not check project.status.name before adding that option. In src/components/views/userProfile/projectsTab/ProjectActions.tsx, any non-cause project with no verification status or a DRAFT form and !project.isGivbackEligible still gets the Verify/Resume action, so deactivated projects continue to show the entry and only get blocked after navigation.

Useful? React with 👍 / 👎.

Comment on lines +45 to +48
10. On success:
- a preview/draft flow routes to the project page,
- a publish flow routes to the success page,
- local storage is cleared for a successful new-project completion.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Document the publish redirect used with recurring setup

The create-flow happy path currently implies every publish ends on the success page, but src/components/views/create/CreateProject.tsx has a separate branch for new projects with an Allo/recurring-donation registry: after saving the anchor contract it clears local storage and pushes directly to slugToProjectView(...). On Base/Optimism, readers following this document will therefore test the wrong post-publish destination.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant