Need to add Optimism as a Network, filter, and icon first. Then add their Optimism address: https://ankarelief.org/

Display popular tweets for this cause and display a one-click-share tweet with the content we decide.

SOS Chain should be added for helping that relief effort. However, it'll be tricky.

SInce we don't list its addresses, it should be another type.

I suggest adding "sos_chain" type.
It should have a text like "Donate through their Avalanche dapp" and link to their webpage using the linkName and linkUrl parameters.

The "Other" filter should enable/disable this option and this will be tricky. Needs to be carefully developed, tested, and reviewed.

When applied filters remove some organizations, below the filters display a text in the following format:

Displaying 9 of 21 options

There're various glitchy use cases. Below is an example:

One solution I'd prefer is; when a url with query parameters is loaded, the url is cleared and the filters are saved in local storage (or the new alternatives). When refreshed, the filter state must persist.

Only when you click copy the filter, the filter query must be present.

1. The sort dropdown is commented out. Enable that to make sure it looks fine on screens as narrow as 375px (iPhone SE).
2. Add 2 options: "Suggested" (default), "Popular"

Suggested: The order of the array, which is the current implementation.
Popular: Sorted by the popularity parameters.

What about a button appears at the bottom of filters when filters are applied? A button that says:
"Copy URL for this filter"

Clicking that could copy a URL like the following:
https://turkiyereliefdao.com?cryptocurrencies=Polkadot

When such a URL is loaded, the query parameters must be deleted and the state better is persisted (#35) on page refreshes.

Another button next to it could say:
"Reset filter"

Advantage:

• Relevant subsets of options could be shared with networks, resulting in better targeting and conversion.

Disadvantages:
*Harder to implement than most of the other issues i.e. opportunity cost.

[1] Need to create persistent state management. Even more work. Could be delegated to another issue. The disadvantage of this

This's a donation organization card in the smallest supported view size of 375px (iPhone SE).

It should have a smaller margin in my opinion. I mean the margins around the card to the edges of the screen.

3 of the 4 stats here (except the magnitude) need to be updated.
Please suggest:

• A statistics
• Its description with bold word(s) in the beginning.
• Trusted resource link in English, strongly prefered without a paywall.

We've filters, great.

However, a user scrolling to that section, will unlikely click filter, if at all.

I think the experience on mobile views should be different.

1. The app could prompt how the user wants to donate.
2. Then it can list the options.

This way, the user would feel agency and already committed to donating at the time they click an option.

• https://twitter.com/houseofmat_/status/1623837198863720452
• https://forturkey.art

All of the entries in https://pro.btcturk.com/deprem-bagis like the example in AFAD.

I suggest the website loads like the image below for easier access to the functionality & better recognition of this feature.

https://giveth.io/project/gnosisdao-earthquake-relief
https://giveth.io/project/banklessdao-turkey-disaster-relief-fund

So that the filters won't be lost on page refreshes or going to another website and coming back. Use the simplest solution.

Source links are hidden on mobile section.
I'm on it.

source:
1- https://twitter.com/TheBullduck/status/1624389815016751105
2- https://donation.btcturk.com/

Brought by #47.

The filters must be applied first to avoid a glitchy experience and performance enhancement.

This is how the website works on mobile screens.

Reword all the linkNames, so that they all fit in this view (iPhone SE 375px width)

The relevant file: https://github.com/neu-fi/turkiye-relief-dao/blob/main/config/donations.ts

Add the new bridged L2 assets to Ahbap.

Sources

Arbitrum

• https://twitter.com/ConnextNetwork/status/1624413520258379776
• https://arbiscan.io/address/0x8888759373137b84e9f0ef13ecb13e321c251ee3#readContract

Optimism

• https://twitter.com/ConnextNetwork/status/1624413520258379776
• https://optimistic.etherscan.io/address/0x8888759373137b84e9f0ef13ecb13e321c251ee3#readContract

Add info: "Bridged through a trustless and audited contract"

A. https://www.paribu.com/#/afet-destek
B. https://www.paribu.com/blog/en/news/about-our-disaster-support-plan-and-the-cryptocurrency-donation-system/
C. https://earthquaketurkey.notion.site/Turkiye-Earthquake-Donations-330ba83b6a93442b92fd46a414a928db
D?

There're ideas for making the donation cards rounded and having different layouts.

They do not look clickable. Ideally, they are trailed with the open icon and underlined. Perhaps with dotted underlines.

Donations.tsx is currently 600 lines.

The logic and the components better are broken down into sub-components and hooks and helper functions

The filters have duplicated code for mobile and desktop views. They better share their code.

However, I don't know a good space to incllude these yet.

Some organizations have accounts with the same names such as "Tron" and "Tron" again. They do this for supporting multiple exchanges.

However, the state management mishandles these. It creates duplicates if you toogle cryptocurrencies.

Need to add Aptos as a Network, filter, and icon first. Then add 3+ Aptos addresses: https://www.paribu.com/blog/haberler/afet-destek-planimiz-ve-kripto-para-ile-bagis-organizasyonu-hakkinda/

https://twitter.com/TurkeyReliefDAO/status/1624051944632340486

The number of options in some of the organizations is close to 20.

We should design this experience, especially tailored towards mobile phones.

A few options:

1. The "donation types" and "cryptocurrency networks" filters could be opt-in, instead of opt-out.
2. Every organization could have up to 3 options marked as "featured", and the rest could be extended, or contracted.

We need design help on this issue.

Now that we've built the website quickly, we should enhance the performance by putting the images into the project.

The footer doesn't have gray-400 and hover:gray-500 colors and the dune icon is a little bit larger than the others.

We should sort the cryptocurrency addresses by their network. This way, we can display the addresses in a more organized way. New addresses must be ONLY appended to the options arrays to avoid conflicts and trust issues.

Here's the current look.

There's no use of the focus element, except accessibility. We do not support accessibility at the moment. I suggest we remove focus rings from these checkboxes.

Fix missing key prop errors.

1-)

2-)

Fix invalid DOM property

1-)

We need prettier configuration and Husky to perform "pnpm format". Using this convention will prevent formatting inconsistencies among the codebase and contributors.

To be designed by Damla.

The addresses should have blue pills just like the sources. They should be named "Explorer" and link to dynamically created explorer URLs.

The hero section and the rest of the texts should be edited.

Decouple the data from the components. Research the best practices for Next.js 13 file structure and data handling options, and TypeScript annotations.

Opening the filter panel has the following buggy scroll behavior:

The issues below are fixed with #68:

It's also missing feature parity with the desktop one:

• The first category is not expanded by default.
• When some organizations are filtered, the number indicator at the bottom is missing.

The last two issues better are resolved by reusing the code as a component. Contributors tend to omit to check the mobile view for them.

There could be a leaderboard of selected verified on-chain donations.

This idea got 4 🔥 emojis:

Pros:

• Incentivizing big donations
• Showing our gratitude

Cons:

• Development opportunity cost
• Distracting the attention of small donors from making donations