\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)",[2926,2928,2930,2931],{"name":2927,"color":2872},"p2",{"name":2929,"color":2875},"A-landing",{"name":2891,"color":2892},{"name":2932,"color":2933},"redesign","227120",3844,"Redesign Landing page","2022-10-19T15:38:37Z","https://github.com/kodadot/nft-gallery/issues/3844",0.74272305,{"description":2940,"labels":2941,"number":2948,"owner":2877,"repository":2878,"state":2894,"title":2949,"updated_at":2950,"url":2951,"score":2952},"> That is something I would like to avoid. That's why we have the worker as it serves as proxy and we do not need to rework the component\r\n\r\n> maybe make a separate issue and can be done as supplement PR?\r\n\r\nnoted, so the task is to cache `Response.redirect()` on the workers side. it will help the proxy to resolve faster to cf-images\r\n\r\n_Originally posted by @preschian in https://github.com/kodadot/nft-gallery/issues/4587#issuecomment-1370866557_\r\n ",[2942,2943,2945,2947],{"name":2868,"color":2869},{"name":2944,"color":2875},"A-research",{"name":2946,"color":2872},"p4",{"name":2907,"color":2875},4595,"Faster Response.redirect() for image proxy","2023-01-16T19:30:34Z","https://github.com/kodadot/nft-gallery/issues/4595",0.7495624,{"description":2954,"labels":2955,"number":2967,"owner":2877,"repository":2878,"state":2894,"title":2968,"updated_at":2969,"url":2970,"score":2971},"backlogging for redesign as it's among onboarding popular field for users \r\n\r\n> onchain identity supports picture this would be nice we could include on user profile their pictures\r\n\r\n- we will probably putting there IPFS hash which will point on our gateway, best way we can do it right now, need confirm if IPFS is not too long as I've seen u32 there\r\n- we can also show some thumb of uploaded picture\r\n- \r\n\r\n- https://github.com/kodadot/nft-gallery/issues/4466\r\n\r\n\u003Cimg width=\"1116\" alt=\"image\" src=\"https://user-images.githubusercontent.com/104380776/213158601-571ee80e-db20-4b88-9037-4237546e11c8.png\">\r\n\r\n_Originally posted by @JustLuuuu in https://github.com/kodadot/nft-gallery/issues/4466#issuecomment-1386895690_\r\n ",[2956,2957,2960,2961,2964],{"name":2927,"color":2872},{"name":2958,"color":2959},"onboarding","715318",{"name":2932,"color":2933},{"name":2962,"color":2963},"on-chain","95EB87",{"name":2965,"color":2966},"Ready for dev","12F4BE",4751,"Redesign Identity dialog","2023-09-30T12:35:37Z","https://github.com/kodadot/nft-gallery/issues/4751",0.7502132,{"description":2973,"labels":2974,"number":2989,"owner":2877,"repository":2878,"state":2894,"title":2990,"updated_at":2991,"url":2992,"score":2993},"### Is your feature request related to a problem?\r\n\r\nRMRK is knocking on the door and with that a support for multiresource NFTs\r\n\r\n### Describe the solution you would like\r\n\r\nIt would be nice do design how to show multiresource NFTs in the new gallery detail \r\n\r\ncc @exezbcz \r\n\r\n### Describe alternatives you have considered\r\n\r\nHaving same carrousel as singular?\r\n\r\n## Ref \r\n- https://github.com/kodadot/packages/issues/80\r\n- https://github.com/kodadot/packages/pull/43\r\n- kodadot/grants#6 ",[2975,2978,2979,2982,2984,2987],{"name":2976,"color":2977},"enhancement","a2eeef",{"name":2944,"color":2875},{"name":2980,"color":2981},"redesign-seeds","053A03",{"name":2983,"color":2872},"p5",{"name":2985,"color":2986},"design-request","9259A3",{"name":2988,"color":2875},"A-rmrk2",4516,"Multi resource component/design","2024-07-31T14:16:30Z","https://github.com/kodadot/nft-gallery/issues/4516",0.7528156,{"description":2995,"labels":2996,"number":3003,"owner":2877,"repository":2878,"state":2894,"title":3004,"updated_at":3005,"url":3006,"score":3007},"description: https://github.com/kodadot/nft-gallery/issues/4111#media-section",[2997,2999,3000,3002],{"name":2998,"color":2869},"$$",{"name":2927,"color":2872},{"name":3001,"color":2875},"A-item",{"name":2932,"color":2933},4228,"redesign: Media Component (histoire-able)","2022-11-10T08:54:09Z","https://github.com/kodadot/nft-gallery/issues/4228",0.75699025,{"description":3009,"labels":3010,"number":3013,"owner":2877,"repository":2878,"state":2894,"title":3014,"updated_at":3015,"url":3016,"score":3017},"To avoid the particular end-users issues when a particular RPC provider doesn't work, let's add some load balancing checks in round robin fashion where it can try out other endpoints if the default fails. \r\n\r\n> have you tried changing different RPC endpoints at https://kodadot.xyz/settings ?\r\n> \r\n> \u003Cimg alt=\"image\" width=\"224\" src=\"https://user-images.githubusercontent.com/5887929/174314437-a6dc8c56-5f6b-4f7a-a76d-aee8199906ff.png\">\r\n\r\n> That worked, but this is not long term solution? Cannot we automatize this in the background so end user doesn’t have to care? Or we cannot change user’s endpoints?\r\n\r\n_Originally posted by @cryptodamsky in https://github.com/kodadot/nft-gallery/issues/3169#issuecomment-1158939393_",[3011,3012],{"name":2868,"color":2869},{"name":2927,"color":2872},3170,"Load balance RPC endpoint for user","2022-06-20T12:02:48Z","https://github.com/kodadot/nft-gallery/issues/3170",0.7573274,["Reactive",3019],{},["Set"],["ShallowReactive",3022],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fu7_6xbfx9sL_swQ_HelFi3eYZliTYbTYpdr9X48R6ik":-1},"/kodadot/nft-gallery/4598"]