\r\n\r\nFinally, we have an endpoint we can start to integrate multi-chain components.\r\n\r\nAt some point would be nice to have some component which would wrap and abstract the current endpoint in case we find Supabase is not sufficient for our case. \r\n\r\n\r\n## Endpoint\r\nFollow up what can be done with new endpoint\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\r\n## Tasks \r\n- https://github.com/kodadot/nft-gallery/issues/4865\r\n- https://github.com/kodadot/nft-gallery/issues/4617\r\n- https://github.com/kodadot/nft-gallery/issues/4380\r\n- https://github.com/kodadot/nft-gallery/issues/4618\r\n- https://github.com/kodadot/nft-gallery/issues/4073\r\n- https://github.com/kodadot/nft-gallery/issues/4275\r\n- https://github.com/kodadot/nft-gallery/issues/4753\r\n\r\nOnce all the above done \r\n- https://github.com/kodadot/nft-gallery/issues/4379\r\n\r\n## Ref\r\n- https://developers.cloudflare.com/d1/platform/client-api/\r\n- https://github.com/kodadot/nft-gallery/issues/1824",[2865,2868,2871,2874,2877],{"name":2866,"color":2867},"$$","0E8A16",{"name":2869,"color":2870},"p2","D4C5F9",{"name":2872,"color":2873},"A-search","FBCA04",{"name":2875,"color":2876},"chief","67EA1F",{"name":2878,"color":2873},"A-multi-chain",4257,"kodadot","nft-gallery","open","Enable Multi-chain capabilities in KodaDot","2023-03-15T14:49:24Z","https://github.com/kodadot/nft-gallery/issues/4257",0.7375976,{"description":2888,"labels":2889,"number":2899,"owner":2880,"repository":2881,"state":2882,"title":2900,"updated_at":2901,"url":2902,"score":2903},"Right now, KodaDot was built mostly to be an on-chain data explorer and being a thin layer. Hence we would like to enhance comfort and are not sure if we should put these numbers like views on-chain as it might get expensive; we would like to provide users/artists some off-chain metrics and close to real-time.\r\n\r\nMaking a serverless function (worker?) which will be storing this stuff in KV in some efficient way. \r\nProbably each 1k, or 10k we can offload some stores to some remark to store these numbers on-chain to having only small increments off-chain. \r\n\r\nThis would be helpful for artists, creators and game item designers to have approximate estimation of which item is in demand. Similiar you have plays in Spotify, this would help estimate general audience likeliness of particular artifact \r\n\r\nWe could collect \r\n- load times of item (we should put some filter/captcha to account it was human viewing and not programmatically made or bumping some views)\r\n- if it's video play times\r\n- if it's 3d, time user has played with item?\r\n- if it's downloadable, times user/owner has downloaded it \r\n\r\nwyt?\r\n\r\n\r\nWe can then incorporate this into the new v1.1 Gallery item detail\r\n- #4403 \r\n\r\n\r\nTo start iterating on this, we would like to start showing this views per visit from logged persons. \r\nI think we can still trigger workers somehow and I guess we should split it to counting with logged vs not logged persons with wallet\r\nWe can trigger worker from which item was it visited and take it from there? \r\n\r\nUsing Workers/CF infrastructure would be probably easiest \r\n\r\n",[2890,2893,2895,2897],{"name":2891,"color":2892},"enhancement","a2eeef",{"name":2894,"color":2873},"A-research",{"name":2896,"color":2870},"p3",{"name":2898,"color":2873},"A-worker",4593,"Views counter/ranking","2023-04-11T20:04:33Z","https://github.com/kodadot/nft-gallery/issues/4593",0.78125286,{"description":2905,"labels":2906,"number":2912,"owner":2880,"repository":2881,"state":2913,"title":2914,"updated_at":2915,"url":2916,"score":2917},"This will be place holder issue to bit coordinate the transition to the new rewrite and version of KodaDot 2.0.\r\n\r\n# Where you can test new beta version? \r\n**Go to the [beta.kodadot.xyz](https://beta.kodadot.xyz/)** [backup](https://koda-nuxt.netlify.app/) \r\n\r\n# Found a bug?\r\n\r\n[To ensure everything will land smoothly to production and mainstream, please report a bug here](https://github.com/kodadot/nft-gallery/issues/new?assignees=&labels=bug&template=bug.yml&title=Be+descriptive+and+short)\r\n\r\n# Want to chat? \r\n\r\n[Let us know on Discord channel #beta](https://discord.gg/G2JmdCjA6r) \r\n\r\n# [Project table](https://github.com/orgs/kodadot/projects/1/views/1)\r\n[Overview of outstanding issues for beta](https://github.com/orgs/kodadot/projects/1/views/1)\r\n\r\n# Progress - in a particular order, to be done.\r\n- https://github.com/kodadot/nft-gallery/issues/1251\r\n- https://github.com/kodadot/nft-gallery/issues/1113\r\n- https://github.com/kodadot/nft-gallery/issues/984\r\n- https://github.com/kodadot/nft-gallery/issues/1224\r\n- https://github.com/kodadot/nft-gallery/issues/1155\r\n- https://github.com/kodadot/nft-gallery/issues/1028\r\n- https://github.com/kodadot/nft-gallery/issues/992\r\n\r\n### Done \r\n- https://github.com/kodadot/nft-gallery/issues/1154\r\n- https://github.com/kodadot/nft-gallery/issues/1089\r\n- https://github.com/kodadot/nft-gallery/issues/912\r\n- https://github.com/kodadot/nft-gallery/issues/1077\r\n\r\n## Migration Strategy \r\n\r\n- [x] once https://github.com/kodadot/nft-gallery/issues/1089 is done, let's freeze `main` branch\r\n- [ ] rename `main` to `main-spa`\r\n- [ ] rename `main-nuxt` to `main` \r\n- [ ] check new deployment for `main`\r\n- [ ] deploy legacy.kodadot.xyz from `main-spa`\r\n- [x] move current spa into `/spa` folder\r\n- [ ] back merge `main-spa` into `main`\r\n- [ ] remove `spa/` folder from `main`\r\n- [ ] set deploy from `rmrk-fluffy` on Netlify\r\n\r\n# Backlog\r\nIt will be starting with merging #843 into `main-nuxt`, then syncing `main-nuxt` with `main`, then switching gears to deployment running from `nuxt/` folder.\r\n\r\n\r\n### Ref\r\n- https://github.com/kodadot/nft-gallery/pull/843#issuecomment-955709805 origin\r\n- https://discord.com/channels/840514076538830888/842717226758701056/904325916346421258\r\n\r\n[Probably all of the issues labelled with `nuxt` are related in time of writing this](https://github.com/kodadot/nft-gallery/issues?q=is%3Aissue+is%3Aopen+label%3Anuxt) \r\n",[2907,2909],{"name":2908,"color":2873},"A-nuxt",{"name":2910,"color":2911},"koda2","AB66CA",1060,"closed","KodaDot 2.0 - beta & migration","2022-01-15T13:48:36Z","https://github.com/kodadot/nft-gallery/issues/1060",0.7347678,{"description":2919,"labels":2920,"number":2923,"owner":2880,"repository":2881,"state":2913,"title":2924,"updated_at":2925,"url":2926,"score":2927},"It's related to the deploy environment\r\n\r\nnew one: https://deploy-preview-11317--polkadot.netlify.app/ahp/collection/244\r\n\r\noriginal: https://deploy-preview-11317--koda-canary.netlify.app/ahp/collection/244\r\n\r\n_Originally posted by @Jarsen136 in https://github.com/kodadot/nft-gallery/issues/11318#issuecomment-2566997713_\r\n \r\n\r\n\u003Cimg width=\"821\" alt=\"image\" src=\"https://github.com/user-attachments/assets/1dd14728-f326-4886-a4eb-dab719c9ed45\" />\r\n\u003Cimg width=\"857\" alt=\"image\" src=\"https://github.com/user-attachments/assets/e103dc3a-e5c8-4f76-82c9-180a483a3628\" />\r\n\r\nIt looks like every PR has these double deployment. We should only keep one netlify deployment env.\r\n\r\n@vikiival Do you have access to the netlify dashboard?\r\n",[2921],{"name":2922,"color":2873},"A-maintenance",11326,"Double deploy on netlify for all the branchs","2025-02-13T16:33:26Z","https://github.com/kodadot/nft-gallery/issues/11326",0.740735,{"description":2929,"labels":2930,"number":2938,"owner":2880,"repository":2881,"state":2913,"title":2939,"updated_at":2940,"url":2941,"score":2942},"Probably deploy serverless twitter bot which will tweet once we merge new stuff into production branch, current `rmrk-lite` in future we will have more of them, like per parachain, upcoming are basilisk and statemine\r\n\r\nCould be merged with https://github.com/kodadot/nft-gallery/issues/734 somehow\r\n\r\nIdea behind this is, I can write a changelog in something like tweets, i.e. if we have 3 features in the current upgrade, format for tweets would be tweet per line? Or actually standardize PR changelog so twitter bot can parse that.\r\n\r\ntweet thread \r\n- this brings new colours to the profile\r\n- this optimizes bundle so kodadot now loads faster on your device\r\n- enjoy new sharing buttons",[2931,2934,2936],{"name":2932,"color":2933},"good first issue","5319e7",{"name":2935,"color":2867},"$",{"name":2937,"color":2870},"p5",795,"Create Twitter bot to Tweet when there is production update","2022-04-08T09:43:53Z","https://github.com/kodadot/nft-gallery/issues/795",0.7604776,{"description":2944,"labels":2945,"number":2950,"owner":2880,"repository":2881,"state":2913,"title":2951,"updated_at":2952,"url":2953,"score":2954},"Hence to ease onboarding for new contributors, would be nice to have a lightweight article on how KodaDot actually works in the background. How KodaDot is actually middleware and leveraging existing web3 infrastructure to drive end-user experience and how can anyone use us as a template to make spinoffs with existing components.\r\n\r\nI would suggest mentioning\r\n- subquery (vikiival/magick, kodadot/unique)\r\n- subsquid (kodadot/rubick, kodadot/snek)\r\n- Cloudflare / workers\r\n- bao (pictures)\r\n- packages (subapi, minimark, vuex-options)\r\n- Nuxt \r\n- Infra providers (Netlify, CF)\r\n- Storage, [you can recycle from @kkukelka article about past, present and future of data storage](https://medium.com/kodadot/on-the-past-present-and-future-of-data-storage-at-kodadot-7634a0c32530?source=collection_home---------2-------------------------------)\r\n\r\nBonus stage (required for better awareness for new comers)\r\n- Make a dedicated page on docs.kodadot.xyz for tech-stack for better reachability\r\n\r\nAnything I'm missing? 📟 @vikiival \r\n\r\nh/t @thea-exe for amazing nudge and spotting blind spot",[2946,2947,2948],{"name":2866,"color":2867},{"name":2896,"color":2870},{"name":2949,"color":2873},"A-writing-✍️",2766,"Write article about tech stack of KodaDot ","2022-06-25T08:20:51Z","https://github.com/kodadot/nft-gallery/issues/2766",0.76855284,{"description":2956,"labels":2957,"number":2962,"owner":2880,"repository":2881,"state":2913,"title":2963,"updated_at":2964,"url":2965,"score":2966},"- `main` branch for stable release\r\n- `nuxt-mark` as for production j/k w vikiival\r\n- archive `rmrk-lite` and `old-spa` time to say good bye\r\n- keep `main-nuxt` as beta channel so it can be still default branch tho to track issue and issues closes automatically\r\n\r\nAny objections? \r\n\r\n### Ref \r\n- #1060 \r\n- #1612 ",[2958,2961],{"name":2959,"color":2960},"p1","D93F0B",{"name":2908,"color":2873},1726,"Deploy pre-production to Cloudflare pages","2022-01-15T13:15:06Z","https://github.com/kodadot/nft-gallery/issues/1726",0.7706873,{"description":2968,"labels":2969,"number":2977,"owner":2880,"repository":2881,"state":2913,"title":2978,"updated_at":2979,"url":2980,"score":2981},"Also I would extend middleware so `https://beta.kodadot.xyz/bsx` will go to `https://beta.kodadot.xyz`\r\n\r\n_Originally posted by @vikiival in https://github.com/kodadot/nft-gallery/pull/3227#issuecomment-1161664483_",[2970,2971,2972,2974],{"name":2935,"color":2867},{"name":2896,"color":2870},{"name":2973,"color":2873},"A-landing",{"name":2975,"color":2976},"entropy","F02D17",3237,"Landing page of parachain should have fallback ","2022-06-26T07:24:50Z","https://github.com/kodadot/nft-gallery/issues/3237",0.77269554,{"description":2983,"labels":2984,"number":2989,"owner":2880,"repository":2881,"state":2913,"title":2990,"updated_at":2991,"url":2992,"score":2993},"To me looks like a Netlify outage?\r\n\r\n`Deploy did not succeed: Deploy directory 'dist' does not exist`\r\n\r\nFirst failed build seems on `main` at 11:44am\r\n\r\nMy bet is at \r\n\r\nhttps://github.com/kodadot/nft-gallery/pull/2815/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519R27\r\n\r\n### Ref\r\n- https://github.com/kodadot/nft-gallery/pull/2812\r\n- https://github.com/kodadot/nft-gallery/pull/2825\r\n- #2718 \r\n\r\nhttps://app.netlify.com/teams/yangwao/builds/625549e849e59900089b0d26\r\n\r\n\r\n\r\nhttps://app.netlify.com/sites/koda-nuxt/deploys/62554a7806c0270008e7f412\r\n\r\n\r\n\r\n",[2985,2986],{"name":2959,"color":2960},{"name":2987,"color":2988},"🧙♀️ - bug-hunt","DC2653",2826,"Builds are broken ","2022-04-12T11:39:00Z","https://github.com/kodadot/nft-gallery/issues/2826",0.7728931,{"description":2995,"labels":2996,"number":3000,"owner":2880,"repository":2881,"state":2913,"title":3001,"updated_at":3002,"url":3003,"score":3004},"It's time to continue on handovering to new branch stuff so we can be in sync and avoid ppl making PRs into old code.\r\n\r\n- [x] merge `main` into `main-nuxt` \r\n- [x] delete all stuff root connected with old **SPA** in `main-nuxt`\r\n- [x] put the context of folder `/nuxt` to the upper directory\r\n- [x] re-set deploy from root directory -- that's on @yangwao \r\n- [x] enjoy new PRs!\r\n\r\n# ref\r\n#1060 ",[2997,2998,2999],{"name":2959,"color":2960},{"name":2908,"color":2873},{"name":2910,"color":2911},1077,"Sync main branch into main-nuxt","2021-11-10T17:16:21Z","https://github.com/kodadot/nft-gallery/issues/1077",0.7755367,["Reactive",3006],{},["Set"],["ShallowReactive",3009],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f_LWT4Nh80Wk9BX0tD3KufQwZlICyom5-Ubs9EHpMisM":-1},"/kodadot/nft-gallery/657"]