From 8cca4487577a95b13e2928ef0ef8c1c4912482f3 Mon Sep 17 00:00:00 2001
From: Anna Sancho Vaquer <anna.sanchovaquer@canonical.com>
Date: Thu, 27 Aug 2026 10:29:51 +0200
Subject: [PATCH 1/2] docs: apply revised version of homepage model (#78)

---
 docs/index.md | 20 ++++++--------------
 1 file changed, 6 insertions(+), 14 deletions(-)

diff --git a/docs/index.md b/docs/index.md
index 3a6d7cb..c08839c 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -13,24 +13,16 @@ Users need to be able to create software suited to their specific needs with a r
 surface and a small storage footprint. With Chisel, users build a minimal root filesystem by 
 selecting and installing only the necessary slices from the full Ubuntu package set.
 
----------
 
 ## In this documentation
 
-* **Tutorial**: [Hands-on introduction to Chisel in 15 minutes](tutorial/getting-started)
-    
-* **Common patterns**: [Install Chisel](how-to/install-chisel) • 
-[Slice a package](how-to/slice-a-package/) • 
-[Use Chisel in a Dockerfile](how-to/use-chisel-in-dockerfile) • 
-[Explore the Chisel CLI](reference/cmd/index) 
-    
-* **Slices**: [Learn more about slices](explanation/slices) • 
-[Chisel releases](reference/chisel-releases/index) • 
-[chisel.yaml](reference/chisel-releases/chisel.yaml) •
-[Slice definitions](reference/chisel-releases/slice-definitions) • [Slice design approaches](explanation/slice-design-approaches.md) • 
-[Install Ubuntu Pro package slices](how-to/install-pro-package-slices)
+* **Getting started**: [Hands-on introduction to Chisel in 15 minutes](tutorial/getting-started) • [General installation guide](how-to/install-chisel)
+* **Slices overview:** [Overview](explanation/slices) • [Chisel releases](reference/chisel-releases/index)
+* **Deploying slices:** [Using Chisel in a Dockerfile](how-to/use-chisel-in-dockerfile) • [Install Ubuntu Pro package slices](how-to/install-pro-package-slices) • [Manifest](reference/manifest)
+* **Creating slices:** [Slice definitions](reference/chisel-releases/slice-definitions) • [chisel.yaml](reference/chisel-releases/chisel.yaml) • [Slice design approaches](explanation/slice-design-approaches) • [Slice a package](how-to/slice-a-package)
+* **Chisel CLI:** [Command reference](reference/cmd/index)
+* **Security:** [Cryptographic information](reference/security)
 
----------
 
 ## How this documentation is organized
 

From 5ff298393396f7d2f3b109af2a98ac4de3dda556 Mon Sep 17 00:00:00 2001
From: Anna Sancho Vaquer <anna.sanchovaquer@canonical.com>
Date: Wed, 2 Sep 2026 16:52:28 +0200
Subject: [PATCH 2/2] feat: Add CODA issue template

Signed-off-by: Anna Sancho Vaquer <anna.sanchovaquer@canonical.com>
---
 .github/ISSUE_TEMPLATE/coda.md | 43 ++++++++++++++++++++++++++++++++++
 1 file changed, 43 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/coda.md

diff --git a/.github/ISSUE_TEMPLATE/coda.md b/.github/ISSUE_TEMPLATE/coda.md
new file mode 100644
index 0000000..2ef0025
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/coda.md
@@ -0,0 +1,43 @@
+---
+name: CODA issue template
+about: Applies the CODA issue structure.
+title: 'CODA: short description'
+labels: 'coda'
+---
+
+# Background
+
+<!-- Expand on the title and provide clear context that helps users understand the product and the problem. -->
+
+# Task
+
+<!-- Include the expected steps for the completion of the issue, including the repository where the PR must be opened in and mention the requirement of signing the [Canonical contributor license agreement](https://ubuntu.com/legal/contributors). -->
+
+# Prerequisites
+
+<!-- This section is optional. Explicitly state if specific domain knowledge or tools are required, or if the issue is beginner-friendly. -->
+
+# What you will learn
+
+<!-- Briefly list what the contributor will learn from working on this issue. -->
+
+# Outcome
+
+<!-- Describe the expected result needed to close the issue. -->
+
+# Resources
+
+<!-- List URLs or references that help the contributor research and complete the task. -->
+
+# Mentor
+
+<!-- Add who the mentor of the issue is.
+
+If the mentor is a TA, use: `The mentor for this issue is [GH username]. They are the Technical Author for [Product name].`
+
+If the mentor is not a TA, modify the second sentence accordingly.
+
+If there is no mentor for the issue, use: `This issue does not currently have a mentor. If you are interested in working on it, please leave a comment and we will assign one as soon as possible. Please check our [guidelines for contributors](https://github.com/canonical/open-documentation-academy/blob/main/CONTRIBUTING.md) in the meantime.`
+Include contact information, for example: -->
+
+Please feel free to reach out to the mentor on [Matrix](<INSERT_YOUR_MATRIX_DM_ADDRESS_HERE>) if you have further questions.