Update sdk examples (in rust, go, java, JS)

[linnnsss]

• added github links of SDK code examples in rust, go, java, and lumos, on the nervos ckb sdks page
• added new pages of SDK code examples under "basics-guides", including an additional intro to these three operation categories (transfer, sudt, DAO operations)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nervos-ckb-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 24, 2023 6:28am

[jordanmack]

• added new pages of SDK code examples under "basics-guides", including an additional intro to these three operation categories (transfer, sudt, DAO operations)

What pages have links to these new examples?

[homura]

There seems a lack of sidebar configuration of SDK examples in the sidebar.json like the following

docs.nervos.org/website/sidebars.json

Lines 30 to 38 in 65b3d96

	"type": "category",
	"label": "Crypto Wallet",
	"items": [
	"basics/guides/crypto wallets/neuron",
	"basics/guides/crypto wallets/imtoken",
	"basics/guides/crypto wallets/safepal",
	"basics/guides/crypto wallets/portalwallet",
	"basics/guides/crypto wallets/bitpie"
	]

[jordanmack]

Overview Page:

• It appears you may have been trying to add a link in the first section, but it came out as code.
• I would recommend a small change for readability. Instead of the three sections being labeled 1, 2, 3, then the subsections a, b, c, make the three sections each a header, followed by a brief description, then the subsections are a 1, 2, 3 list.

@linnnsss

[15168316096]

@linnnsss I have questions about ckb-sdk-swift. I see that the sdk repo has been archived. It feels like it has been a long time. I should be familiar with the current ckb There are quite a few versions of adaptation. Check whether it is necessary to write it in the nvervos ckb sdk document. Also, this repo is not under the nervous network. personal

[linnnsss]

Overview Page:

• It appears you may have been trying to add a link in the first section, but it came out as code.
• I would recommend a small change for readability. Instead of the three sections being labeled 1, 2, 3, then the subsections a, b, c, make the three sections each a header, followed by a brief description, then the subsections are a 1, 2, 3 list.

@linnnsss

thanks for the suggestions, updated.