daostack / daostack/common

Proposal Page re-structure [S13-01]

Open
#1,353 0 comments 0 reactions 0 assignees View on GitHub
need design
Dominant language
TypeScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

proposal page will include all information exists in its card in the full view (large chart)

plus

1. Menu (for mobile - bottom menu, for mobile )
1. Proposal
2. Discussion

Note: we should remove the inner menu in the proposal and get rid of the confusing animation

**Proposal Tab**

1. Status, i.e. -
1. Discussion + Countdown: Time left (i.e. 24:10:12, format: HH:MM:SS)
2. Voting + Countdown: Time left (i.e. 24:10:12, format: HH:MM:SS)
[Either discussions or voting countdown are active, not both]
3. Rejected
4. Approved
5. Withdrawn
6. Expired (if the money was not transferred for some reason)
2. **Type of Proposal (i.e., Funds Allocation, Funds Request, etc.)**
3. **Proposal Title**
4. Date (when active - ”X hours/days ago”, after proposal ends - end of proposal date)
5. Proposer
1. Proposer user name
2. Proposer Profile picture
6. Voting Chart (i.e. 42% support, 17% Object, 16% Abstain)
7. Number of voters + **Link to list of voters** (web: pop-up, mobile: inner page) divided to
1. All
2. Approved
3. Abstain
4. Object
8. **Indication whether the voting is fulfilling the conditions:**
1. **Quorum** (percentage of the voters from the numbers of members with voting rights should be greater than the minimum defined for this type of proposals) [could be 0%]
2. **Minimum support** (percentage of the approving votes from the total votes should be greater than the minimum defined for this type of proposals) [could be 0%]
3. **Maximum object** (percentage of the objecting votes from the total votes should be smaller than the maximum defined for this type of proposals)
9. Member’s vote profile picture + vote icon (i.e. support)
10. **Unique details for each type of proposal:**
1. Funds allocation (taken from proposal creation):
1. Type of funds
2. sum of money for pay-out (i.e., 500 NIS)
3. Recipients (type and name or list)
4. Recurring (single, monthly etc.)
5. Net+ (Immediately, in x days, etc.)
2. Funds request:
1. Recurring indication: i.e., “Single” / “Monthly”
2. Sum of money for pay-in
3. Target recipients circles
3. Assign circle:
1. Name of member
2. Circle to be assigned to
4. De-assign circle:
1. Name of member
2. Circle to be de-assigned from

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the proposal page and proposal card entry points; no files or tests are named in the issue. Compare the existing card and full-view behavior with the requested Proposal and Discussion navigation, status countdowns, voting details, and proposal-type fields. Done means the full proposal view presents the specified information and mobile and desktop navigation without the confusing inner menu or animation.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.