\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)",[2068,2069,2071,2074],{"name":2008,"color":1986},{"name":2070,"color":1989},"A-landing",{"name":2072,"color":2073},"chief","67EA1F",{"name":1991,"color":1992},3844,"Redesign Landing page","2022-10-19T15:38:37Z","https://github.com/kodadot/nft-gallery/issues/3844",0.73071474,{"description":2081,"labels":2082,"number":2087,"owner":1994,"repository":1995,"state":1996,"title":2088,"updated_at":2089,"url":2090,"score":2091},"\n\n\n-----\n\n\u003Cimg src=https://github.com/user-attachments/assets/4d6565a3-2346-4d3b-8fe9-3343f72063d9 width=400 />\n\n",[2083,2084,2086],{"name":2005,"color":2006},{"name":2085,"color":1986},"p3",{"name":1988,"color":1989},11536,"Item Explorer Price filter & Navbar broken styles","2025-04-15T11:27:57Z","https://github.com/kodadot/nft-gallery/issues/11536",0.73118216,{"description":2093,"labels":2094,"number":2102,"owner":1994,"repository":1995,"state":1996,"title":2103,"updated_at":2104,"url":2105,"score":2106},"Based on the discussion from #2511 \r\n\r\nFor the sake and easier maintenance would be superior nice to have merged explorer and collections, so we don't need to maintain these two components as extra. It would simplify architecture in @petersopko words, which I can agree, keep it simple stupid.\r\n\r\nThe flow would look like when a user searches for \"something\" it can drive it to tabs, where the first highlighted tab could be collectables, other items and once we will have #2112 we can add that one as well \r\n\r\n> we could merge the Gallery + Collections under one tab in the navbar (Explore) and have it separated by tabs within the search section\r\n\r\n\r\n\r\n> As still, we haven't thought what merger of explore+collections feed would look like I'm open to new ideas and sense this is the time",[2095,2097,2100,2101],{"name":2096,"color":2020},"$$",{"name":2098,"color":2099},"redesign-seeds","053A03",{"name":2008,"color":1986},{"name":1988,"color":1989},2719,"Unification explorer + collections into one ","2022-04-12T09:44:05Z","https://github.com/kodadot/nft-gallery/issues/2719",0.73482823,{"description":2108,"labels":2109,"number":2115,"owner":1994,"repository":1995,"state":1996,"title":2116,"updated_at":2117,"url":2118,"score":2119},"\r\n\r\n### What happened?\r\n\r\n\r\n\r\n\r\n\r\n",[2110,2111,2112,2114],{"name":2005,"color":2006},{"name":2035,"color":2036},{"name":2113,"color":1989},"A-search",{"name":1988,"color":1989},10930,"Navbar collection search not working","2024-09-11T04:53:36Z","https://github.com/kodadot/nft-gallery/issues/10930",0.7400339,["Reactive",2121],{},["Set"],["ShallowReactive",2124],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"yUtSh85qa2AWYqAfZaor-PJ9wJ3hNjULp95dlLzf8uM":-1},"/kodadot/nft-gallery/4684"]