Merge branch 'development' into lint-docs

Author: MarkvanMents

.travis.yml

@@ -60,20 +60,29 @@ install:
   - mkdir public  # This because <Maybe> the process of syncing to public is probably deadlocked behind waiting for the public folder to be made, and is never signalled that the folder is created, which ends up stalling the build on Travis CI.
   # ------------------------
   -  ./node_modules/.bin/hugo config --environment $TRAVIS_BRANCH # report the config we are using
-  - echo "HUGO was run for environment $TRAVIS_BRANCH" > $TRAVIS_BUILD_DIR/hugo.log
+  # Output header in bold white on green
+  - printf '\033[37;42;1m' > $TRAVIS_BUILD_DIR/hugo.log
+  - echo "HUGO was run for environment $TRAVIS_BRANCH" >> $TRAVIS_BUILD_DIR/hugo.log
+  - printf '\033[0;22m' >> $TRAVIS_BUILD_DIR/hugo.log
   # Set pipefail so that if Hugo fails the whole job fails
   - set -o pipefail
   # put the flags in different config files controlled by environment matching $TRAVIS_BRANCH
   # Append output to hugo.log file to print at the end of the travis job
   # (see https://stackoverflow.com/questions/418896/how-to-redirect-output-to-a-file-and-stdout)
+
   -  ./node_modules/.bin/hugo --environment $TRAVIS_BRANCH 2>&1 | tee -a $TRAVIS_BUILD_DIR/hugo.log
-  #
+
   # normal htmltest takes too much memory - using a modified version which strips <aside> tag content
   # NB - Set pipefail so that Travis CI sees the return code from `tee` and not from `htmltest` so it will always build.
   - set +o pipefail
+  # Additional info  in bold white on green
+  - printf '\033[37;42;1m' >> $TRAVIS_BUILD_DIR/hugo.log
   - echo "Any errors from HTMLTEST will be treated as warnings - the build will continue." >> $TRAVIS_BUILD_DIR/hugo.log 
+  - printf '\033[0;22m' >> $TRAVIS_BUILD_DIR/hugo.log
   - chmod +x ./htmltest/htmltest
-  - ./htmltest/htmltest 2>&1 | tee -a $TRAVIS_BUILD_DIR/hugo.log
+  # Run htmltest - convert red (91) and green (92) aixterm colors with 8-bit versions (31 and 32).
+
+  - ./htmltest/htmltest 2>&1 | sed "s/\o033\[91/\o033\[31/g; s/\o033\[92/\o033\[32/g" |tee -a $TRAVIS_BUILD_DIR/hugo.log
 
 before_script:
 ##############
@@ -109,7 +118,7 @@ script:
 #  - pwd
 # NB: Have to have something here, otherwise Travis tries to run "npm test"
 # Display the output from hugo and htmltest so it is not folded and hidden, and is at the end of the log.
-  - echo "$(<$TRAVIS_BUILD_DIR/hugo.log)"
+  - printf '\n\n%s\n\n' "$(<$TRAVIS_BUILD_DIR/hugo.log)"
 
 # before_cache
 ############## Skipped

content/en/docs/apidocs-mxsdk/apidocs/apps/app-repository-api.md

@@ -107,7 +107,7 @@ Returns information about the version control repository for a Mendix app.
 
 |Name|Type|Required|Description|
 |---|---|---|---|
-|`AppId`|String|Yes|The App ID of the Mendix app for which the repository information should be returned. You can find this in the [General](/developerportal/collaborate/general-settings/) tab of the **Settings** page after you open your app in [Apps](https://sprintr.home.mendix.com/). |
+|`AppId`|String|Yes|The App ID of the Mendix app for which the repository information should be returned. You can find this under **Project ID** in the [General](/developerportal/collaborate/general-settings/) tab of the **Settings** page after you open your app in [Apps](https://sprintr.home.mendix.com/). |
 
 ##### Example
 

content/en/docs/apidocs-mxsdk/apidocs/apps/team-server-api.md

@@ -0,0 +1,26 @@
+---
+title: "Catalog APIs"
+linktitle: "Catalog"
+url: /apidocs-mxsdk/apidocs/catalog-apis/
+description: "The Catalog APIs register data sources from other business applications."
+weight: 50
+restapi: true
+aliases:
+    - /apidocs-mxsdk/apidocs/data-hub-apis/
+---
+
+## APIs for the Catalog
+
+Mendix offers the following APIs for the [Catalog](/catalog/): 
+
+* [Search API](/apidocs-mxsdk/apidocs/search-api/)
+  
+  Search and retrieve information on registered assets that can be used in your app development.
+
+* [Registration API](/apidocs-mxsdk/apidocs/registration-api/)
+  
+  Register and update services to the organization's Catalog.
+
+* [Transform API](/apidocs-mxsdk/apidocs/registration-api/#transform-api)
+  
+  For users deploying their Mendix applications outside Mendix Cloud, generate the request bodies to register services using the Registration API. The v5 compatibility for the Transform API is accessible via the Registration API in the Endpoints section.