New Crowdin translations

src/pages/da/api.md

@@ -0,0 +1,7 @@
+---
+template: api-index
+---
+
+# API Index
+
+Each Ionic [component](/docs/components) consists of one or more [custom elements](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements). Each custom element, in turn, may expose properties, methods, events, and CSS custom properties.

src/pages/da/appflow.md

@@ -0,0 +1,37 @@
+---
+title: Welcome to Appflow
+---
+
+Appflow is a continuous integration (CI) and continuous deployment (CD) platform for Ionic development teams. Appflow helps development teams continuously build and ship their iOS, Android, and web apps faster than ever.
+
+<docs-cards class="static-width"> <docs-card header="Quickstart" href="/docs/appflow/quickstart/connect" img="/docs/assets/icons/guide-quickstart.png"> 
+
+Get your app set up with multiple environments that automatically build new binaries for iOS and Android and provide real time updates for your users instantly every time your team commits new code.</docs-card>
+
+<docs-card header="Deploy" href="/docs/appflow/deploy/intro" icon="/docs/assets/icons/guide-deploy-icon.png"> 
+
+Provide live updates and hotfixes to user devices instantly without going through the app stores.</docs-card>
+
+<docs-card header="Package" href="/docs/appflow/package/intro" icon="/docs/assets/icons/guide-package-icon.png"> 
+
+Build native iOS and Android binaries in the cloud without the headache of maintaining your own build servers.</docs-card>
+
+<docs-card header="Automate" href="/docs/appflow/automation/intro" icon="/docs/assets/icons/guide-automate-icon.png"> 
+
+Automate your Deploy and Package builds to help you team ship better updates faster.</docs-card>
+
+<docs-card header="News & Updates" href="https://ionic.zendesk.com/hc/en-us/categories/360000410554-Announcements" icon="/docs/assets/icons/guide-news-icon.png"> 
+
+Learn about recent Appflow updates & announcements.</docs-card>
+
+<docs-card header="Package FAQ" href="https://ionic.zendesk.com/hc/en-us/categories/360000410494-Package" icon="/docs/assets/icons/guide-faq-icon.png"> 
+
+Find answers to common questions about building native binaries.</docs-card>
+
+<docs-card header="Deploy FAQ" href="https://ionic.zendesk.com/hc/en-us/categories/360000409113-Deploy" icon="/docs/assets/icons/guide-faq-icon.png"> 
+
+Find answers to common questions about live updates.</docs-card>
+
+<docs-card header="Billing FAQ" href="https://ionic.zendesk.com/hc/en-us/categories/360000410574-Billing-Support" icon="/docs/assets/icons/guide-faq-icon.png"> 
+
+Find answers to common billing questions.</docs-card> </docs-cards>

src/pages/da/appflow/automation/create.md

@@ -0,0 +1,69 @@
+---
+previousText: 'Introduction'
+previousUrl: '/docs/appflow/automation/intro'
+nextText: 'Environments'
+nextUrl: '/docs/appflow/automation/environments'
+---
+
+# Using Automations
+
+## Managing Automations
+
+Creating and customizing automations is simple. To get started, navigate to the `Automate` tab within the desired app.
+
+To **create a new automation**, click the `New Automation` button on the top right of the `Automate` dashboard. When clicked, the automation customization form will appear, which has several fields available to customize the automation (Read more about these [below](#customizing-automations)).
+
+To **edit an automation**, click the three dots next to the one you'd like to modify.
+
+## Customizing Automations
+
+There are a number of customizations available to specify the specific behavior of a given automation. They are shown on the create/edit automation form below.
+
+### Basic Automation Info
+
+All automations need a name and git branch to trigger from. Whenever code is pushed to the selected branch, the automation will run.
+
+![Choosing an Automation Type](/docs/assets/img/appflow/ss-automation-create-type.png)
+
+#### Fields
+
+* **Name:** A name to identify the automation task.
+* **Git Branch:** The branch which will trigger the automation. This will run a build any time a `git push` is made to the specified branch.
+* **Automation Type:** The type of job this automation will run.
+
+In addition to name and git branches, automations have a number of customizations available depending on the type of job selected.
+
+##### Note about Git Branch naming
+
+It is possible to specify one or multiple `*` wildcards character to match multiple branches within a single automation; for instance:
+
+* a branch simply set to `*` will match all the branches and will trigger the automation for any single git push
+* a branch set to `dev*` will match any branch with a name starting with `dev` including `dev` itself
+* a branch set to `dev*other` will match any branch with a name starting with `dev` and ending with `other` including `devother`
+
+### Package Automations
+
+Package automations create native builds which can be downloaded and run on devices. They have the following customizations:
+
+![Creating a package automation](/docs/assets/img/appflow/ss-automation-create-package.png)
+
+#### Fields
+
+* **Environment:** The [custom build environment](/docs/appflow/environments/#custom-environments) (if any) to use when this automations is triggered.
+* **Native Config:** The [native config](/docs/appflow/package/intro#native-configs) (if any) to use when this automations is triggered.
+* **Target Platform:** The platform being targeted, can be Android or iOS (for either Xcode 8 or 9)
+* **Build Type:** The type of build to create. Options depend on the selected platform.
+* **Security Profile:** Which security profile to use. Learn more about them [here](/docs/appflow/package/credentials).
+* **Webhook:** (optional) If specified, a POST with information about completed builds will be sent to the entered URL. Learn more about their content [here](/docs/appflow/automation/webhooks).
+
+### Web Automations
+
+Web automations build the javascript portion of an application and interface with the [Deploy](/docs/appflow/deploy/intro) service to enable live app updates.
+
+![Creating a web automation](/docs/assets/img/appflow/ss-automation-create-web.png)
+
+#### Fields
+
+* **Environment:** The [custom build environment](/docs/appflow/environments/#custom-environments) (if any) to use when this automations is triggered.
+* **Channel:** The [Deploy Channel](/docs/appflow/deploy/channels) where web builds from this automation will be assigned.
+* **Webhook:** (optional) If specified, a POST with information about completed builds will be sent to the entered URL. Learn more about their content [here](/docs/appflow/automation/webhooks).

src/pages/da/appflow/automation/environments.md

@@ -0,0 +1,108 @@
+---
+previousText: 'Create Automations'
+previousUrl: '/docs/appflow/automation/create'
+nextText: 'Webhooks'
+nextUrl: '/docs/appflow/automation/webhooks'
+---
+
+# Build Environments
+
+## Introduction
+
+Environments give you a way to customize the build process for your application in order to produce different versions of your applications for different environments from the same code base. All environment variables are accessible to any build scripts that run during the `npm run install` and `npm run build` portion of your builds.
+
+There are two types of Enviornment variables available to use:
+
+* [Predefined Environments](#predefined-environments) (Available on all Builds)
+* [Custom Environments](#custom-environments) (Available on select plans)
+
+## Predefined Environments
+
+Every time a Build occurs, it's done in a secure environment where we provide some predefined variables which are key/value pairs that are made available in the environment and are available by using [process.env.MY_VAR](https://nodejs.org/docs/latest-v8.x/api/process.html#process_process_env) syntax in NodeJS or via `$MY_VAR` syntax in a standard shell script. These variables can be leveraged to [customize the build and outputs](#usage).
+
+The following environment variables are provided in every build, which can be accessed in build scripts:
+
+* `CI_APP_ID` **(string):** Your Ionic app's unique ID.
+* `CI_APP_NAME` **(string):** Your Ionic app's name.
+* `CI_AUTOMATED_BUILD` **(int):** Whether this build occurred as a result of an automation (`0` for `false`, `1` for `true`).
+* `CI_AUTOMATION_ID` **(optional int):** The unique ID of the automation which created this build.
+* `CI_AUTOMATION_NAME` **(optional string):** The name of the automation which created this build.
+* `CI_GIT_COMMIT_SHA` **(string):** The SHA for the commit on which the build was run.
+* `CI_GIT_COMMIT_MSG` **(string):** The message for the commit on which the build was run.
+* `CI_GIT_REF` **(string):** The git ref from which the build was created (i.e. `master`).
+* `CI_GIT_REF_TYPE` **(string):** The git ref type (i.e. `branch`).
+
+## Custom Environments
+
+<blockquote>
+  <p><b>Note:</b>This feature is only available on our <a href="/pricing">Growth plans</a> and above.</p>
+</blockquote>
+
+In addition to the [predefined environments](#predefined-environments), customers on the [plans with access to automations](/pricing) will have access to create custom environments. With custom environments it's easy to create and manage custom sets of key/value pairs to further customize builds on Ionic Appflow. Common use cases include customizing your build process in order to build staging & QA versions of your app that connect to different APIs or to build different white labeled versions of your application. To get started with custom environments, open the app you wish to work on and navigate in the sidebar to **Automate -> Environments**, then click **New Environment** on the top right. You should see a form like this:
+
+![Create Environment Form](/docs/assets/img/appflow/ss-environments-create.png)
+
+As can be noticed, there are 2 different sets of environment variables sections that can be utilized:
+
+* Secrets
+* Variables
+
+The only difference is that the secrets are hidden and never shown in the dashboard after they have been added, while the variables are always available to be read.
+
+The environments dashboard also lists available custom environments along with their configured key/value pairs and secrets keys.
+
+![Environments List View](/docs/assets/img/appflow/ss-environments-list.png)
+
+## Usage
+
+For example you could replace your `build` script in the `package.json` with a custom shell script that reads the branch and triggers a custom build.
+
+```json
+// customize the build script in the package.json
+{
+...
+    "scripts": {
+        "start": "ionic-app-scripts serve",
+        "clean": "ionic-app-scripts clean",
+        "build": "./mybuild.sh",
+        "lint": "ionic-app-scripts lint"
+    },
+...
+```
+
+    #!/bin/bash
+    if [ "$CI_GIT_REF" = "master" ]; then
+        npx ionic build --prod
+    else
+        npx ionic build
+    fi
+
+
+As of `@ionic/app-scripts@3.2.0` you can also use [environment variables directly in your source code](https://github.com/ionic-team/ionic-app-scripts#environments) and they will be replaced at build time so that you can customize your code based on the environment.
+
+For example:
+
+```typescript
+productionConfig = {
+  api: 'https://my.production.api.com',
+  analyticsKey: 'my-production-key'
+}
+stagingConfig = {
+  api: 'https://my.staging.api.com',
+  analyticsKey: 'my-staging-key'
+}
+
+localConfig = {
+  api: 'https://localhost:7000'
+  analyticsKey: 'my-local-key'
+}
+
+switch (process.env.CI_GIT_REF) {
+  case 'master':
+    return productionConfig;
+  case 'staging':
+    return stagingConfig;
+  default:
+    return localConfig;
+}
+```

src/pages/da/appflow/automation/intro.md

@@ -0,0 +1,21 @@
+---
+title: 'Automations'
+previousText: 'Package'
+previousUrl: '/docs/appflow/package/cli'
+nextText: 'Create Automations'
+nextUrl: '/docs/appflow/automation/create'
+---
+
+<blockquote>
+  <p><b>Note:</b>This feature is only available on our <a href="/pricing">Growth plans</a> and above.</p>
+</blockquote>
+
+Ionic Appflow's automation features let you generate builds whenever you need them. Webhooks with secure, signed download URL's and build information are also easily configurable and updatable, ensuring your app gets in the necessary hands quickly and automatically.
+
+Automations enable you and your team to utilize the full CI/CD powers of Appflow. You can create automations that trigger [package builds](/docs/appflow/package/builds) and [deploy builds](/docs/appflow/deploy/builds) every time your team checks in new code to a given branch and you can even configure the automations to use different [environments](/docs/appflow/automation/environments#custom-environments) and [native configurations](/docs/appflow/package/native-configs) so that you can build different versions of your app for development, staging, and production.
+
+##### Helpful links
+
+<docs-cards class="max-measure"> <docs-card header="Create an Automation" href="/docs/appflow/quickstart/automation" icon="/docs/assets/icons/guide-quickstart-icon.png"> 
+
+Create your first Android development binary automation using our quickstart guide!</docs-card> </docs-cards>