The version switcher dropdown box mentiones releases, however currently
it refers to "master" which is not a release at all. I think we could
use the wording "version" which is more generic.

Archived versions instead is a link to releases on github. Changing the
wording accordingly.
Signed-off-by: NAndrea Frittoli <andrea.frittoli@gmail.com>

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

The modal in the interactive tutorials is difficult to navigate. I can not scroll (left to right) and (up and down) because of the embedded iframe.

Publishes a comprehensive overview of Tekton.

Instead, assume a cluster already exists, or briefly document using
`kind` to set up a local cluster for testing.

Update all Katacoda scenarios to run on Kubernetes 1.18, with
a 2 node cluster.

Fix some issues in the tasks and runs scenarios that seem to have
been undone in rebases before they were merged.

Update the Dashboard scenario to run the latest Pipeline and
Dashboard versions at time of writing.

Remove the use of the ingress in the Dashboard scenario since
it appears unstable on Katacoda with kubernetes 1.18. Using a
port-forward is sufficient for this scenario.

Add a Katacoda scenario that can act as a playground for users
to experiment with Tekton in a sandbox environment.

This environment provides a 2-node Kubernetes cluster with the
following projects installed:
- Pipelines v0.14.3
- Dashboard v0.8.2
- CLI v0.11.0

Typical startup time is <1minute, but may take 2 or 3 minutes
in some cases. The installation should not require any manual
steps by the user.

without --dry-run=client option, the create & replace command will fail.

Katacoda supports linking to images in the assets folder. Update our
existing links to use this approach instead of using the GitHub 'raw'
URLs as this gives us greater portability for the tutorials and ensures
the correct version of the images is loaded even if we stop loading content
from the `master` branch in future.

Tekton is a cloud native project, not necessarily a kubernetes native
project, and in fact (beyond basing our design around k8s style
resources and using k8s containers) we try to minimize our coupling to
k8s (at least in our API).

If you look at our README you can see that we are k8s-style and cloud
native: https://github.com/tektoncd/pipeline#-tekton-pipelines

You can see this reflected in our mission as well:
"Be the industry-standard, cloud-native CI/CD platform components and
ecosystem."
https://github.com/tektoncd/community/blob/master/roadmap.md#mission-and-vision

This commit updates the wording to be a bit more accurate.

- Moving the code from the decentralized to the centralized
- Create .vimrc in the background to cut down noise in the terminal
- Add a short delay before calling launch.sh to avoid intermittent failures with launch.sh not being ready
- Fix pipeline definition to ensure deploy runs after build
- Fix `kubectl expose` command since there's no deployment involved, just a pod
- Fix some lingering bad PipelineResource versions
Signed-off-by: NJJ Asghar <jjasghar@gmail.com>
Co-authored-by: Nmichaelawyu <michaelawyu@google.com>
Co-authored-by: NAlan Greene <alangree@ie.ibm.com>

Some of the Triggers content was moved in https://github.com/tektoncd/triggers/pull/642,
specifically: create-ingress.yaml and create-webhook.yaml

These have been moved to the getting-started folder which broke
the website sync script, blocking other changes.

Update the sync config to point to the new paths to unblock
other changes.

down in the docs

- Also updated the output from hello goodbye to goodbye world

As a user it is not straight forward on how to run the dev environment. I can not run the website locally without running npm, the sync script and hugo in a specific order. As a user it is also annoying to create an alias to run a makefile. I changed the makefile so that I do not have to make an alias. As a developer, I do not believe this is documented anywhere and following this guide will fix this issue. https://github.com/tektoncd/website/issues/3

- Moved over Brandow Walker's dashboard tutorial
- Created the basic pipeline tutorial
Signed-off-by: NJJ Asghar <jjasghar@gmail.com>
Co-authored-by: NBrandon Walker <bcwalker@ibm.com>

This achieves a few things:

1. Creates Dockerfile for sync tool, so that it can be invoked from
   Tekton tasks.
2. Makes sync config directory configurable by flag, so that the tool
   can be ran from any directory. This defaults to sync/config (same as
   before).

Symlinks are retainined in the root directory for requirements.txt and
runtime.txt to satisfy Netlify Build requirements:
https://docs.netlify.com/configure-builds/manage-dependencies/#python

Issue: #34

- Added a second task creation
- Added a pipeline example
- Added links back and forth from the page
Signed-off-by: NJJ Asghar <jjasghar@gmail.com>
Signed-off-by: NPaul Czarkowski <username.taken@gmail.com>
Co-authored-by: NPaul Czarkowski <username.taken@gmail.com>

As per user guide https://www.katacoda.community/git-repository-structure.html#scenarios
add a katacoda.yaml so that we may store katacoda scenarios in a
dedicated folder in the website folder.

Signed-off-by: NSteve Martinelli <stevemar@ca.ibm.com>

Signed-off-by: NSteve Martinelli <stevemar@ca.ibm.com>

Adds guidance for formatting lists.

For new users who want to start contributing the main doc contributers guide is not easy to find.

Fix a few typos in Concepts/_index.md

- Migrating from v1alpha1 to v1beta1
- Pipeline metrics
- Variable substitution

Changed `name` to `generateName` because of the behavior of the `--dry-run` of `tkn`.
Changed the `tkn` command for the logs at the end, because of the `generateName` is different per run.
Signed-off-by: NJJ Asghar <jjasghar@gmail.com>
Signed-off-by: NPaul Czarkowski <username.taken@gmail.com>

Changed from `apply` to `create` due to the declarative nature of `apply`. You can not use `generateName` with `apply`.
The error that happens is:

```
❯ kubectl apply -f taskRun.yml
error: error when retrieving current configuration of:
Resource: "tekton.dev/v1beta1, Resource=taskruns", GroupVersionKind: "tekton.dev/v1beta1, Kind=TaskRun"
Name: "", Namespace: "hello-world-pipeline"
from server for: "taskRun.yml": resource name may not be empty
```
The following is the correct behavior. 
```
❯ kubectl create -f taskRun.yml
taskrun.tekton.dev/echo-run-c5dtm created
```
Please look at:  https://github.com/kubernetes/kubernetes/issues/44501#issuecomment-294255660Signed-off-by: NJJ Asghar <jjasghar@gmail.com>

The banner for cd foundation and partners are off center after a certain size of 1739px. As a user this breaks the flow and decreases the usuability of the website.

Change broken CSS styles

The padding for the banners on the tekton webpage had incorrect max-widths and some strange padding.
As a user these changes improve the flow of the website.

add bg color to wrapper below container

The rendering on IOS mobile devices are different and causes the style to overridden on IOS devices. Removing the Copyright on the footer. Added the class for styles one element below to fix this issue

remove bootstrap styling

Fixes a spelling error on the landing page

It made sense for me to be in OWNERS file while we were releasing Beta
but I'm not on top of current website planning/work to review PRs.

Add support for a custom page param that can be used to point the
links in the sidebar to the correct project repos.

'Edit this page' will open the editor pointing to the correct file
in the project repo, instead of trying to find it in the website repo.

'Create an issue' will open the new issue UI in the target project repo.

Fixes username formatting.

Fixes more username formatting.

Move styles from _variables to _styles_project so it easier to maintain styles. Privacy notice banner was offset was not visible when site was docked to partial view. This allows a user to view the privacy notice properly. Add styling to takton banner hero logo. Logo breaks flow. Chaning the css to fix this issue. Added var to scss to increase readability.

Update the text to reflect the actual destination since we don't
currently have a try.tekton.dev subdomain.

The samples for the two 'Getting Started' links at the end of the main
Triggers page in the docs are missing so the links result in 404.

Add the YAML files to the sync config so they'll be included and available
from the links on the website.