Would it make sense to register a memorable domain name for this site?

Something like: mspdu.co.uk, msukpdu.com or ukpdu.com?

At the very least, we ought to reserve a short URL like http://aka.ms/ukpdu

If we revamp the page templates it would be good if authors was an array and we could show multiple authors on the page footer more easily

Hi @richeney
Thanks for creating the awesome hands-on labs :)
While trying out lab3 count meta parameter to create 3 different linux based free app service plans, I'm getting the following error:

Error: Error creating/updating App Service Plan "plan-free-westus" (Resource Group "webapps"): web.AppServicePlansClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="BadRequest" Message="Exceeded the limit of 1 free tier linux server farm per subscription." Details=[{"Message":"Exceeded the limit of 1 free tier linux server farm per subscription."},{"Code":"BadRequest"},{"ErrorEntity":{"Code":"BadRequest","ExtendedCode":"11027","Message":"Exceeded the limit of 1 free tier linux server farm per subscription.","MessageTemplate":"Exceeded the limit of 1 free tier linux server farm per subscription.","Parameters":[]}}]

Important part is Exceeded the limit of 1 free tier linux server farm per subscription.
While the limits mention being able to create 10 free app service plans per region but my error message says otherwise for linux based free plans !

Have you been able to workaround this ?
I can confirm if I switch to Standard SKU it works well.

The lab walks the user through creating multiple ASPs using the count meta parameter.
At one point it suggests using eastus2, uksouth, and centralindia for your test reasons.
Unfortunately, centralindia is not supported and failed for me (the other regions were successful).

Error: Error creating/updating App Service Plan "plan-free-1nf8dck7-centralindia" (Resource Group "webapps"): web.AppServicePlansClient#CreateOrUpdate: Failure sending request: StatusCode=401 -- Original Error: Code="Unauthorized" Message="The scale operation is not allowed for this subscription in this region. Try selecting different region or scale option." Details=[{"Message":"The scale operation is not allowed for this subscription in this region. Try selecting different region or scale option."},{"Code":"Unauthorized"},{"ErrorEntity":{"Code":"Unauthorized","ExtendedCode":"52020","Message":"The scale operation is not allowed for this subscription in this region. Try selecting different region or scale option.","MessageTemplate":"The scale operation is not allowed for this subscription in this region. Try selecting different region or scale option.","Parameters":["default"]}}]

Doesn't render correctly on pages he's created

It still has "Microsoft UK PDU CIM Site" as the title

Ordering of items on summary pages (like Labs) is a bit random - in reverse published date order might be better.

I'm writing the contributing guide. It would be useful for the content curator to be shown on the landing pages - perhaps as author, perhaps just at the bottom of the page. Also enable the comments section so that visitors can suggest new content.

Note that tables will workon the site, despite being outside of the official markdown standard. Example:

Column 1 Header | Column 2 Header
Key1 | Value1
Key2 | Value 2

You can do additional spacing and edge vertical pipes, but they aren't strictly necessary. Nor is putting the column header in bold, but it does look a little better.

https://ukpdu.github.io/prereqs/subscription/ is a good example.

Update guidance to offer Docker as an alternative (to me, i found it simpler to set up) way to do site generation / testing.

I used the following:
docker run -e "JEKYLL_ENV=docker" --label=jekyll --volume=%CD%:/srv/jekyll -it -p 4000:4000 jekyll/jekyll jekyll serve --config _config.yml,_config_local.yml --unpublished --future

I then did a docker commit on the container to generate my own image ... by then using the new image it avoided downloading numerous packages each time I needed to generate / test.

Since changing the style on code blocks, making them dark it has also affected any inline code. Which can be really hard on the eyes (see below) I think these are done with <pre> tags so hopefully can be style separately

Perhaps worth mentioning, per 'These commands are as tested within the Windows Subsystem for Linux (WSL), with the CLI 2.0 added.' -- nearly everything works on MacOS (High Sierra, with the Azure CLI and Homebrew installed), at least as far as lab 4.

The one command which fails is job=job.$(date --utc +"%Y%m%d.%H%M"), because Linux uses the GNU version of the date command and MacOS uses the UNIX version.

Easy fix: brew install coreutils, and use gdate instead of date. Further details here.

It looks %$!"$*! stupid

I think it'd be nice to syndicate this content via RSS/Atom. What do others think? Is there a preferred approach to accomplish this with Jekyll?