Hello,

Helion thanks for take your time to clone it. The issue you mention is registered in Issues section, if your using mobile to solve it just reload and it will be relocated correctly.

PR's welcome

Remember that the proposal covers the work done and improvements for the next 6 months. Thanks

And for those who are in the middle or feel the map isn't sufficiently understandable, I'll share two things:

1.The structure was personally reviewed by renowned ecosystem engineers (Shawn, Kian, Rad, and others). If that's still not enough for you, I invite you to open all the links to the elements, read their content, and count how long it takes you to do that task.

2.Then put yourself in the position of a developer who wants to start their journey with Polkadot (for example, at a hackathon) and you'll see how the map helps you understand all the elements more clearly and in less time. Including the programming languages used (in the repositories where they are available). All of this is translated into eight languages.

I hope this clarification allows you to reconsider your vote. Best regards.

@SIM-DOT Thanks for your explanation.

1. I struggle to understand its necessity considering we have a detailed polkadot wiki and some awesome serious repos which we can search resources.
2. I 100% understand your efforts on it and appreciate your work, but I think the treasury should fund a good enough work which can really help developers. I'd prefer to other resources like polkadot wikis to the chart on the proposal.
3. I think these kinds of work need long term maintenance to keep it updated in time. So maybe it'll be more acceptable if this work can be merged to some other well maintained resources like polkadot wiki.

During conversations with members of the W3F, it was shared that the map should not replace the Polkadot Wiki and could be included among the official resources, but like many things in Open Source, everything starts with an idea, an effort to generate something tangible and then improve it. In my case, I'm not part of any organization in the ecosystem, so everything has been entirely voluntary, and I hope that effort is valued.

And as a developer, there's a great need for developers to have a broad and quick overview of the components (of which there are many) that exist in Polkadot, so they have an additional resource that allows them to decide where to focus their efforts.

This is part of the developer experience, and here's an example: when a developer looks for a position in a company or project, they search for the available position and select the one that interests them most. That posting typically mentions the category of work to be done: whether it's frontend, backend, mobile, infrastructure, and the programming languages used. What doesn't happen is that they tell them they have to review every area of the company, every project, and all the documentation.

Developers go directly to where they can contribute, and the easier that process is, the better the experience will be. That's what we're trying to convey to developers with this work, which has been going on for some time and which we hope to continue improving with everyone's support.