Templating documentation and guides to use a specific chain
@deansallinen is already working on this.
Since Sep 1, 2023.
- Dominant language
- Svelte
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The basic of the idea is this:
- We'd have a dropdown somewhere in the site where you could "Select a blockchain"
- This dropdown would contain Jungle4, EOS, WAX, Telos, and UX
- When the user changed this dropdown, it'd remember their choice and show somewhere on the page
- As the user is browsing documentation or guides, all the chain-specific information would change to be that blockchain
- This means
https://jungle4.greymass.comwould be not always jungle 4, but a specific chain - The same as the above, except with chain IDs.
This idea came from Telegram here: https://t.me/wharfkit/1362
I'm not sure how we'd accomplish this, except maybe we write some kind of variable into the page that happens on page render? Maybe there's a [[[chain_url]]] string in the markdown, which then persists in the HTML, and when the page renders, reads the users preference and renders https://jungle4.greymass.com?
I'm not sure we should jump on this immediately, but would like to know what kind of effort it'd take to pull this off.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.