Add installation instructions to website

[geriom]

Changes

This adds the installation instructions to the website under the same
section, for visibility and ease of navigation. There's no new
information from what you can find on the repo docs for each component,
but the installation instructions are presented in a cohesive way,
following the same style and structure to provide a better experience
for the user.

This also fixes some minor formatting errors and updates links in the
"Getting started" tutorials.

/closes #4553

Docs Preview

Submitter Checklist

• Includes docs (if user facing)
• 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

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dibyom]

Can we elaborate what the correct permissions are?

[dibyom]

For the component specific installation pages, is it possible to have the pages in the projects themselves and pull the content from there? Otherwise, anytime a component's installation process changes , we'd have to update the website page separately.

[geriom]

Hmm... I recently submitted a PR to upstream Docsy that adds a shorcode to include the contents of one file into another. We can use that to have the Installation content under the same section while keeping it in the repo.

Thanks for the suggestions. I'll look into that.

[afrittoli]

Installation instructions must be versioned, same as the reference docs, so the instructions shown here must change when a different version is picked from the dropdown.

It may be possible to handle that through the sync script, but if we can get more native support in docsy that's even better.

I think the main disconnect between Tekton and Docsy is that Tekton has multiple components released independently, and I don't think Docsy natively supports that?

[geriom]

Docsy supports versioning but for the entire docset, not for individual files or folders. But we already have a shortcode for the synced docs, we can make something similar for the installation.

It may be possible to handle that through the sync script

I was going through the script to figure out the best way to do it. I think it should be possible with the current functions. I'll close this PR and come up with a solution after I'm done with a few other PRs I'm currently working on.