Use a simple scheduled github action to deploy
the website nightly. The deploy step includes sync,
so this will pull in an up to date version of the docs
on the master branch.

When an older version is selected, we still want to be able
to select the latest version. Alter the version switcher to
allow for that.
Signed-off-by: NAndrea Frittoli <andrea.frittoli@gmail.com>

Set the latest version of each component as the current one, add
everything else, including master, to the vault.
Remove the _index.md files that are brought in via sync.
Signed-off-by: NAndrea Frittoli <andrea.frittoli@gmail.com>

Hugo produces lowercase anchors into rendered markdown pages.
If a fragment points to a markdown page, make it lower case.
We do not touch fragments on external URLs or on github files
that are not markdown.

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

I think it's safe to say that Napoleon has gone above and beyond
anything we could have asked for help on this repo.

Thanks for everything, and here's to more!
Signed-off-by: NJJ Asghar <jjasghar@gmail.com>

For relative URLs that are not matched to a file on disk, we
rewrite them to a github URL. The base URL is joined to the
path with urljoin. If the the path includes a `..` then
urljoin goes up one level from the last `/` in the base URL.
Because of that, we need the base url to end with a `/`.
Added tests to avoid this from breaking in future.
Signed-off-by: NAndrea Frittoli <andrea.frittoli@gmail.com>

The previous logic parses URLs with a regex first and then using
the markdown library. It then uses urlopen().read() to validate
links.

We use now the markdown library only to extract the list of links,
and then urlparse to deconstruct, analyse, adapt and reconstract
the link. We do not attempt to fetch links anymore, which means
that external links are not guaranteed to be working.

Absolute URLs are not changed (they may be external)
Fragments are relative to the page and do not need changes
Path only links should point to a file synced to the website
but sometimes the file may be missing (if it's not in the sync
configuration), so we follow this approach:
- prefix with base_path and check for the file locally
- if not found, prefix with base_url instead

Note that urlparse treats URLs without scheme like path only
URLs, so 'github.com' will be rewritten to base_url/github.com
Signed-off-by: NAndrea Frittoli <andrea.frittoli@gmail.com>

Most of the time required for a sync is spent in two tasks:
- wget of all the original files
- validating the URLs with urlopen().read()

Running those two tasks in parallel greatly reduces the
processing time. This will be even more relevant when syncing
files from multiple releases.
Signed-off-by: NAndrea Frittoli <andrea.frittoli@gmail.com>

Add a new python script that can be used to add a new version to
the configuration of a component.
This script can be used by various projects as part of their
release process to keep the version on the website up-to-date.
Signed-off-by: NAndrea Frittoli <andrea.frittoli@gmail.com>

Cleanup typos, simplify logic in a few places.
Make the list of files config a dict instead of a list of dicts.
Signed-off-by: NAndrea Frittoli <andrea.frittoli@gmail.com>

As a developer, it is difficult to make changes to a script and ensure that nothing is broken without tests. Test are added in this patch with 80% code coverage. The script has also been refactored to increase readability. This refactor is not a pure refactor. The sync did not work properly. There is a list of bugs that reported the script generating broken links, #160, #126, #158, #133, #134. This refactor also includes a patch that fixes these bugs. The patch redirects a user to github if there is a relative link to a file that does not exist. This is important because some links will reference a snippet of code, test, or example. These artifacts are not docs, they are not rendered properly on the site. It is better to redirect the user to the intended artifact if the file is not synced. This prevents random 404s, and preserves the original behavior of the sync script. There are other approaches to fix this bug. This includes, manually editing links, downloading the files that the broken link are referencing in the sync config file, or removing the broken links. This is the best approach because broken links are automatically fixed and do not require manual intervention. This approach causes a side effect of not requiring the config file to be up-to date because the script will redirect the user to github. We want to encourage frequent sync. So eventually, this script should become tekton-ified (tekton task) and placed into the tekton catalog repo. Sync needs to become a tekon task in order for every repo to sync docs on push event.

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>