This repo contains the content for Tanzu Application Platform docs.
Branch | Staging | Production |
---|---|---|
main | Staging (Pre-release v1.5 docs) | n/a |
1-4-2 | Staging (Pre-release v1.4.2 docs) | n/a |
1-4-1 | Staging | Production |
1-4-0 | Not in use. Do not PR to this branch. | Not in use. Do not PR to this branch. |
1-3-5 | Staging | Production |
1-3-4 | Not in use. Do not PR to this branch. | Not in use. Do not PR to this branch. |
1-3-3 | Not in use. Do not PR to this branch. | Not in use. Do not PR to this branch. |
1-3-2 | Not in use. Do not PR to this branch. | Not in use. Do not PR to this branch. |
1-3-1 | Not in use. Do not PR to this branch. | Not in use. Do not PR to this branch. |
1-3-0 | No longer in use. Do not PR to this branch. | No longer in use. Do not PR to this branch. |
1-2-2 | Staging | Production |
1-2-1 | No longer in use. Do not PR to this branch. | No longer in use. Do not PR to this branch. |
1-2-0 | No longer in use. Do not PR to this branch. | No longer in use. Do not PR to this branch. |
1-2 | No longer in use. Do not PR to this branch. | No longer in use. Do not PR to this branch. |
1-1 | Staging | Production |
1-0 | Staging | Production |
Some components have docs that introduce them in this repository, but the rest of their docs are stored in dedicated repositories.
Component | Repo |
---|---|
API Auto Registration | https://gitlab.eng.vmware.com/tap-api-first/api-auto-registration |
API portal | https://github.com/pivotal-cf/docs-api-portal |
Carvel | https://github.com/vmware-tanzu/carvel/tree/develop/site/content |
Cloud Native Runtimes | https://gitlab.eng.vmware.com/daisy/cloud-native-runtimes-for-vmware-tanzu |
Services Toolkit | https://gitlab.eng.vmware.com/services-control-plane/documentation |
Spring Cloud Gateway | https://github.com/pivotal-cf/docs-scg-k8s |
Tanzu Build Service | https://github.com/pivotal-cf/docs-build-service/tree/v1.5 |
Use the complete product name at first use:
- Cloud Native Runtimes for VMware Tanzu
- Application Accelerator for VMware Tanzu
- Application Live View for VMware Tanzu
- VMware Tanzu Build Service
And thereafter:
- Cloud Native Runtimes
- Application Accelerator
- Application Live View
- Tanzu Build Service (not Services)
- Tanzu Application Platform (not TAP)
Use this table to keep a running list of terms used and how they should be defined.
Word or phrase | Explanation |
---|---|
API Auto Registration | Both Auto and Registration are separated from each other, and capitalized |
API portal | The p is supposed to be lowercase. Pull request #73. |
components | The individual products available in the TAP SKU. For example, Cloud Native Runtimes is a component of TAP. Not: add-ons or capabilities. |
convention controller | Lowercase; this is one of the minor components that make up Convention Service |
convention server | Lowercase; this is one of the minor components that make up Convention Service |
Convention Service | Title case; this is a component with its own TanzuNet product page |
Default Supply Chain | singular |
kubectl | First use in a topic: Kubernetes command-line tool (kubectl). Subsequent uses: kubectl. |
Tanzu Insight | This CLI plug-in is named simply Insight in the v1.0 documentation because it is separate from the Tanzu CLI |
packageRepository | Is a definition. Variations found in original doc (Package repository, PackageRepository, packagerepository) but standardize on the one shown. 2021.08.26 |
PackageRepositories | Don't use. There is really only one packageRepository of interest for this page. |
packageRepository custom resource | Because we don't use CR in other Kubernetes docs, spell out custom resource here too. An example of the packageRepository custom resource is given in the YAML file named tap-package-repo.yaml . |
packageRepository pull | Just means pulling the packages from the repository |
Services Toolkit for VMware Tanzu | (First use in body text) No longer Services Control Plane Toolkit 2021.10.26 Ed Cook |
Services Toolkit | (In headings and after first use in body text) No longer SCP Toolkit 2021.10.26 Ed Cook |
Source Controller | Title case; this is a component with its own TanzuNet product page |
Supply Chain Security Tools - Store | Not SCST - Store |
Supply Chain Security Tools - Scan | Not SCST - Scan |
Tanzu Application Platform GUI | Not Tanzu Application Platform Graphical User Interface, nor TAP GUI, nor TAP UI, etc. Also not "the Tanzu Application Platform GUI" because Tanzu Application Platform GUI is considered a product name. |
Tanzu Developer Tools for IntelliJ | The long form is VMware Tanzu Developer Tools for IntelliJ. It can be referred to as "the extension" in a topic after introducing it as "the Tanzu Developer Tools for IntelliJ extension" when there is no risk of confusion. |
Tanzu Developer Tools for Visual Studio | The long form is VMware Tanzu Developer Tools for Visual Studio. It can be referred to as "the extension" in a topic after introducing it as "the Tanzu Developer Tools for Visual Studio extension" when there is no risk of confusion. |
Tanzu Developer Tools for VS Code | The long form is VMware Tanzu Developer Tools for Visual Studio Code. It can be referred to as "the extension" in a topic after introducing it as "the Tanzu Developer Tools for VS Code extension" when there is no risk of confusion. |
Tanzu Kubernetes Grid | Never use TKGm or TKG in customer facing documentation. |
TAP repo bundle | Decided on lowercase and not "TAP Repo Bundle". |
TAP packages | Right now there are three packages: one for each component. The three packages make up the bundle. The bundle is stored in the the TAP package repository. Although "Tanzu Application Platform packages" is in the original google doc, let's use "TAP packages" for consistency. |
TAP package repository | How is this different from the other package repositories? (Are there non-TAP package repositories discussed on this page?) Changed from TAP to Tanzu Application Platform, Sept 24, 2021. |
.yaml and YAML file | Standardize on using the "a", not .yml |
Full Name | Short Name |
---|---|
API Auto Registration | API Auto Registration |
API portal for VMware Tanzu | API portal |
API Scoring and Validation | API Scoring and Validation |
Application Accelerator for VMware Tanzu | Application Accelerator |
Application Live View | Application Live View |
Application Single Sign-On for VMware Tanzu | Application Single Sign-On |
Cartographer Conventions | Cartographer Conventions |
cert-manager | cert-manager |
Cloud Native Runtimes for VMware Tanzu | Cloud Native Runtimes |
Contour | Contour |
Convention Service for VMware Tanzu | Convention Service |
Developer Conventions | Developer Conventions |
Eventing | Eventing |
FluxCD Source Controller | FluxCD Source Controller |
Tanzu Learning Center | Learning Center |
Namespace Provisioner | Namespace Provisioner |
Service Bindings | Service Bindings |
Services Toolkit for VMware Tanzu Application Platform | Services Toolkit |
Source Controller | Source Controller |
Spring Boot conventions | Spring Boot conventions |
Spring Cloud Gateway for Kubernetes | Spring Cloud Gateway |
Supply Chain Choreographer | Supply Chain Choreographer |
Supply Chain Security Tools for VMware Tanzu - Policy Controller | Supply Chain Security Tools - Policy Controller (SCST - Policy Controller) |
Supply Chain Security Tools for VMware Tanzu - Scan | Supply Chain Security Tools - Scan (SCST - Tools) |
Supply Chain Security Tools for VMware Tanzu - Sign | Supply Chain Security Tools - Sign (SCST - Sign) |
Supply Chain Security Tools for VMware Tanzu - Store | Supply Chain Security Tools - Store (SCST - Store) |
Tanzu Application Platform GUI | Tanzu Application Platform GUI |
Tanzu Application Platform Telemetry | Tanzu Application Platform Telemetry |
Tanzu Build Service | Tanzu Build Service |
VMware Tanzu Developer Tools for IntelliJ | Tanzu Developer Tools for IntelliJ |
VMware Tanzu Developer Tools for Visual Studio | Tanzu Developer Tools for Visual Studio |
VMware Tanzu Developer Tools for Visual Studio Code | Tanzu Developer Tools for VS Code |
VMware Tanzu Application Platform Pipeline service with Tekton | Tekton Pipelines |
Component names usage:
- Use the short component name in the Table of Contents, Release Notes headings, and Components page headings.
- Call out the full name where one exists on the first occurrence in the component page description and the first occurrence in the actual component doc and then use the short name elsewhere.
Exception for Supply Chain Security Tools:
- As above, use the short name in the Table of Contents, Release Notes headings, and Components page headings.
- As above, call out the full name on the first occurrence in the component page description and the first occurrence in the actual component doc, however as even the short name is very long, use the acronym after this.
Placeholder | Definition |
---|---|
TANZU-NET-USER and TANZU-NET-PASSWORD |
Where TANZU-NET-USER and TANZU-NET-PASSWORD are your credentials for Tanzu Network |
PACKAGE-REPO-NAME |
Where PACKAGE-REPO-NAME is the name of the packageRepository from step 1 above. |
VERSION |
Where VERSION is the version of the package listed in step 7 |
Top tips:
- Keep line lengths short, around 110 chars.
- Start each sentence on its own line. Markdown only creates new paragraphs after a blank line.
- We've changed our heading style to match the more modern style: sentence case not title case. So going forward, we only need to capitalize the first word in a title. E.g. "Other style stuff" instead of "Other Style Stuff."
- UI elements are bolded and the widget type not mentioned.
For example, "Click on the
NEXT STEPS
button." is rewritten as "Click NEXT STEPS." - Outside of code, Kubernetes API objects are written in lowercase and the words are separated by spaces, like for other common nouns. This is in contrast to the Kubernetes docs, where upper camel case is sometimes used and sometimes not.
If a doc file is autogenerated, any direct edits are overwritten at the next autogeneration event. The files in these folders are autogenerated:
- scst-store/cli_docs
Problem | List displays as a paragraph |
---|---|
Symptom: | Bulleted or numbered lists look fine on GitHub but display as a single paragraph in HTML. |
Solution: | Add a blank line after the stem sentence and before the first item in the list. |
Problem | List numbering is broken: every item is 1. |
---|---|
Symptom: | Each numbered item in a list is a 1. instead of 1. , 2. , 3. , etc |
Solution: | Try removing any blank newlines within each step. |
Problem | Code boxes not showing |
---|---|
Symptom: | VMware publishing system doesn't accept code tags after the three back ticks. |
Solution: | Make sure you're not using shell or bash or console or yaml after back ticks. |
To create a pull request, see Creating pull requests and merge requests in Confluence.
Staging docs:
- docworks is the main tool for managing docs used by writers.
- docsdash is a deployment UI which manages the promotion from staging to pre-prod to production. The process below describes how to upload our docs to staging, replacing the publication with the same version.
- Markdown files live in this repo.
- Each page requires an entry in toc.md for the table of contents.
- Images should live in an
images
directory at the same level and linked with a relative link.
Starting from the repo root, this will create a new docs.zip
with no root folder and show its
contents.
git pull ; rm *.zip ; zip -r tap-1-0 *
- Go to https://docworks.vmware.com/md2docs/publish
- Fill in the fields exactly as below. Repeat this every time - the browser can help to remember form fields.
- Click on upload, and when prompted, enter your VMware AD password (for docsdash)
- If you see invalid path errors in the yellow box on the right there are broken links, but the site will still be published.
- If the toc.md is invalid then the site will not build, but there will be no indication that something is wrong.
Form fields for beta-1: VMwarePub.yaml Form fields for main (beta-2?): VMwarePub.yaml
-
Wait about 1 minute for processing to complete after uploading.
-
Go to https://docsdash.vmware.com/deployment-stage
There should be an entry with a blue link which says
Documentation
and points to staging.
Prerequisite Needs additional privileges - reach out to Paige Calvert on the docs team #tanzu-docs or ask a writer to do this step for you.
-
Go to Staging publications in DocsDash https://docsdash.vmware.com/deployment-stage
-
Select a publication (make sure it's the latest version)
-
Click Deploy selected to Pre-Prod and wait for the pop to turn green (refresh if necessary after about 10s)
-
Go to Pre-Prod list https://docsdash.vmware.com/deployment-pre-prod
-
Select a publication
-
Click Sign off for Release
-
Wait for your username to show up in the Signed off by column
-
Select the publication again
-
Click Deploy selected to Prod
General information about landing pages:
- Every product has a landing page (Not exactly true: every umbrella product, such as Tanzu Application Platform should have a landing page.)
- The landing page is a container for all the "publications" for a product.
- Typically there will be a new docs publication for each minor release but not each point release.
This version number become part of the URL e.g. Our first release was version
0.1
(see form section above for the current release). - Some products, such as Tanzu Kubernetes Grid, publish separate release notes publications for each point release.
- For comparison see https://docs.vmware.com/en/VMware-Tanzu-Application-Catalog/index.html
For information about how we use partials, see our Working with partials Confluence page.