Replace links to old wiki in markdown documents

We have a number of URLs on the website that point to the old wiki. Since
these documents have either moved or we can provide a more direct link,
update the URLs. This will improve our ability to check for broken links.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

content/guidelines/build_and_integration_infrastructure_documentation.md

@@ -16,7 +16,7 @@ for B\&I services, documentation and activities in the project.
 
 ## Services
 
-  - [Wiki](https://wiki.apertis.org)
+  - [Website](https://www.apertis.org)
   - [Issue Tracker](https://phabricator.apertis.org)
   - [OBS (Open Build Service)](https://build.collabora.co.uk)
   - [Images](https://images.apertis.org/)

content/image_building.md

@@ -29,7 +29,7 @@ using [Debos](https://github.com/go-debos/debos). It is strongly
 recommended to utilise the [appropriate Docker image builder
 container](https://gitlab.apertis.org/infrastructure/apertis-image-recipes#building-in-docke)
 to perform these steps, though the Apertis SDK image [running in a
-VM](https://wiki.apertis.org/Deployment_Environment#Apertis_on_virtual_machines)
+VM]( {{< ref "/guides/virtualbox.md" >}} )
 can be used with reduced reliability.
 
 # Building OSpacks
@@ -60,4 +60,4 @@ image is compressed to minimise storage space.
 Existing Apertis examples can be found in the [Apertis Image Recipes
 repository](https://gitlab.apertis.org/infrastructure/apertis-image-recipes)
 called `apertis-image-*.yaml`. The Debos documentation also provides a
-[simple example](https://github.com/go-debos/debos#simple-example).
+[simple example](https://github.com/go-debos/debos#simple-example).
\ No newline at end of file

content/release/17.03/releasenotes.md

@@ -560,7 +560,7 @@ concepts.
 
 Several widgets and other components in libmildenhall have names that do
 not start with the correct [namespace
-prefix](https://wiki.apertis.org/Guidelines/Coding_conventions#Namespacing).
+prefix](https://designs.apertis.org/latest/coding_conventions.html#namespacing).
 All symbols, types and macros not starting with `Mildenhall`,
 `mildenhall_`, `MILDENHALL_` are deprecated and will be removed in a
 future Apertis version, hopefully 17.06.
@@ -1159,4 +1159,4 @@ Image build tools can be found in the Apertis tools repositories.
     multiple applications)
 
   - Status bar is not getting updated with the current song/video being
-    played
+    played
\ No newline at end of file

content/release/v2019pre/releasenotes.md

@@ -130,13 +130,13 @@ easier.
 Now any package on Apertis can be updated by submitting [merge
 requests](https://docs.gitlab.com/ce/user/project/merge_requests/) to
 its corresponding project on GitLab. The [Gitlab-based packaging
-workflow](https://wiki.apertis.org/Guidelines/Gitlab-based_packaging_workflow)
+workflow]( {{< ref "/guidelines/gitlab-based_packaging_workflow.md" >}} )
 guide walks developers through the steps needed, sensibly lowering the
 learning curve for developers new to the Debian-based packaging tools.
 
 Developers now have a coherent and reliable workflow that applies to all
 the packages in the archive using the same [contribution
-process](https://wiki.apertis.org/Guidelines/Contribution_process) used
+process](https://designs.apertis.org/latest/contribution-process.html) used
 for all the other Apertis projects, while maintainers have finer grained
 control on the downstream changes that get applied.
 

content/release/v2020pre/releasenotes.md

@@ -213,7 +213,7 @@ high-level and how this can be introduced into Apertis.
 
 A new developers handbook helps people interested in [building, patching
 and maintaining versions of the Linux
-kernel](https://wiki.apertis.org/Guidelines/BuildingPatchingAndMaintainingTheApertisKernel)
+kernel]( {{< ref "guidelines/buildingpatchingandmaintainingtheapertiskernel.md" >}} )
 based on the Apertis package.
 
 The guide suggests workflows both utilising the Debian infrastructure on
@@ -834,4 +834,4 @@ services.
 
   - frome: 6_frome test failed
 
-  - frome: 5_frome test failed
+  - frome: 5_frome test failed
\ No newline at end of file