This blog is imported from https://opensource.googleblog.com/2023/03/getting-to-slsa-level-2-with-tekton-and-tekton-chains.html

Signed-off-by: NAndrea Frittoli <andrea.frittoli@gmail.com>

This blog post announces the upcoming event, cdCon + GitOpsCon 2023
together with the list of talks about Tekton.

Add instructions to embed code samples from external files in the
documentation.

- Create new partial to display links to the Nightly and  LTS release.
- Disable breadcrumb and use that space for the links.

- Refactor config file for legibiltiy
- Write new menu logic to pick manual menu from config file
- Replace spaces with dashes in folder names

This is the first PR adding vendor-specific documentation.

- Refactor installation docs to make it simpler with tabs for generic
  instructions, Google cloud, and Openshift. This is a multi-PR change.
  The actual installation doc is created on the Pipelines repo and
  rendered on the website.

- Update the build and push how-to with instructions to authenticate to
  Google Artifact Registry.

- Create a new shortcode to commenting out text in the markdown file.

Fix a simple grammatical mistake

change "tekton-triggers-core-controller" to "tekton-triggers-core-interceptors"

Typo fixes and small quality of life improvements:

- Typo in heading sentence in triggers getting started
- Update links in landing page
- Add scrolling and margin to version selector.
- Typo in community page, misson instead of mission
- Add vertical scrolling to extra-long code samples.
- RSS button styles to match other buttons styles.

Create a new entry for blog posts in the contribution guidelines
section.

Signed-off-by: NAndrea Frittoli <andrea.frittoli@gmail.com>

Signed-off-by: NAndrea Frittoli <andrea.frittoli@gmail.com>

Create the blog folder for the Tekton website.

Bup docsy version and comment out jinja2 code in vendor guidelines.

Some highlights about this new Docsy version:

- Better styles for tabs
- Improved readfile shortcode rendering
- Consistent code block styles

Community page with links to guidelines, communication channels and the
community repository.

Fixing a small typo which breaks the How-to Guide if followed blindly/copy-pasted.
The documentation refers to `pipeline,yaml` in line 49, but I believe it should be referring to `pipeline.yaml` ( using a punctuation instead of a comma ).

- Add contribution guidelines for platform specific docs
- Simplify existing contribution guidelines

This new section surfaces the installation documentation for all the
Tekton components.

This first iteration adds Pipelines and Triggers, more work is required
for other components docs to be included here.

- Add new beginners tutorial for Triggers.
- Modify Pipelines example to use one parameter.
- Make some editorial changes to the previous tutorials.

Tekton Pipelines currently does not install on Kubernetes 1.25 due
to use of some deprecated resources that have been removed in that
release. Pin the version used for the `minikube start` command so
users following the tutorial have a working environment.

To avoid having to delete and reapply a Pipelinerun when developing your
code, this PR switches to `generateName`, which adds a suffix to have a
unique name each time.

Additionally, this PR also fixes a problem with the latest version of
the `git-clone` Task in the Git clone tutorial.

Recently, the git-clone task was updated to version 0.8 which is not
backwards compatible in that it is run as a non-root user which does not
have access to volumes mounted via workspaces by default. To accomodate
this change, the users need to update their PipelineRuns and TaskRuns
with `podTemplate.securityContext.fsGroup = 65532` to fix the
permissions on mounted volumes.

This commit makes this configuration change in the how-to guide.

Based on feedback, this commit:

-  Explicitly mention in the installation instructions that `tkn` is the
   command name of the Tekton CLI.

-  Provide a better description of when the installation of Tekton
   Pipelines is complete. Namely, when both tekton-pipelines-controller
   and tekton-pipelines-webhook are `READY`.

-  Consistent capitalization of "Task", "TaskRun", "Pipeline",
   "PipelineRun", "Workspace", and "Step". Since these are first class
   objects with a specific meaning meaning within Tekton, we treat them
   as nouns when writing docs.

Fix typographical errors in the code samples.

Correct mis-typed name of desired `pipelineRef`.

A tutorial that shows how to create a Tekton Pipeline to build and push
an image with Kaniko.

Create a new section for how-to's. This section will include end-to-end
guides for common tasks. The first one is how to create a Pipeline to
clone a repository.

Add most recent release `v0.26.x` and `main` as the only options for
now as we've updated the structure and links to ensure they work
correctly on both GitHub and the website.

Include a series of introductory videos that can be very helpful for
many new users.

Closes https://github.com/tektoncd/website/issues/366

- [x] tekton.dev home page
	- [x] Get started with interactive tutorials' which links to https://tekton.dev/try/
		- Update the link text to: 'Get started with Tekton.'
		- Update the URL to point to our new tutorial: `https://tekton.dev/docs/getting-started/`
- [x] 'Try Tekton' block towards the bottom of the page which links to the Katacoda playground scenario
	- Update the text to: 'Learn, explore, and experiment with Tekton by following the tutorial.'
	- Make the word 'tutorial' a link with URL pointing at `https://tekton.dev/docs/getting-started/`
- [x] 'Try' link in the site header which also links to `https://tekton.dev/try/`
	- remove the link, page, and associated content

This commit makes some updates to the concepts informations:

- Update the navigation to keep the conceptual information under the
  "Concepts" section, including the main Overview.

- Delete references to deprecated PipelineResources.

- Update path for images to be absolute instead of relative. In some
  documents relative paths don't render correctly.

Alpine containers don't have bash, so need to change the first line.