Added Aurora DeepSpeed content

[hatanp]

First draft for DeepSpeed on Aurora. Modified from Polaris instructions and tested to work.

[felker]

Suggested change

	for using / cloning the base environment can be found [here](../python.md).
	for using and cloning the base environment can be found [here](../python.md).

[hatanp]

To me "using and cloning" seems to imply the two are related. They are two separate topics. The slash was how it is in Polaris documentation. If words are preferred, then I would maybe go with "or"

[felker]

no need to overthink this one; go with whatever you find best.

instructions for both steps are found at that link, hence why I suggested "and"

IMO using "or" or "and" seems a bit more polished than "/" in our user docs, although I am guilty of using it from time to time

[felker]

I had a conversation with @saforem2 about the use of syntax highlighting for inline code markup like you use here with #!bash ...

We concluded that it isnt really worth the marginal gains for such short pieces of text, since it doesnt render in GitHub Flavored Markdown and has different escaping conventions.

Kinda degrades the readability when you are editing someone else's source text. Have you found it to be helpful?

[hatanp]

Unfortunately I am not following. This was just copied from Polaris docs and I did no changes to the formatting nor am I familiar with it. This looked fine and just like the Polaris docs when I rendered the document. Is the issue that this is hard to read in GitHub? What was the solution you concluded on in the discussion?

I have no opinion on how syntax highlighting should be implemented so feel free to propose changes as seems like both of you have better idea than I do. I do not have the skills to make educated choices on this. I just took something that was used before and worked in the rendered document.

[felker]

I am suggesting just using .deepspeed_env

[felker]

`.deepspeed_env`
instead of
`#!bash .deepspeed_env`

[felker]

https://squidfunk.github.io/mkdocs-material/reference/code-blocks/#highlighting-inline-code-blocks
this where the feature is discussed--- still can be useful for highlighting syntax for inline Python etc. but less useful for a single word Bash command or filename

[hatanp]

@saforem2 Did you have a chance to check this document? I just took whatever was in Polaris docs and modified it a bit so some details could have escaped me, so a second pair of eyes on this would be great. Also, looks like I did not receive any notifications from all the comments here and I now resolved a few. Thanks @felker!