Closed benefacto closed 7 months ago
@benefacto As i've stated elsewhere I do not believe the subgraph is correctly configured
Hi @benefacto !
- It also looks like the Estimates are a bit off - for example the low end should be 48 hours (if I add up all of the low-end of your estimates).
Good catch, fixed it!
I believe this is complete. Please QA when you can @vldkhh
2 open issues to resolve before this scope is closed:
Business Description
The primary goal is to implement the profile interface for Stewards in the platform. This enhancement focuses on providing Stewards with a comprehensive view of their financial activities and contributions. By integrating key financial statistics into the profile page, we aim to offer Stewards a deeper insight into their impact and engagement within the platform.
Key Features and Benefits
Rich Profile Information: Incorporating elements like profile pictures (sourced from NFT images), names, and other relevant data, enriches the Steward's profile, making it more personalized and engaging.
Financial Activity Overview: The interface will display crucial financial metrics such as the number of collectives the Steward has received payments from, total actions performed, and cumulative amounts received. This provides Stewards with a clear and concise summary of their financial engagements.
Contribution Tracking: Stewards will be able to track their donations and the impact they have made. The profile will show the total amount donated and the number of collectives or individuals they have supported, highlighting their contribution to the community.
Data Accuracy and Integration: Ensuring the accuracy of the data displayed is paramount. This will involve integrating with the existing subgraph data structure efficiently.
Improved Engagement: By providing Stewards with detailed insights into their activities and contributions, we aim to enhance their engagement and satisfaction with the platform.
Expected Outcome:
Technical Implementation
Implement new profile interface for Stewards to display key financial statistics, leveraging data already available in the subgraph and contracts. This feature aims to provide Stewards with insightful and detailed information about their activities and contributions. This should be added to the
WalletProfilePage
here.Details
imageUrl
The URL of the NFT's image to display as a profile picturefirstName
Possibly from NFT metadatalastName
Possibly from NFT metadatacollectivesTotal
The number of collectives the steward has received payments from, something like:actionsPerformed
Display the total count of actions performed executed, something like:amountReceived
Present the cumulative amount paid out to said steward, something like:creationDate
When the profile was created. This might require a subgraph change as it's not present in the schema, currently.amountDonated
The amount the steward has donated, something like:peopleSupported
The number of collectives/stewards supported, something likecollectives
The collectives the steward has received payments from, something like:Notes
should be already availablemay not be already present in the subgraph (unknown modifications may be required); ensure proper querying and integration.Estimate
Estimating the time, especially considering potential unknown modifications to the subgraph, involves a degree of uncertainty.
Requirement Analysis and Planning (4-6 hours): Understanding the detailed requirements of the profile UI, including the financial statistics to be displayed, and assessing the subgraph's current configuration.
Subgraph Assessment and Modification (8-15 hours): If modifications to the subgraph are required (which seems likely based on comments), this could include analyzing the existing schema, implementing necessary changes, and testing these changes. The time could vary significantly based on the complexity of the required changes.
Implementation (20-30 hours):
Testing and Debugging (12-18 hours): Comprehensive testing to ensure data accuracy, responsiveness of the UI, and smooth integration with existing systems. This includes testing the new or modified subgraph integrations and ensuring the UI displays the data correctly.
Review and Refinement (4-6 hours): Addressing any feedback, and refining the feature as needed.
Adding these up, the total estimated time could be around 48-75 hours. This estimate assumes the developer is proficient in the relevant technologies and that there are no significant roadblocks or external dependencies that could delay the project.