docs: Update repo and both package readme files

[JesseOlmer]

• Removes readme duplication
• Repo & Contribution guidelines exist exclusively in root repo readme
• Package readme's are thinned down to something which makes sense in an offline context as well (in the shipped package tarballs)
• Change MLAPI references to Netcode for GameObjects
• Remove MLAPI logo

[JesseOlmer]

Links to the rendered versions:

https://github.com/Unity-Technologies/com.unity.netcode.gameobjects/blob/f0e6d646e4bbeb3ecb16b37e0dce76e4c88ffa1a/README.md

https://github.com/Unity-Technologies/com.unity.netcode.gameobjects/blob/f0e6d646e4bbeb3ecb16b37e0dce76e4c88ffa1a/com.unity.netcode.gameobjects/README.md

https://github.com/Unity-Technologies/com.unity.netcode.gameobjects/blob/f0e6d646e4bbeb3ecb16b37e0dce76e4c88ffa1a/com.unity.netcode.adapter.utp/README.md

[Briancoughlin]

@JesseOlmer I have a question about the Transport Docs links. They are linking to our site but to the packages site, should it not link to us? The other links all go to our site , it seems odd to push multiplayer users of transport to a different site, and may lead to a more broken end to end user experience.

[JesseOlmer]

@JesseOlmer I have a question about the Transport Docs links. They are linking to our site but to the packages site, should it not link to us? The other links all go to our site , it seems odd to push multiplayer users of transport to a different site, and may lead to a more broken end to end user experience.

Right now our site doesn't have 1.0 docs, but the Unity docs site does. The Unity docs site is also the first search result for the package on every search engine I checked - if we want to not "break" end-user experience we should change those docs to point at the other site.

[Briancoughlin]

@JesseOlmer I have a question about the Transport Docs links. They are linking to our site but to the packages site, should it not link to us? The other links all go to our site , it seems odd to push multiplayer users of transport to a different site, and may lead to a more broken end to end user experience.

Right now our site doesn't have 1.0 docs, but the Unity docs site does. The Unity docs site is also the first search result for the package on every search engine I checked - if we want to not "break" end-user experience we should change those docs to point at the other site.

I have not written the 1.0 docs for transport so im not sure what those docs are?

[Briancoughlin]

@JesseOlmer I have a question about the Transport Docs links. They are linking to our site but to the packages site, should it not link to us? The other links all go to our site , it seems odd to push multiplayer users of transport to a different site, and may lead to a more broken end to end user experience.

Right now our site doesn't have 1.0 docs, but the Unity docs site does. The Unity docs site is also the first search result for the package on every search engine I checked - if we want to not "break" end-user experience we should change those docs to point at the other site.

I have not written the 1.0 docs for transport so im not sure what those docs are?

Problem solved ( these are auto generated by the package ) I'm doing an Index.md for transport similar to ours in Netcode that will stop the two sources of trust issue. I will talk to someone around the SEO for google search

[TwoTenPvP]

For future-proofing, we should change the shield URLs to point to Unity-Technologies/com.unity.netcode.gameobjects.

Perhaps also delete the download shield since that's not a relevant number as we go through the package registry now.

[JesseOlmer]

For future-proofing, we should change the shield URLs to point to Unity-Technologies/com.unity.netcode.gameobjects.

Perhaps also delete the download shield since that's not a relevant number as we go through the package registry now.

Good call on the shield URLs - fixed.
I removed the download count badge, but left in the release badge, as even though we'll be releasing through package registry I'd like us to continue to create github releases as well.