ROCm platform installation guide
@sachinprasadhs When can we expect reaction on this issue? It can affect our team planning, that's why it would be nice to know. @MarkDaoust are you able to speak to this request or know who best to route it to?  > @MarkDaoust are you able to speak to this request or know who best to route it to?

@MarkDaoust can we get some feedbacks?  That will be my team. 

These files all come from the docs repo. You can submit changes there. 

https://github.com/tensorflow/docs/tree/master/site/en/install

But this does sound like a big enough change that we should probably give feedback early. 

Another layout that could be easier initially would be to add a rocm.md doc to the install section.

@joefernandez WDYT?
### Issue type

Documentation Feature Request

### Have you reproduced the bug with TensorFlow Nightly?

No

### Source

source

### TensorFlow version

master branch

### Custom code

No

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

We tried to write an email: https://github.com/tensorflow/tensorflow/issues/62784

I am currently working on ROCm documentation project as technical writer with @saadrahim and @lisadelaney. The AMD would like to extend the documentation with ROCm platform related information. The main areas, which first we would like to cover:

- install page: https://www.tensorflow.org/install/
- build from source [Linux] page: https://www.tensorflow.org/install/source
- pip install page: https://www.tensorflow.org/install/pip
- Docker install page: https://www.tensorflow.org/install/docker

Our goal is to keep the docs as clear and easy to navigate as is. Adding AMD GPU support to the docs may warrant minor structural changes. We are confident that we can devise a solution that satisfies all parties, but to minimize review bounces and implementation effort:

- Are there generic principles, or principles specific to this document to keep in mind (beside keeping the formatting and grammatical style intact)?
- Are changing these files sufficient or are there others files we have to update to streamline the upstream process?

Some of the things we keep in mind during contribution:

- Platform coverage initially will be narrower with AMD support. (No 1:1 mapping between CUDA/ROCm coverage.)
    - Document structure would somehow have to reflect this and be clear.
- The current docs conflate "GPU" support with "CUDA" support.
    - The install instructions (and with time other doc parts) would need to be clearer on what is related to offload acceleration and what is specific to vendors.

We already find the following page: https://www.tensorflow.org/community/contribute/docs

### Standalone code to reproduce the issue

```shell
I can't give you standalone code for this.
```


### Relevant log output

_No response_