Release new example to production (#6)

* Update azure-pipelines.yml for Azure Pipelines (#3)

* Create Standalone build example (#5)

* Update README

* Update azure-pipelines.yml for Azure Pipelines (#3) (#4)

* Update azure-pipelines.yml for Azure Pipelines

* Update azure-pipelines.yml for Azure Pipelines

* Update azure-pipelines.yml for Azure Pipelines

* Update azure-pipelines.yml for Azure Pipelines

* Update azure-pipelines.yml for Azure Pipelines

* Add htaccess file for https redirect

* Add GA

* Create first standalone example

Author: FejZa

README.md

@@ -2,7 +2,7 @@
 
 [![Documentation](./static/img/page-preview.png)](https://www.unitydevops.com)
 
-This repository contains the documentation website for [Unity Tools for Azure DevOps](https://marketplace.visualstudio.com/items?itemName=DinomiteStudios.64e90d50-a9c0-11e8-a356-d3eab7857116). A collection of tools and tasks for working with Unity based projects. The website is built using [Docusaurus 2](https://v2.docusaurus.io/), a modern static website generator.
+This repository contains the documentation website for [Unity Tools for Azure DevOps](https://marketplace.visualstudio.com/items?itemName=DinomiteStudios.64e90d50-a9c0-11e8-a356-d3eab7857116). A collection of tools and tasks for working with Unity based projects on Azure DevOps. The website is built using [Docusaurus 2](https://v2.docusaurus.io/), a modern static website generator.
 
 ## Branches
 

docs/example-standalone-0.md

@@ -3,8 +3,73 @@ id: example-standalone-0
 title: Standalone Build And Upload
 ---
 
-This pipeline example will build a Unity application targeting the Standalone platform and then proceed to upload the exported files from the agent to the Azure DevOps storage, so they can be deployed or distributed as needed in subsequent operations, such as a continuous deployment pipeline.
+This pipeline example will build a Unity application targeting the Standalone platform and then proceed to upload the exported files from the agent to the Azure DevOps storage, so they can be deployed or distributed as needed in subsequent operations, such as a CD pipeline.
 
-## At a glance
+## Overview
 
-**Target Platform:** Standalone
+**Target Platform:**
+
+- Standalone (Windows)
+
+**Used Tasks:**
+
+- Unity Activate License
+- Unity Build
+
+**Agent:**
+
+- Custom Agent with Unity preinstalled
+
+## YAML
+
+```yaml
+# Trigger the pipeline to run whenever a commit to the main branch is made.
+trigger:
+- main
+
+# Use a custom agent pool called "Unity Windows" that manages custom agents
+# that have the required Unity versions installed and any required SDKs for target platforms
+# configured.
+pool:
+  name: 'Unity Windows'
+
+# Adds a pipeline variables library to the pipeline that contains
+# authentication variables for activating a Unity editor with a Unity Plus / Pro seat.
+variables:
+  - group: 'unity-activation-variables'
+
+steps:
+# Before we build we activate a Unity Plus/Pro seat on the agent, only for the duration
+# of the pipeline execution. That way we can e.g. get rid of the Unity splash screen in our build.
+- task: UnityActivateLicenseTask@1
+  name: 'unityactivation'
+  inputs:
+    username: '$(unity.username)'
+    password: '$(unity.password)'
+    serial: '$(unity.serial)'
+
+# Build the Unity project to standalone. Since we are running on a Windows agent, this will produce
+# an .exe executable and any dependency files needed.
+- task: UnityBuildTask@3
+  inputs:
+    buildTarget: 'standalone'
+    outputPath: '$(Build.BinariesDirectory)'
+    outputFileName: 'mygame'
+
+# Copy build output files to artifact staging directory.
+- task: CopyFiles@2
+  inputs:
+    SourceFolder: '$(Build.BinariesDirectory)'
+    Contents: '**'
+    TargetFolder: '$(Build.ArtifactStagingDirectory)'
+    CleanTargetFolder: true
+    OverWrite: true
+
+# Finally publish all items in artifact staging to the Azure Pipelines
+# artifact storage. They will be available for sharing and/or further processing there.
+- task: PublishBuildArtifacts@1
+  inputs:
+    PathtoPublish: '$(Build.ArtifactStagingDirectory)'
+    ArtifactName: 'drop'
+    publishLocation: 'Container'
+```

docs/features.md

@@ -3,7 +3,7 @@ id: features
 title: Features Overview
 ---
 
-Once `Unity Tools for Azure DevOps` has been installed to your organization, you'll have access to a set of
+Once Unity Tools for Azure DevOps has been installed to your organization, you'll have access to a set of
 build and release tasks for Unity related operations. The extension provides the following tasks for use in your pipelines:
 
 Please check each tasks documentation page and for examples on how to use them. Also make sure to checkout our [Examples](./examples.md) collection with useful pipeline definitions you can copy-paste and adjust to your needs.

docusaurus.config.js

@@ -1,14 +1,18 @@
 module.exports = {
   title: 'Unity Tools for Azure DevOps',
   tagline: 'Set up CI/CD for Unity projects powered by Azure Pipelines',
-  url: 'https://your-docusaurus-test-site.com',
+  url: 'https://www.unitydevops.com',
   baseUrl: '/',
   onBrokenLinks: 'throw',
   onBrokenMarkdownLinks: 'warn',
   favicon: 'img/favicon.ico',
   organizationName: 'Dinomite-Studios',
-  projectName: 'unity-azure-pipelines-tasks',
+  projectName: 'unity-azure-pipelines-tasks-docs',
   themeConfig: {
+    googleAnalytics: {
+      trackingID: 'G-W9FFRR7HX3',
+      anonymizeIP: true
+    },
     navbar: {
       title: 'Unity Tools for Azure DevOps',
       logo: {

static/.htaccess

@@ -0,0 +1,3 @@
+RewriteEngine On
+RewriteCond %{HTTPS} !=on
+RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]