Rework workflow documentation

The workflow documentation is a bit of a mess. Rework the documentation:

• Split the details out of the platform guide, making it a better high level overview of Apertis targeted more at selling the platform.
• Create an architectural document covering the basics of the Apertis workflow and how the tools used by Apertis fit together. Use pictures to help explain.
• Detailed information about workflows shifted to guides
  • Packaging guide starting to be restructured to better cover workflows by adding sections.
  • Separating out description of component repository layout into its own guide.
  • Shift image creation details to Image building guide.

While I've noticed:

• Packages have been moved from repository based sub-directories under pkg/ to pkg/ its self. Update the URLs used on the website to reflect this.

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

content/architecture/platform-guide.md

@@ -83,8 +83,8 @@ On top of the shared core, each user has access to
 components that are not meant to be shared with other teams, both for
 experimentation and for product development.
 
-Contributions to the shared Apertis components follows Open Source Software
-(OSS) best practices with it's
+Contributions to the shared Apertis components follow Open Source Software
+(OSS) best practices with its
 [maintainer/contributor policies]( {{< ref "contributions.md" >}} )
 centered on code review and
 [continuous integration]( {{< ref "component_structure.md" >}} ).
@@ -126,7 +126,7 @@ example of how to implement fleet manangement.
 
 Applications can be deployed and updated in
 [application bundles]({{< ref "canterbury-legacy-application-framework.md" >}})
-(with a new [Flatpak based solution]({{< ref "application-framework.md" >}}) on
+(with a new [Flatpak-based solution]({{< ref "application-framework.md" >}}) on
 the way) without re-deploying the whole platform, decoupling the release and
 update cycle of the base software from that of each application.