Channel installation support

.README

@@ -18,4 +18,4 @@
 
 [[load:readme/5-Vedlikehold.md]]
 
-[[load:readme/6-Utvikling.md]]
+[[load:readme/6-Utvikling.md]]

.development-guide/.README

@@ -6,231 +6,24 @@
 [[ template:toc ]]
 </details>
 
-## Site Design / Site Scripts
+[[load:.development-guide/Site_Design_Site_Scripts.md]]
 
-Everything related to the site design and the corresponding site scripts reside in the folder **SiteScripts**. 
+[[load:.development-guide/JS_Provisioning_Template.md]]
 
-The source files are found in the **src** folder.
+[[load:.development-guide/Templates.md]]
 
-## JS Provisioning Template
+[[load:.development-guide/NPM.md]]
 
-Not everything we want to do is available with site designs, so we're also using [sp-js-provisioning](https://github.com/Puzzlepart/sp-js-provisioning). Please note that we're using the Puzzlepart fork from **pnp**.
+[[load:.development-guide/Building_a_new_release.md]]
 
-With our PnP content templates (see **3.2.2**) we're provisioning a default template. The default templates for our supported languages are built from the source file [_JsonTemplate.json](../Templates/_JsonTemplate.json).
+[[load:.development-guide/Building_only_PnP_templates.md]]
 
-Please note the **Parameters** object.
+[[load:.development-guide/Continuous_integration.md]]
 
-```json
-{
-  "Parameters": {
-    "ProvisionSiteFields": "Kolonner for Prosjektportalen (Prosjekt)",
-    "ProjectContentTypeId": "0x0100805E9E4FEAAB4F0EABAB2600D30DB70C",
-    "ProjectStatusContentTypeId": "0x010022252E35737A413FB56A1BA53862F6D5"
-  }
-}
-```
+[[load:.development-guide/Creating_a_new_release.md]]
 
-| Parameter                  | Description                                                                           |
-| -------------------------- | ------------------------------------------------------------------------------------- |
-| ProvisionSiteFields        | The site fields in this group will be copied to the project site during provisioning. |
-| ProjectContentTypeId       | Content type ID for the Project properties content type                               |
-| ProjectStatusContentTypeId | Content type ID for the Project status content type                                   |
+[[load:.development-guide/Versioning.md]]
 
-In addition to the parameters specified in [Standardmal.txt](../Templates/Portfolio/Prosjektmaler/Standardmal.txt), there's also the following parameters:
+[[load:.development-guide/Installation_channels.md]]
 
-| Parameter  | Description                                                                           |
-| ---------- | ------------------------------------------------------------------------------------- |
-| TermSetIds | An map of term set fields and term set id. Used to override the default term set ids. |
-
-Say you'd like to use the term set with ID **54da9f47-c64e-4a26-80f3-4d3c3fa1b7b2** for project phase. The internal field name for project phase is **GtProjectPhase**. With the default template, the **Parameters** object would look like this:
-
-```json
-{
-  "Parameters": {
-    "ProvisionSiteFields": "Kolonner for Prosjektportalen (Prosjekt)",
-    "ProjectContentTypeId": "0x0100805E9E4FEAAB4F0EABAB2600D30DB70C",
-    "ProjectStatusContentTypeId": "0x010022252E35737A413FB56A1BA53862F6D5",
-    "TermSetIds": {
-      "GtProjectPhase": "54da9f47-c64e-4a26-80f3-4d3c3fa1b7b2"
-    }
-  }
-}
-```
-
-## Templates
-
-### JSON provisioning template
-
-At the root level of the **Templates** folder, the following files are found:
-
-| File/Folder                     | Description                                                                                   |
-| ------------------------------- | --------------------------------------------------------------------------------------------- |
-| `Clean-Resx.ps1`                | Script to remove unused **.resx** resources                                                   |
-| `Find-FieldUsage.ps1`           | Script to find field usage                                                                    |
-| `Get-ComponentProperties.ps1`   | Script to get component properties from `<pnp:ClientSidePage>` instances                      |
-| `Encode-JSON.ps1`               | Script to take the content of a JSON file, encode and minfiy at, and store it in a `.txt`file |
-| `Search-Resx.ps1`               | Script to search for unused **.resx** resources                                               |
-| `tasks/generateResxJson.js`     | Node script to generate a JSON representation of the **.resx** files                          |
-| `tasks/generateJsonTemplate.js` | Node script to generate JSON templates for each language                                      |
-| `_JsonTemplate.json`            | JSON project template                                                                         |
-
-#### Building JSON templates
-
-When doing changes to the JSON template the npm task `watch` can be used. This watches `_JsonTemplate.json` and builds localized version of this to the corresponding Content template.
-
-Resources from the **.resx** files in the folder Portfolio can be used in the template using `{{tokens}}`.
-
-**Example:**
-
-```json
-{
-    "ID": "0x0100A87AE71CBF2643A6BC9D0948BD2EE897",
-    "Name": "{{ContentTypes_Uncertainty_Name}}",
-    "Description": "",
-    "Group": "{{ContentTypes_Group}}"
-}
-```
-
-### PnP templates
-
-In addition we have two PnP provisioning templates. 
-
-| Template                            | Description      |
-| ----------------------------------- | ---------------- |
-| [Portfolio](../Templates/Portfolio) | Portfolio assets |
-| [Taxonomy](../Templates/Taxonomy)   | Taxonomy         |
-
-#### Portfolio
-
-| File/Folder        | Description                                                    |
-| ------------------ | -------------------------------------------------------------- |
-| Objects            | PnP assets. See https://github.com/pnp/PnP-Provisioning-Schema |
-| SiteAssets         | Files to be uploaded to SiteAssets                             |
-| Portfolio.xml      | Main template file                                             |
-| `Resources.*.resx` | Resource files                                                 |
-
-#### Content templates
-
-Content templates are found in the **Content** folder. The name of the template follows the following pattern:
-
-`Portfolio_content.{language_code}.xml`
-`Portfolio_content_BA.{language_code}.xml`
-
-`language_code` can be for example **no-NB** or **en-US**.
-
-The templates contains the JSON template(s), planner tasks and phase checklist items.
-
-## NPM
-
-The SharePoint Framework solutions are published to `npm` independently.
-
-- [@Shared](https://www.npmjs.com/package/pp365-shared)
-- [ProjectWebParts](https://www.npmjs.com/package/pp365-projectwebparts)
-- [ProjectExtensions](https://www.npmjs.com/package/pp365-projectextensions)
-- [PortfolioWebParts](https://www.npmjs.com/package/pp365-portfoliowebparts)
-- [ProgramWebParts](https://www.npmjs.com/package/pp365-programwebparts)
-- [PortfolioExtensions](https://www.npmjs.com/package/pp365-portfolioextensions)
-
-## Building a new release
-
-To build a new release make sure your on the `main` branch and in sync with **origin**.
-
-Run the PowerShell script `Build-Release.ps1` located in the `Install` directory:
-
-```powershell
-./Install/Build-Release.ps1
-```
-
-The installation package should be found in the release folder.
-
-## Building only PnP templates
-
-To only build PnP templates make sure your on the `main` branch and in sync with **origin**.
-
-Run the PowerShell script `Build-Release.ps1` located in the `Install` directory:
-
-```powershell
-./Install/Build-Release.ps1 -SkipBuildSharePointFramework
-```
-
-The PnP templates should be found in the release folder.
-
-## Continuous integration
-
-We have set up continuous integration using GitHub actions.
-
-[![CI (dev)](https://github.com/Puzzlepart/prosjektportalen365/actions/workflows/ci-dev.yml/badge.svg?branch=dev)](https://github.com/Puzzlepart/prosjektportalen365/actions/workflows/ci-dev.yml)
-
-Keywords can be used in the commit message to avoid (or force) the CI running some of the jobs.
-
-- `[skip-ci]` to avoid the _Build release package_ job starting. This will result in no jobs starting as the _Upgrade_ and _Install_ jobs are dependent on the job _Build release package_
-- `[skip-upgrade]` to avoid the _Uprade_ job starting. This will also skip the _Install_ job as it's dependent on _Upgrade_
-- `[skip-install]` to avoid the _Install_ job starting. 
-- `[upgrade-all-sites-to-latest]` to run script `UpgradeAllSitesToLatest.ps1` in CI mode
-
-### Build and install (dev)
-
-[ci-releases](../.github/workflows/ci-releases.yml) builds a new release on _push_ to **releases/***.
-
-It runs [Build-Release.ps1](../Install/Build-Release.ps1) with `-CI` param, then runs [Install.ps1](../Install/Install.ps1) (also with `-CI` param, this time with a encoded string consisting of the username and password, stored in a GitHub secret). The URL to install to is stored in the GitHub secret `CI_DEV_TARGET_URL`.
-
-With the current approach, with no cache (as it runs `npm ci`), a full run takes about 25-35 minutes.
-
-![image-20201121133532960](assets/image-20201121133532960.png)
-
-### Build release (main)
-
-[build-release](../.github/workflows/build-release.yml) builds a new release package on **push** to **main**.
-
-## Creating a new release
-
-For creating a new release, we have two options: Minor and patch. New minor version should be created when there is new functionality of interest to users, while patch versions can be created often with bug fixes, adjustments and minimal functional improvements.
-
-Increasing the version number is done by npm scripts. This is done on the dev-branch when the functionality currently in dev is deemed ready for release.
-
-
-### Patch-release
-```powershell
-npm version patch
-git push --tags
-```
-
-### Minor-release
-```powershell
-npm version minor
-git push --tags
-```
-
-Then create a Pull Request to merge `dev` into `main`. The output from GitHub Actions will include a release package that can be shared as a release on GitHub. No manual build required.
-
-## Versioning
-
-After updating the version using `npm version patch` or `npm version minor` the task `tasks/automatic-versioning.js` are run. This synchronizes versions across the solution.
-
-This `automatic-versioning.js` task can also be run as a **npm script** outside the `postversion` event.
-
-```powershell
-npm run sync-version
-```
-
-After the `sync-version` script has been run, it is important to publish the SharePointFramework packages (@Shared, PortfolioWebParts, etc...) to npm.
-
-This is done for each package by running the following script:
-
-```powershell
-npm install; npm run build; npm publish;
-```
-
-If you have to update and use a package under development add a temp tag:
-
-```powershell
-npm install; npm run build; npm publish --tag temp;
-```
-
-N.B.: To be able to publish you must sign in with an account that has access to the packages at [npmjs](https://www.npmjs.com)
-
-## README generation
-
-READMEs are automatically generated using [@appnest/readme](https://github.com/andreasbm/readme). The main README is generated from [.README](../.README) while this README is generated from [.README](.README). The generation is configured with the `blueprint.json` files.
-
-For the main [README.md)[../README.md] generation, the different parts are included from the [readme](../readme) folder at root level.
+[[load:.development-guide/README_generation.md]]

.development-guide/Building_a_new_release.md

@@ -0,0 +1,11 @@
+## Building a new release
+
+To build a new release make sure your on the `main` branch and in sync with **origin**.
+
+Run the PowerShell script `Build-Release.ps1` located in the `Install` directory:
+
+```powershell
+./Install/Build-Release.ps1
+```
+
+The installation package should be found in the release folder.

.development-guide/Building_only_PnP_templates.md

@@ -0,0 +1,11 @@
+## Building only PnP templates
+
+To only build PnP templates make sure your on the `main` branch and in sync with **origin**.
+
+Run the PowerShell script `Build-Release.ps1` located in the `Install` directory:
+
+```powershell
+./Install/Build-Release.ps1 -SkipBuildSharePointFramework
+```
+
+The PnP templates should be found in the release folder.

.development-guide/Continuous_integration.md

@@ -0,0 +1,32 @@
+## Continuous integration
+
+We have set up continuous integration using GitHub actions.
+
+### CI (releases/*)
+[![CI (releases)](https://github.com/Puzzlepart/prosjektportalen365/actions/workflows/ci-releases.yml/badge.svg?branch=releases/1.9)](https://github.com/Puzzlepart/prosjektportalen365/actions/workflows/ci-releases.yml)
+
+Keywords can be used in the commit message to avoid (or force) the CI running some of the jobs.
+
+- `[skip-ci]` to avoid the _Build release package_ job starting. This will result in no jobs starting as the _Upgrade_ and _Install_ jobs are dependent on the job _Build release package_
+- `[skip-upgrade]` to avoid the _Uprade_ job starting. This will also skip the _Install_ job as it's dependent on _Upgrade_
+- `[skip-install]` to avoid the _Install_ job starting. 
+- `[upgrade-all-sites-to-latest]` to run script `UpgradeAllSitesToLatest.ps1` in CI mode
+
+### Build and install (dev)
+
+[ci-releases](../.github/workflows/ci-releases.yml) builds a new release on _push_ to **releases/***.
+
+It runs [Build-Release.ps1](../Install/Build-Release.ps1) with `-CI` param, then runs [Install.ps1](../Install/Install.ps1) (also with `-CI` param, this time with a encoded string consisting of the username and password, stored in a GitHub secret). The URL to install to is stored in the GitHub secret `CI_DEV_TARGET_URL`.
+
+With the current approach, with no cache (as it runs `npm ci`), a full run takes about 25-35 minutes.
+
+![image-20201121133532960](assets/image-20201121133532960.png)
+
+### CI (channels/test)
+Keyword `[channels/test]` needs to be used in the commit message for this CI to run.
+
+It will build a package for channel [test](../channels/test.json) and deploy it to the URL specified in `SP_URL_TEST`.
+
+### Build release (main)
+
+[build-release](../.github/workflows/build-release.yml) builds a new release package on **push** to **main**.

.development-guide/Creating_a_new_release.md

@@ -0,0 +1,20 @@
+## Creating a new release
+
+For creating a new release, we have two options: Minor and patch. New minor version should be created when there is new functionality of interest to users, while patch versions can be created often with bug fixes, adjustments and minimal functional improvements.
+
+Increasing the version number is done by npm scripts. This is done on the dev-branch when the functionality currently in dev is deemed ready for release.
+
+
+### Patch-release
+```powershell
+npm version patch
+git push --tags
+```
+
+### Minor-release
+```powershell
+npm version minor
+git push --tags
+```
+
+Then create a Pull Request to merge `dev` into `main`. The output from GitHub Actions will include a release package that can be shared as a release on GitHub. No manual build required.

.development-guide/Installation_channels.md

@@ -0,0 +1,26 @@
+## Installation channels
+
+To support installing several instances of _Prosjektportalen 365_ in a tenant, we support **installation channels**.
+
+### Generating a new channel configuration
+To generate a new channel configuration, use the `npm` script `generate-channel-config`.
+
+To generate a new channel configuration for `test`:
+
+```javascript
+npm run-script generate-channel-config test
+```
+
+To update an existing channel configuration, add the flag `/update`:
+
+```javascript
+npm run-script generate-channel-config test /update
+```
+
+### Building a new release for a channel
+To build a new release for a channel, add the `-Channel` flag when running the release-script.
+
+**Example (buiding for test channel):**
+```powershell
+Install/Build-Release.ps1 -Channel test
+```