Reorganize the left navigation menu

[geriom]

Changes

To match the structure agreed on the documentation plan, this CL moves the imported documentation to its own section, "Reference".

• Netlify file updated to redirect old URLs to the new location.

• Dockerfile and docker-compose files updated to use nelitfy to run the site and mount the volumes in the correct locations.

• Sync script updated to match the new structure.

• New folders that will contain the API, and Installation documents are created as placeholders. To be populated later.

• .gitignore updated to exclude new directories.

Navigation comparison

New	Old

/closes #338

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you review them:

• [x] Includes docs (if user facing)
• [x] Commit messages follow commit message best practices

See the contribution guide for more details.

[tekton-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: To complete the pull request process, please assign geriom You can assign the PR to them by writing /assign @geriom in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/tektoncd/website/blob/main/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[geriom]

It seems I have to update the unit tests too. Added "work in progress" till it passes all the checks. Feel free to review what's currently here.

[tekton-robot]

@geriom: PR needs rebase.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[tekton-robot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale with a justification. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[geriom]

/lifecycle frozen

I'll do my best to come back to this before the end of the year. Either updating the sync script or exploring a different approach.

[tekton-robot]

@geriom: The lifecycle/frozen label cannot be applied to Pull Requests.

In response to [this](https://github.com/tektoncd/website/pull/395#issuecomment-1317516160): >/lifecycle frozen > >I'll do my best to come back to this before the end of the year. Either updating the sync script or exploring a different approach. Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[geriom]

/remove-lifecycle stale

[geriom]

Attempting a different approach in #502 Closing this one.