Adds tabbed content, annotations, and admonitions

[Burhan-Q]

Overview

Proposal to some updates for new docs pages. Specifically for

• docs\getting_started\basic\install.md
• docs\getting_started\basic\virtualenv.md
• docs\fiftyone_concepts\running_environments.md

Apologies for the big PR. I intended originally to specifically add the tabbed content, but found several other areas that felt (to me) could use some attention.

Summary of Changes

• reordered markdown_extensions alphabetically
• included tabbed content to provide cleaner interface in documentation
• added annotations for interactive pop-out comments
• added frontmatter for keywords to help surface relevant content
• reordered OSes (only on these three pages) to maintain consistent order
• included install examples for uv
• changed syntax highlights to shell where appropriate
• changed syntax highlights to json where appropriate
• included examples for setting environment variables in multiple OSes
• added spaces in mkdocs.yml per yaml-lint errors (ignored other errors as it was not obvious that they needed to be fixed)
• added step numbers for connect to remote data steps
• removed $ and >>> from code blocks for consistency
• reformatted directory preview to use tree notation

Preview

Admonitions and Tabbed content (expand for screenshot)

Admonitions and Annotations (expand for screenshot)

[thesteve0]

@Burhan-Q Can you please make an edit to the code in the pr (say update a doc page or something). We just implemented functionality that should build the entire site based on this PR. Doing so will make it easier for us to review changes.

[Burhan-Q]

@thesteve0 added some white space, hopefully that helps

[Burhan-Q]

Sorry on mobile at the moment, but seems like there's a permission problem

remote: Permission to voxel51/voxel51-docs.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/voxel51/voxel51-docs.git/': The requested URL returned error: 403
Changes committed to the gh-pages branch… 📦
Running post deployment cleanup jobs… 🗑️
/usr/bin/git checkout -B github-pages-deploy-action/zp62jsw7x
Reset branch 'github-pages-deploy-action/zp62jsw7x'
/usr/bin/chmod -R +rw github-pages-deploy-action-temp-deployment-folder
/usr/bin/git worktree remove github-pages-deploy-action-temp-deployment-folder --force
Completed deployment successfully! ✅

Run marocchino/sticky-pull-request-comment@331f8f5b4215f0445d3c07b4967662a32a2d3e31
  
Error: Resource not accessible by integration

[thesteve0]

@tom-vx51 Looks like people outside 51 may get the permissions issue

[Burhan-Q]

Might need the token according to the GHA Readme

Authentication token for the preview deployment.
The default value works for non-fork pull requests to the same repository. For anything else, you will need a Personal Access Token with permission to access it, and store it as a secret in your repository. E.g. you might name that secret 'PREVIEW_TOKEN' and use it with token: ${{ secrets.PREVIEW_TOKEN }}.

Default: ${{ github.token }}, which gives the action permission to deploy to the current repository.

SOURCE

[Burhan-Q]

FWIW here's my fork permissions

[Burhan-Q]

Is the preview action working properly for repo maintainers? I tried using it on my fork (again, trying it all from mobile) and this was the result https://burhan-q.github.io/voxel51-docs/pr-preview/pr-2/ where the main on my fork deployed without issue.

[thesteve0]

It's a known issue you can't deploy from forks :( - we are investigating a solution that will allow for community builds

rossjrw/pr-preview-action#6

[Burhan-Q]

FWIW, I've attached screenshots of the locally deployed changes in this PR

Install

Details

Default tabbed content

Alternate tabbed content

Running Environments (long)

[thesteve0]

@Burhan-Q I have not forgotten this. Waiting on another PR to land before I test this. I think there are too many changes to merge all at once (though I do like them all). I just want to be a bit more deliberate about this.
I would like to see this as two separate PRs

1. The updated mkdocs.yml
2. The changes to content

[Burhan-Q]

I haven't had the time to, but I've been meaning to split this into smaller PRs. My concern with splitting the update to the mkdocs.yml is that content relying on those changes won't render correctly. I guess if it was split with the mkdocs.yml going first, it wouldn't be an issue.

I was thinking of splitting apart more by page or type of content update. That should make the PR less burdensome (I know the pain, I just had to review a +4000 line PR), but again I just haven't had the time to put into making the split.

[thesteve0]

No rush and yeah do the mkdocs first. I was about to make some of your changes myself and then I remembered your PR. Do you want me to take on those changes by blatantly stealing your work and then you can just focus on content updates?

[Burhan-Q]

Opened a PR with just a quick copy-paste of the mkdocs.yml changes. If there are issues or unwanted changes, please feel free to merge the changes in another PR and I will work on the content PRs when I have some time.

[Burhan-Q]

Splitting some of the updates out from this PR into #92

[thesteve0]

Handled in separate PRs