seems navbar and search is gone?

Sharing slides from my kodadot ecosystem talk
cc @poppyseedDev

Who we are

Mission

unlockable-as-sdk

general overview of tooling

Uniquery

Workers

Indexers

MiniMark

Fandom Shops

CLI tooling

coming soon

@thea-exe following the last thing here

I'm thinking, guide on how to turn $KSM into cash without KYC? 🚀

Originally posted by @petersopko in kodadot/nft-gallery#1269 (comment)

I guess we should prepare one dedicated page where we can show people what's best to mint on kodadot for optimal experience and then we can link it from kodadot.xyz minting interface

did my best
2ce2914..fc654b9

is there vuepress plugin to show it on all pages with warning tip?

we don't want to break SEO of those pages and later do best soft redirect to hello?

Following up from here kodadot/nft-gallery#3356

In https://github.com/kodadot/nft-gallery/blob/main/REWARDS.md , it is not clear in the table that the reward amount is in USD (and not KSM since it is your favorite currency)

Describe the solution you would like
I would like to see the currency clearly stated, like in the label

Describe alternatives you have considered
Put the KSM amount ^^

Screeenshots
No response

Are there opened related issues?
No response

Thanks to @joelamouche

• Submit your site to Google: Do this via Google's Search Console. This informs Google your site exists and requests it to crawl your site.
• Check your robots.txt file and meta tags: Ensure they're not inadvertently blocking Google from indexing your site or any of its important pages.
• Improve your SEO: This might include using relevant keywords in your content, optimizing your meta descriptions and alt tags, using semantic HTML, etc.
• Improve your website's speed and mobile optimization: Use tools and strategies to achieve this, from optimizing images to minimizing CSS and JavaScript.

Wyt @kodadot/internal-dev

I want to deploy new vitepress and scrape all old docs to new domain with vitepress

I see lot of projects using something else than docs.

Subdomain for developers

https://developers.cloudflare.com/d1/get-started/
https://developers.fractal.is/
https://developers.facebook.com/
https://api.magiceden.dev/
https://guide.rarible.com/
https://docs.opensea.io/
https://docs.looksrare.org/
https://docs.alchemy.com/
https://docs.rarible.org/

I guess once there will be tutorial kodadot/nft-gallery#2780 out there @thea-exe can make a video out of it on how to setup developer and run Kodadot Firstime for others

Video could be uploaded to our youtube channel :)

We’d need to input some basic data and tutorial on how to proceed with BSX implementation, namely:

• How to switch to BSX address
  • How is it different when using talismand and polkadot.js
• How to switch to BSX chain
• Mention our apply form
• Mention how bug reporting works
• Explain that it’s testing and the tokens are not real 🗡️

maybe unify emoji of zoom on one side?

we should change that we will be supporting nine NFT standards on nine chains

we can make it even better, nine on nine
rmrkv1, rmrkv2, erc721, erc1155, uniquesv1, nft-pallet,

in the making so I would put them in some coming soon section

gNFTs, ink NFTs (aleph,astar), eip-6551

cc @poppyseedDev

Originally posted by @yangwao in #91 (comment)

Take it from here, maybe needs to update

https://github.com/kodadot/nft-gallery/blob/main/ACTIVITY.md#kodadot-infrastructure

Originally posted by @yangwao in #94 (comment)

I would be cool to add kodadot github link in navbar "find us"

Would be nice to make a dedicated page for onboarding developers to use our API

• some examples to write stuff on how developers can use our API
• maybe leverage auto code? ( kodadot/nft-gallery#2890 )
• would be highly important before hackathons are coming

Ref

• https://www.npmjs.com/package/@kodadot1/kodapi
• kodadot/nft-gallery#2890

Kapa

• https://www.kapa.ai/
  https://twitter.com/subsquid/status/1671486108616589312?t=2k4MXoG0pDxFhexeyCm0WQ&s=35

I think it's something similiar like Gitbook has Lens for Search

https://docs.gitbook.com/product-tour/searching-your-content/lens

As we are trying build ecosystem of vivid builders experience we would need one page where we can sent everyone with all instructions.

Whenever me or someone else will be in chat with someone over internet or at physical event we can direct them to one all around page :)

Page should consist of

• culture of kodadot
• why they want to join us
• opened job positions, like at https://kodadot.xyz/jobs/
• hiring for frontend like existing process we have in hiring.md https://github.com/kodadot/nft-gallery/blob/main/HIRING.md

Current opened positions we are constantly looking for

• Frontend Developers (Vue2 + Vue3)
• Rust developer (parachain Dev & Ops & ink! smart contracts)
• Technical Product Manager
• COO
• UI/UX Designer
• Creative Director
• Developer Advocate
• Technical Writer
• Growth & Ops

We’ve currently filled the ambassador program and started junior one, please let’s update links and info according to this notion database

https://metaprime.notion.site/KodaDot-Guilds-Community-overview-e8eb64f1bbd74e7a924c5fb07e3ff3dd

Let’s also put this notion docs to navbar, we’ll be coordinating guilds there and most of the community stuff.

Form link:

https://form.kodadot.xyz/junior_ambassadors

Seems deployment fails on this one, probably we should use Git LFS on this or something else?

Maybe

https://git-lfs.github.com/ ?
or any other way to do it?

https://docs.github.com/en/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage

or we can add that webm to video, @cryptodamsky can help on that and we can link it back to docs:)

edit meanwhile I've deleted to not block docs deployment tho

Currently, we are missing a page where one can read what's under the hood of KodaDot in terms of various NFTs standards across Polkadot.

The goal of this page would be to highlight different implementations on various levels, starting from system.remark (RMRK), going through runtime level, like Basilisk NFT marketplace implementation (BSX&SNEK on Rococo), going higher to EVM implementation like MoonRiver & MoonBeam, continuing to Astar ink! WASM smart contracts and all of this in one simple interface under hood of KodaDot with other features coming to unpack like Reactive NFTs

Generalized

• https://github.com/kodadot/packages/tree/main/sub-api
• https://github.com/kodadot/packages/tree/main/uniquery

RMRK

• indexer -- rubick - https://github.com/kodadot/rubick
• minimark - https://github.com/kodadot/packages/tree/main/minimark
• other packages we are using here?
• hacks we've used - https://github.com/kodadot/packages/tree/main/metasquid

RMRKv2

• ongoing kodadot/packages#43

Basilisk

• indexer Snek - https://github.com/kodadot/snek
• how multi fee payments works under hood
• assets screen maybe?

Astar (RMRK) - under research

• rmrk pallet - https://github.com/rmrk-team/rmrk-substrate

MoonRiver & MoonBeam (EVM)

• indexer Click - https://github.com/kodadot/click
• Moonriver collections

Astar WASM - ink! smart contracts

• under research, hopefully coming 😄

Is anything significant we should mention from our major infrastructure components?

Let's drop list of good devrel inspiration we should definitley have over

inspirations

• https://docs.alchemy.com/docs/alchemy-quickstart-guide
• https://docs.blockmate.io/docs/api-reference
• https://docs.hel.io/introduction/welcome-to-helio
• https://docs.goldsky.com/recipes/nft-transfers
• https://docs.spheron.network/
• https://developer.nftscan.com/
• https://docs.nftscan.com/reference/evm/account-holding-distribution

This page would help others to learn how to work with Subsquid for debugging purposes

• how to run local SubSquid
• how to debug queries (graphQL bin / explorer?)
• what's else would help new developers to play around ?

Review our tooling in some long-form article for backlinks

cc @poppyseedDev

I guess every new folk would be nice to see where our values and culture are at.

Currently, we have numerous initiatives running which is great I guess.

• Having KodaForest/GretaForest
• Reactive NFTs
• Generative Art
• Public goods & Quadratic Funding
• Gig economy way how contributors are working

probably would be great to on dedicated meta hours page link all recordings
make youtube playlist?
https://docs.kodadot.xyz/meta_hours.html#recent-meta-hours

wiki docs: I have found that we have quite a lot great tech articles were hidden in the closed github issue. I think put them outside to bring more value. How about putting them on https://github.com/kodadot/nft-gallery/wiki

Instead of putting all articles to the wiki, would be nice to have indexable page with this

https://github.com/kodadot/nft-gallery/issues?q=is%3Aopen+is%3Aissue+label%3A%22%E2%9C%8D%EF%B8%8F+-+writing%22

          https://deploy-preview-94--developers-kodadot.netlify.app/core-concepts/kodadot-stack/

Replace to SubSquid and link to https://docs.subsquid.io/

In the upcoming section

• https://deploy-preview-94--developers-kodadot.netlify.app/other/kodadot-upcoming.html
  

I would link those NFT standards.

Expand on more NFT standards

Currently, we are starting to have section of NFT standards on our hello

I would like to see dynamic NFTs which are pop.
On-chain NFTs are not sure if they have ERC already, which are mostly SVG stuff
ERC-998
Tezos has a single Non-Fungible Token standard called FA2.
https://nftnow.com/features/new-token-standards-you-need-to-know/
ERC-721C
BRC-721E

Follow-up actions

• hint NFT standards we should have there cc @vikiival
• Recycle maybe something from https://www.nftstandards.wtf/ and give attribution

Originally posted by @yangwao in #94 (comment)

Good idea bulb to add to docs how to create collectibles with traits.

• explain hashlips
• trait systems

https://twitter.com/yuliias3/status/1492645659085787138?t=vn8j32ysEL4r1N8_OvbW-w&s=09

Where to start? - A guide

Expected Behavior

You see on twitter.

"Want to contribute, click here"

Now you are in the Kodadot Repo. Its looks intimidating. You want to make one tiny contribution. You even manage to recognize in the issue tabs the label good first issue.
You read it and understand exactly the same as you would without reading.
You try to make sense with going to the docs. It doesn't help that much.

Actual Behavior

You see on twitter.

"Want to contribute, click here"

You are in the Kodadot Repo. Its looks intimidating. You want to make one tiny contribution. You even manage to recognize in the issue tabs the label good first issue.
You read it and understand exactly the same as you would without reading.
You try to make sense with going to the docs. It helps.

Possible fix

Write an easy guide. A person with 1 year of WebDev expierience should be able to follow it and make one contribution.

I guess Damsky DMs aren't scalable enough and would be nice to generate form and add it to

https://docs.kodadot.xyz/ambassador-program/ambassador-intro.html#compensation

I would also add to show up on ambassador-program channel

It could be interesting to migrate our current documentation to Vitepress

Good head start, I guess! Funny, it has indexed most webpages out of all (hello and kodadot)

I've used https://www.checkbot.io/

I would aim to have "polkadot nft marketplace" keywords

Let’s get the page to the state where we explain what NFTs are, as it is one of use cases of KodaDot.

Ref: kodadot/nft-gallery#192

Right now at https://docs.kodadot.xyz/how_to_create_wallet.html#how-to-create-a-wallet for example doesn't preload first picture and that would be fair enough! :)

We need to document functions on our discord as well as main differences between steward x ambassador

ctx

https://forum.polkadot.network/t/dune-analytics-style-data-service-for-polkadot-kusama/271/8

@poppyseedDev want challenge 👀

Once done, submit to

• bing webmaster tools
• google webmaster tools

I think this works https://subwork.xyz/sitemap.xml

https://github.com/kodadot/subwork/blob/main/docs/.vitepress/config.ts#L20

Close this

There's built in GH function to close issues by PRs, check it out, maybe add it to the contributing.md as well? 😄 works across repos https://github.blog/2013-03-18-closing-issues-across-repositories/

(Also, pls note that in order to close multiple issues, the correct format is closes #XY, closes #XYZ etc.)

Originally posted by @petersopko in kodadot/nft-gallery#1269 (comment)

I guess the goal of docs is also to help demonstrate.
I would add links to grapqhl playground with mentioned queries? @thea-exe

https://docs.kodadot.xyz/tutorials/write-subsquid-query.html#page-info-object

Mention for devs things for better onboarding

• whats are resolvers
• serverless workers
• ???
• feel free add
• @alko89 @Matehoo if you can drop what you are struggling with

I guess to create a tally form to we can harvest applicant and add it to hiring.md here at docs

Also we should probably create forms to track who applies to each role because maybe DMing you in unsustainable? @yangwao

Would be super nice to describe all the things we can have in terms of reforestation, what's been done in co-op with RMTerra and potential ways to bring utility through ownership &c you name it creativity, even if you're wild enough to bring it for public good framing and funding through augmented bonding curve or quadratic reforestation 😄

I can fairly expand on this stuff

Also feel free drop plans on KodaForest/GretaForest, happy to cherry 🍒 pick best piecies

📟 Pedro

ref

• Discord Green NFTs
• https://github.com/kodadot/research/issues/104

As agreed with @vikiival, we’d like to keep docs.kodadot.xyz for technical purposes only and leave onboarding stuff to Github Wiki, because it’s much more frequently updated. We can link to onboarding materials on Github Wiki from docs.kodadot.xyz and make sure if people search for it, they find what they need.

We would need to seek a proper format for RFPs for grants to slowly help distribute grants to particular projects which would like to signup on this route.

I guess we should have a proper template; feel free to inspire at w3f https://github.com/w3f/Grants-Program/ and other ecosystem grants programs

Current listed grants we have at
https://github.com/kodadot/nft-gallery/discussions/3448

Goal would be that instead of having usual markdowns in repository give some indexable and more human way to read grants and RFPs (request for propals)

Top left corner, there's an error on mobile as well but when I ran the docs on my localhost, it had no error

Logs from cf

15:46:48.866 | Cloning repository...
-- | --
15:46:51.212 | From https://github.com/kodadot/docs
15:46:51.213 | * branch            0a08db6912c1955d3746b76ddbcb714fe48a5666 -> FETCH_HEAD
15:46:51.213 |  
15:46:51.515 | HEAD is now at 0a08db6 add factbook
15:46:51.516 |  
15:46:51.680 |  
15:46:51.710 | Success: Finished cloning repository files
15:46:52.455 | Installing dependencies
15:46:52.467 | Python version set to 2.7
15:46:54.592 | Attempting node version '16.13.2' from .nvmrc
15:46:56.156 | Downloading and installing node v16.13.2...
15:46:56.611 | Downloading https://nodejs.org/dist/v16.13.2/node-v16.13.2-linux-x64.tar.xz...
15:46:57.045 | Computing checksum with sha256sum
15:46:57.176 | Checksums matched!
15:47:01.614 | Now using node v16.13.2 (npm v8.1.2)
15:47:02.078 | Started restoring cached build plugins
15:47:02.093 | Finished restoring cached build plugins
15:47:02.661 | Attempting ruby version 2.7.1, read from environment
15:47:06.628 | Using ruby version 2.7.1
15:47:07.004 | Using PHP version 5.6
15:47:07.173 | 5.2 is already installed.
15:47:07.200 | Using Swift version 5.2
15:47:07.201 | Started restoring cached node modules
15:47:07.218 | Finished restoring cached node modules
15:47:07.227 | Started restoring cached yarn cache
15:47:07.247 | Finished restoring cached yarn cache
15:47:07.270 | Installing yarn at version 1.22.4
15:47:07.288 | Installing Yarn!
15:47:07.289 | > Downloading tarball...
15:47:07.335 |  
15:47:07.335 | [1/2]: https://yarnpkg.com/downloads/1.22.4/yarn-v1.22.4.tar.gz --> /tmp/yarn.tar.gz.6g9CIIEI5n
15:47:07.336 | % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
15:47:07.337 | Dload  Upload   Total   Spent    Left  Speed
15:47:07.573 | 0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0 100    80  100    80    0     0    336      0 --:--:-- --:--:-- --:--:--   337
15:47:07.703 | 0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
15:47:07.713 | curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
15:47:07.714 | More details here: http://curl.haxx.se/docs/sslcerts.html
15:47:07.714 |  
15:47:07.714 | curl performs SSL certificate verification by default, using a "bundle"
15:47:07.715 | of Certificate Authority (CA) public keys (CA certs). If the default
15:47:07.715 | bundle file isn't adequate, you can specify an alternate file
15:47:07.715 | using the --cacert option.
15:47:07.715 | If this HTTPS server uses a certificate signed by a CA represented in
15:47:07.716 | the bundle, the certificate verification probably failed due to a
15:47:07.716 | problem with the certificate (it might be expired, or the name might
15:47:07.716 | not match the domain name in the URL).
15:47:07.717 | If you'd like to turn off curl's verification of the certificate, use
15:47:07.717 | the -k (or --insecure) option.
15:47:07.717 |  
15:47:07.717 | [2/2]: https://yarnpkg.com/downloads/1.22.4/yarn-v1.22.4.tar.gz.asc --> /tmp/yarn.tar.gz.6g9CIIEI5n.asc
15:47:07.772 | 100    84  100    84    0     0   1534      0 --:--:-- --:--:-- --:--:--  1534
15:47:07.821 | 0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
15:47:07.828 | curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
15:47:07.828 | More details here: http://curl.haxx.se/docs/sslcerts.html
15:47:07.829 |  
15:47:07.829 | curl performs SSL certificate verification by default, using a "bundle"
15:47:07.829 | of Certificate Authority (CA) public keys (CA certs). If the default
15:47:07.829 | bundle file isn't adequate, you can specify an alternate file
15:47:07.830 | using the --cacert option.
15:47:07.830 | If this HTTPS server uses a certificate signed by a CA represented in
15:47:07.830 | the bundle, the certificate verification probably failed due to a
15:47:07.831 | problem with the certificate (it might be expired, or the name might
15:47:07.831 | not match the domain name in the URL).
15:47:07.831 | If you'd like to turn off curl's verification of the certificate, use
15:47:07.831 | the -k (or --insecure) option.
15:47:07.844 | > Failed to download https://yarnpkg.com/downloads/1.22.4/yarn-v1.22.4.tar.gz.
15:47:07.856 | mv: cannot stat '/opt/buildhome/.yarn': No such file or directory
15:47:07.866 | /opt/build/bin/run-build-functions.sh: line 106: yarn: command not found
15:47:07.867 | Installing NPM modules using Yarn version
15:47:08.362 | /opt/build/bin/run-build-functions.sh: line 117: yarn: command not found
15:47:08.364 | Error during Yarn install
15:47:08.367 | Failed: build command exited with code: 1
15:47:09.163 | Failed: an internal error occurred

I would like to show devs how easy is to use uniquery through StackBlitz

Probably demonstrate demo where you'll load uniquery, connect to it and fetch collections, get some data out of it.

Model data could be fetch collection, probably from rmrk2 and tell distribution of owners for current collection, floor price and highest sale, tadaa

inspiration from https://zkfs.io/

I guess it's time to highlight things which will come with reactive nfts to the KodaDot and Metaprime.

Highlighting upcoming features

• API
• reusability of components
• https://github.com/kodadot/research/issues/104
• Trait system for game items
• reactive conditional rendering
• loots/bundles

It would be good to have one page in where NFTs would be explained thoroughly. It's also easier for explaining to newcomers who are just getting started.

Referring to:
kodadot/nft-gallery#648

Might @thea-exe could create documentation around Uniquery at least with GrapqhQL and then extend it with REST API when will be available kodadot/packages#21

Then someone in nft-gallery could pick up
I guess hence we have available Uniquery would be nice to build a small raw app deployed on netlify