Added guilds and Slack channels to about page (#422)

* Added guild information onto the engineering website

* Updates from code review

* Updated with descriptions of each guild

* Added Jeff's suggestions including Slack in link and adding link to see pages associated with a guild

* Moved info about guilds to beginning of page

* Readded formating tabs to beginning of links


---------

Co-authored-by: Robert Deniszczyc <[email protected]>
Co-authored-by: Jeff Horton <[email protected]>
Co-authored-by: edhamiltonHO <[email protected]>

docs/about.md

@@ -9,10 +9,69 @@ tags:
 
 The Home Office Engineering Guidance and Standards site is a body of knowledge for software engineers. It is comprised of principles, patterns and standards that define how we do engineering at the Home Office, and that direct how we want to do engineering in the future. This guidance is created and curated by the Home Office engineering community. The project as a whole is led by the Home Office DDaT Engineering Profession team.
 
-## Why we are doing it
+## How you can contribute
 
 The Home Office has a large estate of teams and technology products. There is a wealth of experience and best practice that we can draw on, to standardise some of the things that we do and manage quality consistently. This will help us to deliver secure, performant technology that meets user needs, and deliver it quickly.
 
+We want to use our large community to shape the guidance and standards on this site so guilds have been created to have a network to write content based on topics related to their areas. These guilds are open to anyone in the Home Office with an interest in the given subject (Software Design, Ways of Working etc.).
+
+The guilds meet regularly to discuss topics relating to their areas and contribute towards the guidance, standards and principles.
+
+### Guild information
+
+On Home Office Slack you'll find more information for each guild in their respective channels along with when they meet, and who to contact to join.
+
+Build, release and deployment guild
+: Topics related to the release and deployment pipeline including CI/CD, Feature Toggling and Artefact Management.
+
+  [**Slack**: #segas-build-release-deployment](https://homeoffice.enterprise.slack.com/archives/C02DR9CU4SC)
+
+  [Pages tagged with build, release and deploy](/tags/build-release-and-deploy/)
+
+Low Code
+: A space to discuss low-code engineering guidance and standards.
+
+  [**Slack**: #segas-low-code](https://homeoffice.enterprise.slack.com/archives/C05MK8UM2F7)
+
+  [Pages tagged with low code](/tags/low-code/)
+
+Observability
+: Topics relating to the ongoing monitoring of applications and services, including Logging, Analytics and Performance.
+
+  [**Slack**: #segas-observability](https://homeoffice.enterprise.slack.com/archives/C02BJSXJ0QK)
+
+  [Pages tagged with observability](/tags/observability/)
+
+Security
+: Articles in this section relate to subjects such as Secure Development, Identity & Access and Vulnerability Scanning.
+
+  [**Slack**: #segas-security](https://homeoffice.enterprise.slack.com/archives/C0282A158FM)
+
+  [Pages tagged with security](/tags/security/)]
+
+Software Design
+: Items to be covered to include Frameworks, Languages, Quality and Coding Standards.
+
+  [**Slack**: #segas-software-design](https://homeoffice.enterprise.slack.com/archives/C02AHL4ML7P)
+
+  [Pages tagged with software design](/tags/software-design/)
+
+Source Management
+: Items to be covered to include Open Source, Licensing and Source Code Management.
+
+  [**Slack**: #segas-source-management](https://homeoffice.enterprise.slack.com/archives/C02DE9B8M25)
+
+  [Pages tagged with source management](/tags/source-management/)
+
+Ways of Working
+: Items to be covered to include Documentation, Tooling and Defining Stories.
+
+  [**Slack**: #segas-ways-of-working](https://homeoffice.enterprise.slack.com/archives/C02CLUJ01QX)
+
+  [Pages tagged with ways of working](/tags/ways-of-working/)
+
+## Why we are doing it
+
 In 2021 we conducted a discovery across a wide range of our engineering teams, including suppliers and civil servants, and encompassing all of our delivery portfolios. We found that there were a number of key areas that we should prioritise for centralised guidance. Since then we have been running guilds and other working groups to identify the more specific needs of our engineers, and develop guidance to meet those needs.
 
 This guidance was originally published on an internal content platform. We have since decided to open source it here for a number of reasons, the three main reasons being: