\r\n\r\n## Figma export \r\n- [Readme](https://www.figma.com/file/3iOjW12ERFRDSVnpLuhQmf/landing-page-handoff?node-id=1305%3A5612) \r\n- [Design](https://www.figma.com/file/3iOjW12ERFRDSVnpLuhQmf/landing-page-handoff?node-id=798%3A3662)\r\n- [Components + Prototypes](https://www.figma.com/file/3iOjW12ERFRDSVnpLuhQmf/landing-page-handoff?node-id=1305%3A5613)\r\n\r\n\r\n\r\n## Navbar \r\nNavbar will be functioning most likely nowadays, with some refreshment.\r\n\r\n### From left to right\r\n- There will be a logo which takes you back home `/`.\r\n- Search in the navbar, which will appear once you scroll the site.\r\n- Explore, which will take you to global explorer -- I guess we don't have this one, so most likely skip it for now \r\n- Stats - Rankings like series \r\n- Connect -- this will stay the current one. Hopefully, it's already made as a component (?)\r\n\r\n## Search\r\nWe will have a multi-chain search including RMRK, Basilisk and other upcoming implementations.\r\nMultichain search will support [^supportedchain]\r\nThe search bar could be selected when pressing 'K' \r\nOn input focus, it will show trending collections\r\nthose trending collections could be fetched by default by most volume or most of buys per 7 days with the option to overwrite/add extra collections to list\r\nUnder search, we can show currently working chains , along with upcoming integrations [^chains]\r\nEach chain name would be linked to a particular explorer feed based on that chain. I.e. RMRK -> `/rmrk/explore`\r\n\r\nThe same search bar would go to the navbar once the user scrolls down\r\nThe majority of search is being done in \r\n- #3763 \r\n- #3360\r\n\r\n## Spotlight \r\n\r\nThis section would be a remake of our existing carousel component. The component will be still and without auto-play. \r\nOn this component, we will be showing collections from all chains. So having array with chain and address collection would be mandatory here. \r\nAs you see, we will be showing picture of collection with collection name. The link will take user to the collection view.\r\nThe spotlight will be horizontally scrollable, with at least 15 collection. \r\nThis feed will be a curated list by community picks. \r\n\r\nSome work is being done here\r\n- #3772 \r\n- #876\r\n\r\n## Top collections\r\nThe collection would receive a new look and feel. \r\nMost data are already done in the series insights component, so expanding here should be a breeze. \r\nThe new functionality will be there, showing 24 hours, 7 days and 30 days time frame of data.\r\nDefault selected time frame should be 7 days.\r\nOn the upper right, \"All\" would change collection data based on supported chains: [^supportedchain]. \r\n\r\n### Data\r\n- name of collection\r\n- floor of the collection \r\n- total volume of collection in native token per selected period\r\n- total volume of collection in USD per selected period\r\n- difference within the selected period\r\n\r\nLink will take the user to the collection view.\r\n\r\nSome part of preparation is upcoming in this issue.\r\n\r\n- #3869 \r\n\r\n## New Listings\r\nThis section would work same as current listings. \r\nThe major difference is that we will pool data from various indexers into one component. \r\nWe will be showing user on which chain listing happened, like [^supportedchain] .\r\n\r\n### Data\r\n- NFT name\r\n- Collection name\r\n- Listing price \r\n- Supported chains: [^supportedchain]\r\n\r\n## Latest Sales \r\nThis section would work same as current sales. \r\nThe major difference is that we will pool data from various indexers into one component. \r\nWe will be showing user on which chain sale happened, like supported chains: [^supportedchain] .\r\n\r\n### Data\r\n- NFT name\r\n- Collection name\r\n- Sale price (the last buy happened)\r\n- Supported chains: [^supportedchain]\r\n\r\n## Featured Articles\r\nWe will have a list of articles, for now, three without scroll. \r\n\r\n### Data\r\n- hero picture for the article \r\n- Article title\r\n- Short description\r\n- Link to an article\r\n\r\nMore articles can go to either to Medium or Substack publications, whichever we will decide for \r\n\r\n## Footer \r\nHere we will collect email address into our Substack. \r\nLink Substack of our Kodadot publication, can drop code for button\r\nOther links are to\r\n- FAQ -> https://kodadot.xyz/rmrk/faq -> probably we should move FAQ to root, like https://kodadot.xyz/faq \r\n- Grants -> link to current grants form \r\n- Documentation -> https://docs.kodadot.xyz/\r\n- Contribute -> https://kodadot.xyz/contribute\r\n#### Socials \r\n- Twitter -> https://twitter.com/kodadot\r\n- Instagram -> https://instagram/kodadot.xyz\r\n- Discord -> https://discord.gg/u6ymnbz4PR \r\n- Youtube \r\n- Telegram \r\n\r\n## Legend\r\n\r\n- https://github.com/kodadot/nft-gallery/issues/2792\r\n\r\n[^chains]: Currently supported chains are RMRKv1 and Basilisk Rococo. Upcoming integrated chains will be MoonRiver, MoonBeam and Astar(RMRK) \r\n\r\n[^supportedchain]: RMRK 1.0, Basilisk\r\n\r\n### Currently working chains\r\n- RMRKv1 \r\n- Basilisk Rococo\r\n### Upcoming working chains\r\n- MoonRiver\r\n- MoonBeam\r\n- Astar (RMRK)",[2042,2043,2045,2048],{"name":2025,"color":1989},{"name":2044,"color":1992},"A-landing",{"name":2046,"color":2047},"chief","67EA1F",{"name":2049,"color":2050},"redesign","227120",3844,"Redesign Landing page","2022-10-19T15:38:37Z","https://github.com/kodadot/nft-gallery/issues/3844",0.71824425,{"description":2057,"labels":2058,"number":2062,"owner":1999,"repository":2000,"state":2015,"title":2063,"updated_at":2064,"url":2065,"score":2066},"Seems Create and Stats are not on hover and should be on hover?\r\nPlus seems after clicking, it stays open. Is that intentional? I guess we should not have it there?\r\nRefactoring of this component would be welcome I guess :)\r\n\r\nhttps://user-images.githubusercontent.com/5887929/205489345-5bc3b05e-9214-4111-81df-cdf5cfea1d26.mov\r\n\r\nhttps://user-images.githubusercontent.com/5887929/205489443-57b1d6fc-774e-41b5-8f25-ae861f08179d.mov\r\n\r\n",[2059,2060,2061],{"name":2010,"color":1986},{"name":1988,"color":1989},{"name":2013,"color":1992},4443,"Navbar smol hover fixes ","2022-12-11T20:09:19Z","https://github.com/kodadot/nft-gallery/issues/4443",0.71895,{"description":2068,"labels":2069,"number":2072,"owner":1999,"repository":2000,"state":2015,"title":2073,"updated_at":2074,"url":2075,"score":2076},"It seems to me that redesign info / issues are scattered on too many places with too much text, let's have one simple issue for tracking what's currently happening. I'll keep this updated.\r\n\r\nRelated discussion:\r\n- [ ] #3710\r\n\r\nLanding:\r\n\r\n- [x] #3844\r\n- [x] #3944\r\n- [x] #3945\r\n - [x] #3947 \r\n - [x] #3928\r\n\r\nNavbar and Footer (should be across whole app, not just landing):\r\n- [x] #3946\r\n- [x] #3948\r\n\r\nOld redesign ideas are tracked here:\r\n- [ ] #3956",[2070,2071],{"name":2046,"color":2047},{"name":2049,"color":2050},3950,"Redesign: Neobrutalism","2023-10-16T12:14:49Z","https://github.com/kodadot/nft-gallery/issues/3950",0.7246853,{"description":2078,"labels":2079,"number":2082,"owner":1999,"repository":2000,"state":2015,"title":2083,"updated_at":2084,"url":2085,"score":2086},"I noticed a few inconsistencies, so tried to name them down. \r\nWould be nice if we can have it merged with #2791 so we can push to production and make probably a release.\r\n\r\nIn the actions component, make borders top-border only and 1px, including input.\r\nThinking for Buy we could also try to have just top-border.\r\n\r\n\r\n\r\nSearch bar on input make top-border 1px, now it seems is 2px \r\n\r\n\r\nIn the profile dropdown, the logout button needs top-border 1px love\r\n\r\n\r\n\r\nOn the item detail, the control buttons remove top-border\r\n\r\n\r\n\r\non left and right arrow - top-border 1px \r\n\r\n\r\n\r\nLet's make Action, Chart, History top-border 1px as well \r\n\r\n\r\n\r\n\r\n\r\nEmoji button as well 1px \r\n\r\n\r\n",[2080,2081],{"name":2010,"color":1986},{"name":2025,"color":1989},2806,"Match top-border style where we miss it","2022-04-09T10:03:09Z","https://github.com/kodadot/nft-gallery/issues/2806",0.72480214,{"description":2088,"labels":2089,"number":2093,"owner":1999,"repository":2000,"state":2015,"title":2094,"updated_at":2095,"url":2096,"score":2097},"Right now, the user needs to precisely hit the icon on kodadot.\r\nTo make this easier, let's make this space wider around the icon, at least 20px on each side.\r\nFrom top and bottom make it the same as rest buttons in navbar\r\n\r\nht @vlad \r\n \r\nhttps://user-images.githubusercontent.com/5887929/201425210-ec580f66-8b23-4df5-a913-4f585d120015.mov\r\n\r\n",[2090,2091,2092],{"name":2010,"color":1986},{"name":1988,"color":1989},{"name":2013,"color":1992},4306,"Wider actionable space for buttons in navbar","2022-11-16T13:00:56Z","https://github.com/kodadot/nft-gallery/issues/4306",0.72586393,{"description":2099,"labels":2100,"number":2107,"owner":1999,"repository":2000,"state":2015,"title":2108,"updated_at":2109,"url":2110,"score":2111},"Whenever someone is browsing \r\n- collection\r\n- profile\r\n- item\r\n\r\nIt's not needed to show them buttons like Create, Explore, Stats, chain, Language and would rather strip it as probably don't use it all. \r\n \r\nInstead would be nice to show on that place name of \r\n- collection\r\n- artist \r\n- title of nft item\r\n\r\nSo desired results would be once user scrolls down, fading away buttons and replace it with text. \r\nIf it's long, strip it from end, as in case of similar named collection, higher chance number will be on the end of collection.\r\n\r\n\u003Cimg width=\"1386\" alt=\"image\" src=\"https://user-images.githubusercontent.com/5887929/158192385-89cf3e9a-ed8e-449d-9852-c4120e0c429c.png\">\r\n\r\nThe best inspiration is at how the GitHub app on mobile works. Best check video and how navbar behaves there\r\n\r\nhttps://user-images.githubusercontent.com/5887929/158193913-060d8711-2bbb-4572-8c98-0a962a1ecc5f.mp4\r\n\r\nPlus on the desktop looks like this (tbh haven't noticed till noticed, pretty used for it like it's been there forever)\r\n\r\nhttps://user-images.githubusercontent.com/5887929/158206518-e3f09ea1-89b5-4fa3-937e-835430976ecb.mov\r\n\r\n",[2101,2104,2105,2106],{"name":2102,"color":2103},"UX first","7057ff",{"name":2010,"color":1986},{"name":1988,"color":1989},{"name":2013,"color":1992},2540,"Showing context of page in navbar","2022-03-17T11:02:16Z","https://github.com/kodadot/nft-gallery/issues/2540",0.73249537,{"description":2113,"labels":2114,"number":2120,"owner":1999,"repository":2000,"state":2015,"title":2121,"updated_at":2122,"url":2123,"score":2124},"The functionality of navbarV2 on mobile is already as same as that on pc. However, there still more need to be done on mobile according to the redesign Figma. \r\nBecause UI structure and interaction are quite different from pc, we should implement a new component `MobileNavbarDropdown` according to `Navbar` component.\r\n\r\n\r\nnow:\r\n\u003Cimg width=\"309\" alt=\"image\" src=\"https://user-images.githubusercontent.com/31397967/196070205-b44c2d40-488f-4386-94af-38fe8ecd828a.png\">\r\n\r\nfigma: https://www.figma.com/file/3iOjW12ERFRDSVnpLuhQmf/landing-page-handoff?node-id=0%3A1\r\n\u003Cimg width=\"734\" alt=\"image\" src=\"https://user-images.githubusercontent.com/31397967/196070774-2a83c3d9-8a14-4cd6-84ed-62f938be7ea9.png\">\r\n\r\n## Ref\r\n- #4196 \r\n\r\n_Originally posted by @Jarsen136 in https://github.com/kodadot/nft-gallery/issues/4063#issuecomment-1280153177_\r\n ",[2115,2116,2117,2119],{"name":1985,"color":1986},{"name":2025,"color":1989},{"name":2118,"color":1992},"A-mobile",{"name":2049,"color":2050},4125,"redesign neobrutalism of navbarV2 on mobile","2022-12-16T13:18:21Z","https://github.com/kodadot/nft-gallery/issues/4125",0.73698807,["Reactive",2126],{},["Set"],["ShallowReactive",2129],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"mCnpgrUCRJHS5vHYNZ6YnWEuopt-TAI8IUebBiCgOlM":-1},"/kodadot/nft-gallery/2770"]