Have a general structure of the repository
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
- Welcome
- mini dictionary
- About us section
Tutorials:- How to get started?
- Wallets
- Polkadot Networks
- Teleporting
- Polkadot 2.0
- How to buy Coretime?
- Assigning a Core to a Parachain
- Transfer Core
- Modifying the Core
- Renewing a Core
Advanced:
- links and resources to learn more
- Interact with the Price Simulator
For Developers: - Contributors
- Interact with the Broker Pallet
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.
Research direction
Review the repository's current documentation structure against the proposed Welcome, mini dictionary, About us, Tutorials, Advanced, and For Developers sections. Confirm the intended navigation and content locations with maintainers, then consider the structure complete when these sections are organized and accessible.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100