-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #4 from huayuenh/translations
Update translations and fix translation strings in svg image
- Loading branch information
Showing
14 changed files
with
153 additions
and
181 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,49 +1,49 @@ | ||
| --- | ||
| template.name: "Develop and test microservices on Cloud Foundry~otc-ui863" | ||
| template.description: "With this cloud-native toolchain, you use a sample to create an online store that consists of three microservices: a Catalog API, an Orders API, and a UI that calls both of the APIs. The toolchain is preconfigured for continuous delivery, source control, functional testing, issue tracking, online editing, and alert notification.\n\nThe Catalog and Orders API are backed by a Cloudant store. As part of deploying this application, a no-cost Cloudant service instance is created. For more information and terms, see the [Bluemix catalog](https://console.ng.bluemix.net/catalog/services/cloudant-nosql-db/).\n\nThis toolchain uses tools that are part of the Continuous Delivery service. If an instance of that service isn't already in the selected resource group or organization, when you click **Create**, it is automatically added with the free [Lite](/catalog/services/continuous-delivery/) plan selected.\n\nTo get started, click **Create**.\n\nFor step-by-step instructions, follow the [tutorial](https://www.ibm.com/devops/method/tutorials/use-develop-test-microservices-on-cloud-foundry-toolchain).~otc-ui864" | ||
| template.gettingStarted: "**Your toolchain is ready!**\n**Quick start:** Commit a change to a Git repo to trigger a new build and deployment of one of the microservices. See results in the Deployment Risk dashboard in DevOps Insights. For step-by-step instructions, see the [tutorial](https://www.ibm.com/devops/method/tutorials/use-develop-test-microservices-on-cloud-foundry-toolchain?task=2) for this toolchain.~otc-ui865" | ||
| deploy.title: "Microservices deployment stage~otc-ui866" | ||
| deploy.description: "Microservices deployment schema~otc-ui867" | ||
| deploy.longDescription: "The Delivery Pipeline automates continuous deployment.~otc-ui868" | ||
| deploy.appName1: "Orders app name~otc-ui869" | ||
| deploy.appName2: "Catalog app name~otc-ui870" | ||
| deploy.appName3: "UI app name~otc-ui871" | ||
| deploy.appDescription1: "The name of the app for the Orders API~otc-ui872" | ||
| deploy.appDescription2: "The name of the app for the Catalog API~otc-ui873" | ||
| deploy.appDescription3: "The name of the app for the UI that calls the Orders and Catalog APIs~otc-ui874" | ||
| deploy.apiKeyDescription: "An API key is required to access the IBM Cloud Runtime. If you do not have one, you can click the Create button. You can also obtain an API key with 'ibmcloud iam api-key-create' or via the console at https://cloud.ibm.com/iam#/apikeys~otc-ui875" | ||
| deploy.apiKeyTitle: "IBM Cloud API key~otc-ui876" | ||
| region: "Region~otc-ui877" | ||
| organization: "Organization~otc-ui878" | ||
| space: "Space~otc-ui879" | ||
| prodStage: "Production stage~otc-ui880" | ||
| testStage: "Test stage~otc-ui881" | ||
| github.title: "Microservices deployment stage~otc-ui882" | ||
| github.description: "Microservices Git schema~otc-ui883" | ||
| github.longDescription: "With IBM hosted repos and issue tracking, you can store your source code in a new or an existing Git repository.~otc-ui884" | ||
| github.sourceRepository: "Source Repository~otc-ui885" | ||
| github.targetRepository: "Target Repository~otc-ui886" | ||
| headerSVG.think: "THINK~otc-ui887" | ||
| headerSVG.code: "CODE~otc-ui888" | ||
| headerSVG.deliver: "DELIVER~otc-ui889" | ||
| headerSVG.run: "RUN~otc-ui890" | ||
| headerSVG.learn: "LEARN~otc-ui891" | ||
| headerSVG.manage: "MANAGE~otc-ui892" | ||
| headerSVG.culture: "CULTURE~otc-ui893" | ||
| headerSVG.issueTracker: "ISSUE TRACKER~otc-ui894" | ||
| headerSVG.repository1: "REPOSITORY~otc-ui895" | ||
| headerSVG.repository2: "REPOSITORY~otc-ui896" | ||
| headerSVG.repository3: "REPOSITORY~otc-ui897" | ||
| headerSVG.webIde: "WEB IDE~otc-ui898" | ||
| headerSVG.pipeline1: "PIPELINE~otc-ui899" | ||
| headerSVG.pipeline2: "PIPELINE~otc-ui900" | ||
| headerSVG.pipeline3: "PIPELINE~otc-ui901" | ||
| headerSVG.bluemix: "BLUEMIX~otc-ui902" | ||
| headerSVG.ibmCloud: "IBM Cloud~otc-ui903" | ||
| headerSVG.slack: "SLACK~otc-ui904" | ||
| headerSVG.saucelabs1: "SAUCE LABS~otc-ui905" | ||
| headerSVG.saucelabs2: "SAUCE LABS~otc-ui906" | ||
| headerSVG.saucelabs3: "SAUCE LABS~otc-ui907" | ||
| headerSVG.pagerDuty: "PAGER DUTY~otc-ui908" | ||
| headerSVG.devops: "DEVOPS~otc-ui909" | ||
| headerSVG.insights: "INSIGHTS~otc-ui910" | ||
| template.name: "DevOps Insights Quick Start Demo~otc-ui1082" | ||
| template.description: "Start exploring Insights without any setup! This demo comes with pre-loaded data from our own reference toolchain and three example GitHub repos. The only thing you need is to log into IBM Cloud. \n\nThere are many features to explore. First, look at how we organize test, build, and deploy data for all applications, from all teams, within the Quality Dashboard. This collected information not only helps you to understand how well teams ensure quality for each release, it also lends to the transparency between different contributing teams. Second, evaluate trends and understand areas that need improvements so that you know where to best focus your resources. Lastly, review how team members collaborated per release within Team Dynamics.\n\nTo get started, click **Create**. This will take you to the DevOps dashboard where you can view the toolchain. From there, select the DevOps Insights card to explore Insights.\n\nFor step-by-step instructions, follow the [tutorial](https://www.ibm.com/devops/method/tutorials/explore-ibm-cloud-devops-insights).~otc-ui1083" | ||
| template.gettingStarted: "**Your toolchain is ready!**\n Click on the DevOps Insights card to explore the DevOps Insights features.~otc-ui1084" | ||
| deploy.title: "Microservices deployment stage~otc-ui1085" | ||
| deploy.description: "Microservices deployment schema~otc-ui1086" | ||
| deploy.longDescription: "The Delivery Pipeline automates continuous deployment.~otc-ui1087" | ||
| deploy.appName1: "Orders app name~otc-ui1088" | ||
| deploy.appName2: "Catalog app name~otc-ui1089" | ||
| deploy.appName3: "UI app name~otc-ui1090" | ||
| deploy.appDescription1: "The name of the app for the Orders API~otc-ui1091" | ||
| deploy.appDescription2: "The name of the app for the Catalog API~otc-ui1092" | ||
| deploy.appDescription3: "The name of the app for the UI that calls the Orders and Catalog APIs~otc-ui1093" | ||
| deploy.apiKeyDescription: "An API key is required to access the IBM Cloud Runtime. If you do not have one, you can click the Create button. You can also obtain an API key with 'ibmcloud iam api-key-create' or via the console at https://cloud.ibm.com/iam/apikeys~otc-ui1094" | ||
| deploy.apiKeyTitle: "IBM Cloud API key~otc-ui1095" | ||
| region: "Region~otc-ui1096" | ||
| organization: "Organization~otc-ui1097" | ||
| space: "Space~otc-ui1098" | ||
| prodStage: "Production stage~otc-ui1099" | ||
| testStage: "Test stage~otc-ui1100" | ||
| github.title: "Microservices deployment stage~otc-ui1101" | ||
| github.description: "Microservices Git schema~otc-ui1102" | ||
| github.longDescription: "GitHub repos, the following repos will be mined to obtain Team Dynamics data.~otc-ui1103" | ||
| github.sourceRepository: "Source Repository~otc-ui1104" | ||
| github.targetRepository: "Target Repository~otc-ui1105" | ||
| headerSVG.think: "THINK~otc-ui1106" | ||
| headerSVG.code: "CODE~otc-ui1107" | ||
| headerSVG.deliver: "DELIVER~otc-ui1108" | ||
| headerSVG.run: "RUN~otc-ui1109" | ||
| headerSVG.learn: "LEARN~otc-ui1110" | ||
| headerSVG.manage: "MANAGE~otc-ui1111" | ||
| headerSVG.culture: "CULTURE~otc-ui1112" | ||
| headerSVG.issueTracker: "ISSUE TRACKER~otc-ui1113" | ||
| headerSVG.repository1: "REPOSITORY~otc-ui1114" | ||
| headerSVG.repository2: "REPOSITORY~otc-ui1115" | ||
| headerSVG.repository3: "REPOSITORY~otc-ui1116" | ||
| headerSVG.webIde: "WEB IDE~otc-ui1117" | ||
| headerSVG.pipeline1: "PIPELINE~otc-ui1118" | ||
| headerSVG.pipeline2: "PIPELINE~otc-ui1119" | ||
| headerSVG.pipeline3: "PIPELINE~otc-ui1120" | ||
| headerSVG.bluemix: "IBM CLOUD~otc-ui1121" | ||
| headerSVG.ibmCloud: "IBM Cloud~otc-ui1122" | ||
| headerSVG.slack: "SLACK~otc-ui1123" | ||
| headerSVG.saucelabs1: "SAUCE LABS~otc-ui1124" | ||
| headerSVG.saucelabs2: "SAUCE LABS~otc-ui1125" | ||
| headerSVG.saucelabs3: "SAUCE LABS~otc-ui1126" | ||
| headerSVG.pagerDuty: "PAGER DUTY~otc-ui1127" | ||
| headerSVG.devops: "DEVOPS~otc-ui1128" | ||
| headerSVG.insights: "INSIGHTS~otc-ui1129" |
Oops, something went wrong.