\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)",[3116,3117,3119,3122],{"name":3078,"color":3025},{"name":3118,"color":3031},"A-landing",{"name":3120,"color":3121},"chief","67EA1F",{"name":3046,"color":3047},3844,"Redesign Landing page","2022-10-19T15:38:37Z","https://github.com/kodadot/nft-gallery/issues/3844",0.76533175,{"description":3129,"labels":3130,"number":3135,"owner":3033,"repository":3034,"state":3052,"title":3136,"updated_at":3137,"url":3138,"score":3139},"We are currently showing Spotlight per chain, as our original design intent was to have this multichain. \r\n\r\nFor that to happen, we will have a multi-chain indexer, which will make it possible\r\n- #4257 \r\n\r\nOnce the upper issue is resolved, we can update Spotlight to show multichain resources ^ \r\n\r\nCurrently showing like this \r\n- per Basilisk\r\n\r\n\r\n- per RMRK\r\n\r\n\r\n### Ref\r\n- #3844 ",[3131,3132,3133,3134],{"name":3021,"color":3022},{"name":3024,"color":3025},{"name":3030,"color":3031},{"name":3049,"color":3050},4275,"Multichain Spotlight","2025-07-26T02:03:29Z","https://github.com/kodadot/nft-gallery/issues/4275",0.765651,{"description":3141,"labels":3142,"number":3149,"owner":3033,"repository":3034,"state":3052,"title":3150,"updated_at":3151,"url":3152,"score":3153},"After we added additional checks in #3546, it would be nice if somebody could take a look at the overall way in which we handle minting process, more specifically, how do we check for things such as:\r\n\r\n- [ ] insufficient balance\r\n- [ ] invalid characters\r\n- [ ] form validation in general\r\n\r\nAs an example, I've noticed one difference: On rmrk, insufficient balance means disabled submit button, on bsx insufficient balance means form validation error. iirc, @roiLeo was fan of the second solution, so we could move with that.\r\n\r\nPoint is to have similar UI/UX, it shouldn't change based on the chain (other than chain specific features)\r\n\r\n// original comment: \r\n\r\nok let's merge this since the bsx part seem so to be working (and that's why the issue was created), however ⚠️ we'll need more refactor, currently, the way we handle form validation / minting at rmrk doesn't match bsx at all (button to submit is disabled there in case of insufficient balance).\r\n\r\n_Originally posted by @petersopko in https://github.com/kodadot/nft-gallery/issues/3546#issuecomment-1209075113_",[3143,3146,3147,3148],{"name":3144,"color":3145},"enhancement","a2eeef",{"name":3021,"color":3022},{"name":3080,"color":3031},{"name":3099,"color":3031},3703,"Unify minting process experience - BalanceInput.vue","2022-08-16T15:37:23Z","https://github.com/kodadot/nft-gallery/issues/3703",0.76583135,{"description":3155,"labels":3156,"number":3162,"owner":3033,"repository":3034,"state":3052,"title":3163,"updated_at":3164,"url":3165,"score":3166},"We still need essential parts to be more multi-chain robust, like search.\r\nI briefly chatted with Viki that we will have a cheap hack to aggregate results from other chains for search, for example. \r\n\r\nCurrent results show only one chain.\r\n\r\nI guess we would leverage this on top collections too.\r\n\r\n\r\n## Continue\r\n- https://github.com/kodadot/nft-gallery/issues/4380\r\n\r\n---\r\nFirst draft of schema\r\n\r\nCollection\r\n\r\n```sql\r\n-- create table collection_entities with following columns\r\n-- id (uuid, primary key, auto increment)\r\n-- animation_url (text)\r\n-- block_number (bigint)\r\n-- chain (enum, default 'rmrk')\r\n-- collection_id (text)\r\n-- count (integer, default 0)\r\n-- created_at (timestamp, default now())\r\n-- floor_price (bigint, default 0)\r\n-- hash (text)\r\n-- image (text)\r\n-- issuer (text, foreign key to creators table)\r\n-- max (integer)\r\n-- metadata (text)\r\n-- name (text)\r\n-- supply (integer, default 0)\r\n-- updated_at (timestamp, default now())\r\n-- version (integer, default 0)\r\n```\r\n\r\nNFT: \r\n```sql\r\n-- create table nft_entities with following columns\r\n-- block_number (bigint)\r\n-- chain (enum, default 'rmrk')\r\n-- collection_id (text, foreign key to collection_entities table)\r\n-- issuer (text, foreign key to creators table)\r\n-- id (uuid, primary key, auto increment)\r\n-- metadata (text)\r\n-- name (text)\r\n-- image (text)\r\n-- animation_url (text)\r\n-- created_at (timestamp, default now())\r\n-- updated_at (timestamp, default now())\r\n-- hash (text)\r\n-- serial_number (integer)\r\n-- version (integer, default 0)\r\n```\r\n\r\n--- \r\nFollow up what can be done with new endpoint\r\n\r\nSo I managed to pushed the data into `Supabase`\r\nIf anyone wants to play with that here is the URL\r\n\r\n```\r\nhttps://xtnvtbdyvpbbnonbbcif.supabase.co/graphql/v1\r\n```\r\n\r\nYou need to add `apiKey` header into your request. You can find the key in the discord group.\r\n\r\n\r\nSample Query\r\n```graphql\r\nquery findCollections {\r\n\tcollectionsCollection(first: 10) {\r\n\t\tedges {\r\n\t\t\tnode {\r\n\t\t\t\tname\r\n\t\t\t}\r\n\t\t}\r\n\t}\r\n}\r\n```\r\n\r\n## Ref\r\n- https://github.com/kodadot/nft-gallery/discussions/4457#discussioncomment-4555921\r\n- https://developers.cloudflare.com/d1/platform/client-api/\r\n- https://github.com/kodadot/nft-gallery/issues/1824\r\n- https://github.com/kodadot/nft-gallery/issues/4257",[3157,3158,3159,3161],{"name":3021,"color":3022},{"name":3024,"color":3025},{"name":3160,"color":3031},"A-search",{"name":3030,"color":3031},4617,"Add multi-chain support to the search ","2024-07-31T13:56:48Z","https://github.com/kodadot/nft-gallery/issues/4617",0.7665758,["Reactive",3168],{},["Set"],["ShallowReactive",3171],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fzz3ZwVkXsvYtXpe4VwrmWhraBciyHPcD7Ts8fyE-FT8":-1},"/kodadot/nft-gallery/2965"]