-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI/UX components #757
Comments
Can we move the |
yes we could actually use only /explore instead of having /search /tags |
#751 heres some HTML tags for accessibility |
" fetch more information on FAQ/about" what does this mean @crzypatchwork ? |
I would suggest us bringing informations about what is the project, informations about fees, about the smart contract addresses, as well some tools for devs/getting metadata |
Working on FAQ rn, can add popups in a seperate PR later. Will be active about this in #dev in the Discord. |
FAQ abandoned. Popups going stale... |
why FAQ abandoned? |
After the first two points I did on the FAQ, I realized that I'm not a good FAQ writer... we should probably get a copywriter or writer to write something up so that it sounds a bit better. Anywho, I've finished the new menu from hicathon, if you want to merge it it's over here |
Yep, I did write it but it seems I'm better with guidelines than I am with FAQ since I'm good at telling what to do/not do instead of how to do it. I could try again... may not be the same as the hicathon guidelines tho |
Do you want to implement the explore function by yourself or it's an open task to grab by anyone else still? |
sorry for the late response @denscimonk. the search feature is being implemented here https://github.com/hicetnunc2000/hicetnunc/tree/main/src/pages/search any suggestions are welcome |
@crzypatchwork Hi, I'm checking the explore function, these tags are the suggestions based on keywords you are trying to search? For now they are static seems: https://www.hicetnunc.xyz/search |
objkts
settings
minting
accessibility
The text was updated successfully, but these errors were encountered: