fix: use hugo relative URL references

Signed-off-by: Paul Horton <phorton@sonatype.com>

Author: madpah

content/en/_index.md

@@ -3,10 +3,10 @@ title: Sonatype Community Projects Handbook
 ---
 
 {{< blocks/cover title="The Sonatype Open Source Community" image_anchor="top" height="full" >}}
-<a class="btn btn-lg btn-primary me-3 mb-4" href="/projects/flagship/">
+<a class="btn btn-lg btn-primary me-3 mb-4" href="{{< ref "/projects/flagship" >}}">
   Our Flagship Projects <i class="fas fa-arrow-alt-circle-right ms-2"></i>
 </a>
-<a class="btn btn-lg btn-secondary me-3 mb-4" href="/docs/">
+<a class="btn btn-lg btn-secondary me-3 mb-4" href="{{< ref "/docs" >}}">
   Get Involved <i class="fas fa-arrow-alt-circle-right ms-2"></i>
 </a>
 <p class="lead mt-5">Open Source projects maintained by Sonatype!</p>
@@ -31,12 +31,12 @@ Please follow this space for updates!
 {{% /blocks/feature %}}
 
 
-{{% blocks/feature icon="fab fa-github" title="Contributions welcome!" url="https://github.com/google/docsy-example" %}}
-We do a [Pull Request](https://github.com/google/docsy-example/pulls) contributions workflow on **GitHub**. New users are always welcome!
+{{% blocks/feature icon="fab fa-github" title="Contributions welcome!" url="https://github.com/sonatype-nexus-community/community-handbook.sonatype.com" %}}
+We do a [Pull Request](https://github.com/sonatype-nexus-community/community-handbook.sonatype.com/pulls) contributions workflow on **GitHub**. New users are always welcome!
 {{% /blocks/feature %}}
 
 
-{{% blocks/feature icon="fab fa-twitter" title="Follow us on Twitter!" url="https://twitter.com/docsydocs" %}}
+{{% blocks/feature icon="fab fa-twitter" title="Follow us on Twitter!" url="https://twitter.com/sonatype" %}}
 For announcement of latest features etc.
 {{% /blocks/feature %}}
 

content/en/docs/_index.md

@@ -4,21 +4,5 @@ linkTitle: Get Involved
 menu: {main: {weight: 20}}
 ---
 
-This section is where the user documentation for your project lives - all the
-information your users need to understand and successfully use your project.
-
-For large documentation sets we recommend adding content under the headings in
-this section, though if some or all of them don’t apply to your project feel
-free to remove them or add your own. You can see an example of a smaller Docsy
-documentation site in the [Docsy User Guide](https://docsy.dev/docs/), which
-lives in the [Docsy theme
-repo](https://github.com/google/docsy/tree/master/userguide) if you'd like to
-copy its docs section.
-
-Other content such as marketing material, case studies, and community updates
-should live in the [About](/about/) and [Community](/community/) pages.
-
-Find out how to use the Docsy theme in the [Docsy User
-Guide](https://docsy.dev/docs/). You can learn more about how to organize your
-documentation (and how we organized this site) in [Organizing Your
-Content](https://docsy.dev/docs/best-practices/organizing-content/).
+Wanting to engage with a Sonatype Community Project? This area documents the different 
+ways of engaging with and the standards we expect our Community Projects to operate to.

content/en/docs/contributing/_index.md

@@ -13,8 +13,8 @@ We thank you in advance for contributing to our Open Source Community!
 Contributions come is all shapes and sizes - and we welcome them all. We ask that for the benefit of the wider community the following guidelines are followed depending on the contribution you wish to make.
 
 - **💡Want to discuss an idea?**  
-  *Read our guide on discussions and ideas [here](/docs/contributing/discussing-ideas/).*
+  *Read our guide on discussions and ideas [here]({{< ref "/docs/contributing/discussing-ideas" >}}).*
 - **🪲 Want to report a bug or issue?**  
-  *Read our guide on issue reporting [here](/docs/contributing/reporting-issues/).*
+  *Read our guide on issue reporting [here]({{< ref "/docs/contributing/reporting-issues" >}}).*
 - **🧑‍💻 Want to contribute a change?**  
-  *Read our guide on sumitting contributions [here](/docs/contributing/submitting).*
+  *Read our guide on sumitting contributions [here]({{< ref "/docs/contributing/submitting" >}}).*

content/en/docs/introduction.md

@@ -18,5 +18,4 @@ weight: 20
 
 ### GitHub Repository Configuration
 
-See our [GitHub Repository Configuration Standards](/docs/standards/github-repository).
-
+See our [GitHub Repository Configuration Standards]({{< ref "/docs/standards/github-repository" >}}).

content/en/docs/new-project/_index.md

@@ -53,7 +53,7 @@ The following Branch protection rules should be applied.
   * **Require review from Code Owners** Yes ✅
   * **Allow specified actors to bypass required pull requests** No ❌
 * **Require status checks to pass before merging** Yes ✅
-  * *Checks according to [Code Quality](/docs/standards/code-quality/) and [Dependency Management](/docs/standards/dependency-management/) must be covered*
+  * *Checks according to [Code Quality]({{< ref "/docs/standards/code-quality" >}}) and [Dependency Management]({{< ref "/docs/standards/dependency-management" >}}) must be covered*
 * **Require signed commits** Yes ✅
 * **Allow force pushes** No ❌
 * **Allow deletions** No ❌
@@ -72,7 +72,7 @@ Set both `Flagship-Project` and `Project-Status` accordingly.
 
 #### Code security and analysis
 
-* **Private vulnerability reporting** No ❌ - See [Reporting Issues](/docs/contributing/reporting-issues/)
-* **Dependabot** No ❌ - See [Dependency Management](docs/standards/dependency-management/)
-* **Code Scanning** No ❌ - See [Code Quality](docs/standards/code-quality/)
+* **Private vulnerability reporting** No ❌ - See [Reporting Issues]({{< ref "/docs/contributing/reporting-issues" >}})
+* **Dependabot** No ❌ - See [Dependency Management]({{< ref "/docs/standards/dependency-management" >}})
+* **Code Scanning** No ❌ - See [Code Quality]({{< ref "/docs/standards/code-quality" >}})
 * **Secret scanning** <span class="-text-accent-hot-pink">TBC</span>