\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)",[2053,2054,2056,2059],{"name":2025,"color":2012},{"name":2055,"color":1992},"A-landing",{"name":2057,"color":2058},"chief","67EA1F",{"name":2060,"color":2061},"redesign","227120",3844,"Redesign Landing page","2022-10-19T15:38:37Z","https://github.com/kodadot/nft-gallery/issues/3844",0.7595291,{"description":2068,"labels":2069,"number":2074,"owner":1997,"repository":1998,"state":1999,"title":2075,"updated_at":2076,"url":2077,"score":2078},"Seems the history component table needs to be chain agnostic and point to BSX when the user is selected on BSX\r\n\r\n\u003Cimg width=\"1020\" alt=\"image\" src=\"https://user-images.githubusercontent.com/5887929/174489582-a5fa3b75-ecbc-4135-b1da-ba09965c8d5d.png\">\r\n",[2070,2071,2072,2073],{"name":2040,"color":2041},{"name":2008,"color":2009},{"name":2025,"color":2012},{"name":1991,"color":1992},3200,"Collection History charts points to RMRK","2022-06-20T09:10:49Z","https://github.com/kodadot/nft-gallery/issues/3200",0.76586586,{"description":2080,"labels":2081,"number":2089,"owner":1997,"repository":1998,"state":1999,"title":2090,"updated_at":2091,"url":2092,"score":2093},"We have an issue that when the user fresh mints a new collection, BSX has 12 second block time and Kusama has 6 seconds. So it takes longer to finalise on chain on Basilisk itself and another round trip to fetch data on our indexer and then once client can fetch it and see in their browser, which results in an approximate 30-60 seconds delay till the user can select it as a collection in the select box. \r\n\r\nThe goal is to explain to the user why need to wait so long, till we roll out some more complex fix on this. \r\n\r\nAdd explainer under collection I would suggest something along these lines in some information box. \r\n\r\nFeel free to propose a more entertaining explainer 👀\r\n\r\n\u003Cimg width=\"718\" alt=\"image\" src=\"https://user-images.githubusercontent.com/5887929/177331097-d9c1a121-560b-47f6-9431-4c8a92a38952.png\">\r\n\r\n\r\nUnrelated, Also a bit worried, hopefully, it would be mitigated on the official testnet of bsx these 24 sec blocks. \r\n\r\n\u003Cimg width=\"224\" alt=\"image\" src=\"https://user-images.githubusercontent.com/5887929/177331826-ce5361ad-ae1f-48ba-89f4-50d3ae32853b.png\">\r\n\r\n\r\nThe future fix would be to fetch recent events, find classCreateEvent by user, push to localstorage at client and then client can easily select it from the select box sooner than the indexer would have it. \r\n ",[2082,2083,2084,2087,2088],{"name":1988,"color":1989},{"name":2008,"color":2009},{"name":2085,"color":2086},"p1","D93F0B",{"name":1991,"color":1992},{"name":2030,"color":1992},3333,"Add explainer at collection select for fresh minted collection for user","2022-08-04T05:50:07Z","https://github.com/kodadot/nft-gallery/issues/3333",0.76962525,{"description":2095,"labels":2096,"number":2100,"owner":1997,"repository":1998,"state":1999,"title":2101,"updated_at":2102,"url":2103,"score":2104},"### Is your feature request related to a problem?\r\n\r\nThe code looks supper messy, and It's tough to read\r\n\r\n### Describe the solution you would like\r\n\r\n- Clean up the code.\r\n- Make it more component friendly (aka reusable)\r\n\r\n### Describe alternatives you have considered\r\n\r\n\r\nref #2551\r\n\r\nThis issue is currently blocked by https://github.com/kodadot/rubick/issues/40\r\nWe need to save the current owner of the NFT when the event has happened \r\n",[2097,2098,2099],{"name":1988,"color":1989},{"name":2008,"color":2009},{"name":2011,"color":2012},2589,"Refactor History component","2022-05-26T15:34:18Z","https://github.com/kodadot/nft-gallery/issues/2589",0.77009284,{"description":2106,"labels":2107,"number":2112,"owner":1997,"repository":1998,"state":1999,"title":2113,"updated_at":2114,"url":2115,"score":2116},"> I think one is used for Rmrk and the other one for Statemine, Westmint, Bsx. it would be good to unify all this\r\n\r\nCould we open another issue to handle this unification of these two components?\r\nI think it's not in the description of the original issue and maybe will cost much more time : )\r\n\r\n_Originally posted by @Jarsen136 in https://github.com/kodadot/nft-gallery/issues/2948#issuecomment-1119630405_",[2108,2110],{"name":2109,"color":1992},"A-refactoring",{"name":2111,"color":1992},"A-multi-chain",2965,"Unify shopping logic for multichain","2024-07-31T14:04:45Z","https://github.com/kodadot/nft-gallery/issues/2965",0.7711602,{"description":2118,"labels":2119,"number":2124,"owner":1997,"repository":1998,"state":1999,"title":2125,"updated_at":2126,"url":2127,"score":2128},"Since our /snek is up and running, we'd like to bring over the already implemented functionality from /bsx, I may have forgotten something + I'm not sure about the indexer here, whether new resolvers need to be written or not, regardless. this needs to be done. In case of required indexer work, this can be eventually split into multiple issues.\r\n\r\nIn the meantime, it would be nice to generate some offer activity on /snek so we have something to test this on ( ideally mix in some offers with lower expiration dates as well 👀 - @JustLuuuu @DeluneClaire @cryptodamsky )\r\n\r\nThe stuff we're missing: \r\n\r\n1. routes to /offers and /stats\r\n2. make sure routes work from navbar:\r\n\r\n3. Offers Made tab at user profile:\r\n\r\n4. Incoming offers for user /incomingoffers\r\n\r\n",[2120,2122,2123],{"name":2121,"color":2009},"$$",{"name":2085,"color":2086},{"name":1991,"color":1992},3888,"Migrating Offers related components to /snek","2022-09-04T07:15:32Z","https://github.com/kodadot/nft-gallery/issues/3888",0.77273154,["Reactive",2130],{},["Set"],["ShallowReactive",2133],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"06MudligT_VzN-FR4JugjVebqD-Gwxr6jhhZWNgTRxU":-1},"/kodadot/nft-gallery/3298"]