To enhance the quality and oversight of our codebase, I suggest implementing a requirement for at least two approvals before merging a pull request. This will ensure that changes undergo thorough review and receive input from multiple team members, leading to a more robust and reliable codebase.

instead of having our product as the parent page, we should focus on specific features. For example, we can have a page called "Staking" and then break it down into sub-pages like "Staking in Polkaswap” and "Staking on Mobile." It just makes more sense, you know? Let me know what you think.

When users interested in creating a Request for Proposal (RFP) visit the /rfp page and proceed to the corresponding GitHub repository, they may be surprised by the lack of activity there. This is because all the issues related to ecosystem projects are created directly in their corresponding repositories. To address this, we should either establish the RFP repository as a gateway to all issues related to the ecosystem or explicitly provide links to the issue lists in the corresponding repositories.

• #133

• #114

• #117

• #132

• #131

• #119

• #130

• #129

  • Consider adding contributing.md to each repo.

• #118

• #120

• #127

• #128

• #83
• #84

Make sure that we have the correct replacements or mirrors for all the links in https://docs.google.com/spreadsheets/d/15QXumaISgZ_elw_9gzXer6TyfrZhsjQVscuAglwYqIM/edit?usp=sharing so that there are no issues once the new one is deployed

Currently, there is no aggregated list of live endpoints available. It would be beneficial to provide such a list to allow users easy access to metadata and showcase the capabilities of the blockchain.

Problem statement

We need to add documentation for the XST Platform on the new wiki.

The documentation should explain or link to articles explaining the XST Platform from the business perspective (use cases, value for the users) and from the technical perspective (components involved, pallets implemented, sequence diagram) in the new wiki, in the relevant sections of the wiki.

Description

No response

Definition of Done

• Explanation of the XST Platform - Business value, use cases (I can help with that if needed)
• Explanation of the XST Platform - Components, Pallets, Sequence Diagrams

Requirements

Review from the relevant stakeholders (PM, Tech leads from client applications, Ecosystem manager)

Relevant development issues can be found in sora-xor/sora2-network#11 (comment)

Relevant articles:

https://www.notion.so/soramitsuglobal/Cross-consensus-transfer-95390c5dbdaf45b5a929b37f08e55929
https://soramitsu.atlassian.net/wiki/spaces/SB/pages/4014866588/SORA2+-+Parachains+Relaychain+interaction

Based on Makoto-san's grand introduction to how people can be active participants in SORA, a page with a name similar to Start Here should be made containing information covering;

There are many ways to contribute to the growth of SORA;
📚 You can learn about economics
🔒You can stake to protect the network
🥛You can provide liquidity
There are lots of things to do, study the ecosystem and find out how what you do today can make the most significant impact on humanity in the coming years.

RFP repo link: https://github.com/sora-xor/rfps

Write article in wiki for Parachain Bridge Public Test

https://soramitsu.atlassian.net/wiki/spaces/SE/pages/2224816140/Environments

Problem statement

As we build the new wiki for SORA, we need to update the links that redirect to the former wiki to set the redirection to the new wiki.

Description

No response

Definition of Done

• List of places where the old wiki (https://wiki.sora.org/master) is used

Requirements

No response

https://t.me/c/1484863783/4514

Build binary file for validators in order to speed up them.

Hello,

• Please add the Social Insurance page under the Participating in SORA Economy header and add the page social-insurance.md to src

• Add to page social-insurance.md

Thanks :D

Problem statement

We want to enable other wallets to easily integrate SORA Card. For that we need to provide a guide for development teams to integrate SORA Card by using the libraries we developed.

Description

No response

Definition of Done

• SORA Card integration guide added to the SORA wiki

Requirements

• Library presentation & overview
• Class diagrams (when relevant)
• Sequence diagrams (registering & KYC, payments, referral system)

Problem

The new documentation is missing content from certain pages and only includes references to them. This can be seen in the following example (running a node):

• Deployed page URL: https://wiki.sora.org/guides/staking/how-to-run-a-sora-mainnet-node
• Markdown file for the current wiki page: https://github.com/sora-xor/wiki/blob/master/guides/staking/how-to-run-a-sora-mainnet-node.md
• Location of the same file in the new wiki repository: https://github.com/sora-xor/sora-docs/blob/develop/src/running-a-node.md

Copying and pasting the markdown file results in an error, as shown in the following figure:

Resolution

To resolve this issue, manual editing of the markdown files is necessary to ensure compatibility with the new wiki platform, vitepress.dev.

https://vitepress.dev/reference/site-config#site-metadata

https://sedate-egg-190.notion.site/How-to-Unstuck-SORA-ETHEREUM-Transactions-30c01b70de1c4b8cba930a2c858e0dca

Currently, submitting a project to the builder program requires filling out a Google form, which implies that the submission is not publicly available. It is important to consider that the crypto community often has reservations about using Google services. Exploring alternative submission methods or addressing privacy concerns would be beneficial for wider participation.

• #16
  • Identity
    • The websocket link is not up-to-date.
  • NFT
    • All images are not centered.
    • We need to add more chapter interlinks. For example, in order to start swapping, one will have to add a token to a wallet, which we have mentioned in the warning section at the end. It probably makes sense to include a link to the corresponding heading in this warning box.
  • Nodes connections
    • The pictures are too big.
• #17
  • Account creation
    • I see several pictures added that are not related to the account creation process (e.g., [https://raw.githubusercontent.com/sora-xor/sora-docs/f3868f45e4f0ea45f65283a4f74ec154d3e4230a/src/.gitbook/assets/image%20(26).png)](https://raw.githubusercontent.com/sora-xor/sora-docs/f3868f45e4f0ea45f65283a4f74ec154d3e4230a/src/.gitbook/assets/image%20(26).png)).
• #19
  • I see a lot of slashes (/) added accidentally, I guess.
• Global concerns
  • As guides usually imply linear steps to be followed, it probably makes sense to annotate the steps. For example, https://github.com/soramitsu/adar/blob/docs/docs/GUIDES.md has the steps highlighted and counted, inspired by https://developers.google.com/style.
  • Currently the project cannot be built from the latest commit (npm run docs:build) due to various issues present. It is usually due to incompatibility of Gitbook asset links formatting with Vitepress. For pages migrated earlier, this issue was solved in 7763a36. As a good practice, I would not merge the pull requests that are not being built. In the future, we will be able to ensure that by having a corresponding I just like Iroha is currently having it implemented (https://github.com/hyperledger/iroha-2-docs/tree/main/.github/workflows), but for now, we will have to do it ourselves.
  • We should apply better formatting for all the pages.
  • Maybe it's worth making the figures smaller as they currently cover the entire screen on my PC. The same happens when I'm using my mobile devices.

The documentation does not provide descriptions for several essential features such as liquidity proxy, governance, and Demeter. It is crucial to include detailed explanations and information for these features to ensure a comprehensive understanding of the ecosystem.

Problems

There is no CI/CD present for this project.

Requirements

• The deployed website should have the same view as it will have after the successful build and execution of the docs:preview script. You can refer to https://vitepress.dev/guide/deploy#build-and-test-locally for details. I attempted to add a Github action (https://github.com/sora-xor/sora-docs/blob/develop/.github/workflows/deploy.yml) following the official guide (https://vitepress.dev/guide/deploy#github-pages), but as can be seen from the result (https://github.com/sora-xor/sora-docs/actions/runs/4830173715), only static HTML pages were opened.

  Note 📝 . The latest commits have issues with the project build, so until these issues are resolved, the commit 7763a36 can be used to test CI/CD.

• Temporarily, the docs can be deployed to https://github.com/sora-xor/sora-docs.

It would be valuable to include development contribution guidelines and process schemas to assist developers in understanding how to contribute effectively to the project.

The wiki appears to be disconnected from other popular channels, such as Medium. It would be beneficial to include references or even embed content from these channels within the wiki to create a more cohesive and interconnected documentation experience.

Description

In order to foster seamless collaboration and interoperability within the Dotsama ecosystem, it is crucial to provide ecosystem developers with clear and detailed guidelines on how to open an HRMP channel with us. This comprehensive guide aims to empower developers by equipping them with the knowledge and resources necessary to establish efficient HRMP channels, enabling the exchange of information and value across different Substrate-based projects.

Relevant materials

• https://docs.moonbeam.network/builders/interoperability/xcm/xc-integration/
• https://docs.astar.network/docs/xcm/integration/hrmp
• https://guide.kusama.network/docs/build-hrmp-channels/

Relevant issues

• sora-xor/sora2-network#594
• sora-xor/sora2-network#593
• sora-xor/sora2-network#592
• sora-xor/sora2-network#591

DoD

Feel free to drop the guide as a comment. This way, we'll have the markdown file ready for easy integration into the documentation platform after the review. It'll make the process quicker and more convenient for everyone involved.

Useful materials:

• https://github.com/creyD/prettier_action
• https://mskelton.medium.com/auto-formatting-code-using-prettier-and-github-actions-ed458f58b7df

The current documentation lacks sufficient references to the actual blockchain codebase, resulting in a disconnect between the high-level descriptions and the technical implementation. It would be beneficial to include more references to support the high-level descriptions with specific technical implementation details. However, we should be cautious not to duplicate information found in the RUST documentation.

Q:

There is a "Changelog" page (https://raw.githubusercontent.com/sora-xor/sora-docs/develop/src/changelog.md) in the wiki that doesn't seem to contain much info. It's currently a part of the "Getting started" section, but I don't think it's relevant there. Maybe the Ecosystem chapter would be a better place for it? Also, it contains empty links, should they be updated?

A:

This should link to the SORA backend changelogs on git, I think we need some more work on these

A glossary is missing from the documentation, making it challenging for users to find concise definitions of keywords mentioned throughout the material. Adding an aggregated glossary page would greatly enhance the usability and accessibility of the documentation.

The documentation lacks an ecosystem overview that provides a clear architectural illustration of the main components, including the solo-chain, parachains, and other relevant projects. Including such an overview would greatly aid users in understanding the overall structure and relationships within the ecosystem.

Source: https://www.notion.so/Feedback-on-new-wiki-4f1ff00df89847b8a4e473ec5288088e

• #125

Our dear contributor Grug left the following feedback

1. JpGames tokens are burned.
   2)I can't find XST tokenomics.
   3)TBCD tokenomics and info are missing.
2. staking page is misleading. it doesn't tell anything about staking.
   5)Fearless wallet app page in wiki needs to mention that FW have not will have XOR staking. (With tutorial please).
   6)Please add an nice image of the wallet in this page. https://wiki.sora.org/ecosystem/sora-mobile-app

I have addressed the feedback in the old wiki, now it needs implementation on the new one

Hello,
It has been brought to our attention that segmenting the Polkaswap information could be difficult for new users, within the "Participate in the SORA Economy" section, can we please add a Polkaswap section that includes user guides, from inexperienced to advanced, similar to the structure in the old wiki?
Image attached,
Thank you.

The second part of the create-an-address.md file contains links to images that are either missing or incorrect. In #40 I've put comments around such instances for now, but it should be fixed properly.

https://docs.google.com/document/d/1AugYAY4IZTNN7agfmx8mhJhnyzwXG-IMW3XA4uupxNU/edit?usp=sharing