Merge pull request #26 from BIRDSOpenSource/development

Development
BIRDSOpenSource · Dec 9, 2024 · 48d79af · 48d79af
2 parents 13cc52b + fe586d6
commit 48d79af
Show file tree

Hide file tree

Showing 369 changed files with 189,765 additions and 62 deletions.
diff --git a/Gemfile b/Gemfile
@@ -6,7 +6,6 @@ gem "just-the-docs", "0.5.4" # pinned to the current release
 
 group :jekyll_plugins do
     gem "jekyll-polyglot"
-    gem 'jekyll-spaceship'
     gem "webrick" # required when using Ruby >= 3 and Jekyll <= 4.2.2
     gem "base64", "~> 0.2.0"
 end
diff --git a/Gemfile.lock b/Gemfile.lock
@@ -15,14 +15,13 @@ GEM
     ffi (1.17.0-x86_64-darwin)
     ffi (1.17.0-x86_64-linux-gnu)
     forwardable-extended (2.6.0)
-    gemoji (3.0.1)
-    google-protobuf (4.29.0-arm64-darwin)
+    google-protobuf (4.29.1-arm64-darwin)
       bigdecimal
       rake (>= 13)
-    google-protobuf (4.29.0-x86_64-darwin)
+    google-protobuf (4.29.1-x86_64-darwin)
       bigdecimal
       rake (>= 13)
-    google-protobuf (4.29.0-x86_64-linux)
+    google-protobuf (4.29.1-x86_64-linux)
       bigdecimal
       rake (>= 13)
     http_parser.rb (0.8.0)
@@ -50,11 +49,6 @@ GEM
       sass-embedded (~> 1.54)
     jekyll-seo-tag (2.8.0)
       jekyll (>= 3.8, < 5.0)
-    jekyll-spaceship (0.10.2)
-      gemoji (~> 3.0)
-      jekyll (>= 3.6, < 5.0)
-      nokogiri (~> 1.6)
-      rainbow (~> 3.0)
     jekyll-watch (2.2.1)
       listen (~> 3.0)
     just-the-docs (0.5.4)
@@ -70,25 +64,17 @@ GEM
       rb-fsevent (~> 0.10, >= 0.10.3)
       rb-inotify (~> 0.9, >= 0.9.10)
     mercenary (0.4.0)
-    nokogiri (1.16.7-arm64-darwin)
-      racc (~> 1.4)
-    nokogiri (1.16.7-x86_64-darwin)
-      racc (~> 1.4)
-    nokogiri (1.16.7-x86_64-linux)
-      racc (~> 1.4)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
     public_suffix (6.0.1)
-    racc (1.8.1)
-    rainbow (3.1.1)
     rake (13.2.1)
     rb-fsevent (0.11.2)
     rb-inotify (0.11.1)
       ffi (~> 1.0)
     rexml (3.3.9)
     rouge (4.5.1)
     safe_yaml (1.0.5)
-    sass-embedded (1.81.1)
+    sass-embedded (1.82.0)
       google-protobuf (~> 4.28)
       rake (>= 13)
     terminal-table (3.0.2)
@@ -105,7 +91,6 @@ DEPENDENCIES
   base64 (~> 0.2.0)
   jekyll (~> 4.3.2)
   jekyll-polyglot
-  jekyll-spaceship
   just-the-docs (= 0.5.4)
   webrick
 

diff --git a/_adcs-members/adcs-guide.md b/_adcs-members/adcs-guide.md
@@ -8,10 +8,14 @@ lang: en
 # Guide for ADCS Team Members
 {: .no_toc }
 
+<details markdown="block">
+<summary>Table of Contents</summary>
 
 - Table of Contents
 {:toc}
 
+</details>
+
 ## Introduction
 {:toc}
 This introduction is an overview of the project, how it is organised, and how it works.

diff --git a/_bpb-members/bpb-guide.md b/_bpb-members/bpb-guide.md
@@ -8,10 +8,14 @@ lang: en
 # Guide for BPB Team Members
 {: .no_toc }
 
+<details markdown="block">
+<summary>Table of Contents</summary>
 
 - Table of Contents
 {:toc}
 
+</details>
+
 ## Introduction
 {:toc}
 This introduction is an overview of the project, how it is organised, and how it works.

diff --git a/_com-members/com-guide.md b/_com-members/com-guide.md
@@ -8,10 +8,14 @@ lang: en
 # Guide for COM Team Members
 {: .no_toc }
 
+<details markdown="block">
+<summary>Table of Contents</summary>
 
 - Table of Contents
 {:toc}
 
+</details>
+
 ## Introduction
 {:toc}
 This introduction is an overview of the project, how it is organised, and how it works.

diff --git a/_com-members/link-budget.md b/_com-members/link-budget.md
@@ -4,8 +4,16 @@ layout: default
 lang: en
 ---
 
-## *We make space sector capacity building accessible to everyone*
+## Making a Link Budget
+{: .no_toc }
 
+<details markdown="block">
+<summary>Table of Contents</summary>
+
+- Table of Contents
+{:toc}
+
+</details>
 
 ### *Introduction*
 

diff --git a/_config.yml b/_config.yml
@@ -51,12 +51,12 @@ enable_copy_code_button: true
 mermaid:
   # Version of mermaid library
   # Pick an available version from https://cdn.jsdelivr.net/npm/mermaid/
-  version: "9.1.6"
+  version: "11.4.0"
   # Put any additional configuration, such as setting the theme, in _includes/mermaid_config.js
   # See also docs/ui-components/code
   # To load mermaid from a local library, also use the `path` key to specify the location of the library; e.g.
   # for (v10+):
-  # path: "/assets/js/mermaid.esm.min.mjs"
+  path: "/assets/js/mermaid.esm.min.mjs"
   # for (<v10):
   # path: "/assets/js/mermaid.min.js"
   # Note: copy both `mermaid.esm.min.mjs` (v10+) or `mermaid.min.js` (<v10) and the associated `.map` file from the specified version of `mermaid/dist` to `/assets/js/`.

diff --git a/_eps-members/eps-guide.md b/_eps-members/eps-guide.md
@@ -8,10 +8,14 @@ lang: en
 # Guide for EPS Team Members
 {: .no_toc }
 
+<details markdown="block">
+<summary>Table of Contents</summary>
 
 - Table of Contents
 {:toc}
 
+</details>
+
 ## Introduction
 {:toc}
 This introduction is an overview of the project, how it is organised, and how it works.

diff --git a/_eps-members/power-budget.md b/_eps-members/power-budget.md
@@ -4,8 +4,16 @@ layout: default
 lang: en
 ---
 
-## *We make space sector capacity building accessible to everyone*
+# Making a Power Budget
+{: .no_toc }
 
+<details markdown="block">
+<summary>Table of Contents</summary>
+
+- Table of Contents
+{:toc}
+
+</details>
 
 ### *Introduction*
 

diff --git a/_includes/mermaid_config.js b/_includes/mermaid_config.js
@@ -1,2 +1 @@
-// _includes/mermaid_config.js
 {}
diff --git a/_obc-members/obc-guide.md b/_obc-members/obc-guide.md
@@ -8,10 +8,14 @@ lang: en
 # Guide for OBC Team Members
 {: .no_toc }
 
+<details markdown="block">
+<summary>Table of Contents</summary>
 
 - Table of Contents
 {:toc}
 
+</details>
+
 ## Introduction
 {:toc}
 This introduction is an overview of the project, how it is organised, and how it works.

diff --git a/_obc-members/software-design.md b/_obc-members/software-design.md
@@ -4,7 +4,16 @@ layout: default
 lang: en
 ---
 
-# Title
+# Software Design
+{: .no_toc}
+
+<details markdown="block">
+<summary>Table of Contents</summary>
+
+- Table of Contents
+{:toc}
+
+</details>
 
 > If you need more information about how to fill in this template, read the accompanying [guide](./guide_how-to.md).
 >

diff --git a/_project-managers/pm-cdr.md b/_project-managers/pm-cdr.md
@@ -7,8 +7,15 @@ lang: en
 # Critical Design Review 
 {: .no_toc }
 
-Each subsystem needs to understannd what they are required to present at each milestone review.
+<details markdown="block">
+<summary>Table of Contents</summary>
 
+- Table of Contents
+{:toc}
+
+</details>
+
+Each subsystem needs to understand what they are required to present at each milestone review.
 
 ## Before the review
 

diff --git a/_project-managers/pm-choose-a-dms.md b/_project-managers/pm-choose-a-dms.md
@@ -3,8 +3,17 @@ title: Choose a DMS
 layout: default
 lang: en
 ---
+
 # Choose a Documentation Management System
 
+<details markdown="block">
+<summary>Table of Contents</summary>
+
+- Table of Contents
+{:toc}
+
+</details>
+
 A document management system (DMS) is usually a computerized system used to store, share, track and manage files or documents. 
 
 Teams, SharePoint, OneDrive, and Google Drive can all be used for document management (DMS)

diff --git a/_project-managers/pm-encourage-team.md b/_project-managers/pm-encourage-team.md
@@ -7,6 +7,13 @@ lang: en
 # Encourage your team
 {: .no_toc }
 
+<details markdown="block">
+<summary>Table of Contents</summary>
+
+- Table of Contents
+{:toc}
+
+</details>
 
 ## Get to know your members
 

diff --git a/_project-managers/pm-freq-coord.md b/_project-managers/pm-freq-coord.md
@@ -7,6 +7,14 @@ lang: en
 # Organise Frequency Coordination
 {: .no_toc }
 
+<details markdown="block">
+<summary>Table of Contents</summary>
+
+- Table of Contents
+{:toc}
+
+</details>
+
 Because of the diffderence in process lenght per country it is best to start this as sooon as possible and start having dialogue with the governing body.
 
 

diff --git a/_project-managers/pm-frr.md b/_project-managers/pm-frr.md
@@ -7,10 +7,13 @@ lang: en
 # Organise Flight Readiness Review
 {: .no_toc }
 
+<details markdown="block">
+<summary>Table of Contents</summary>
 
+- Table of Contents
+{:toc}
 
-
-
+</details>
 
 Testing and integration
 

diff --git a/_project-managers/pm-guide.md b/_project-managers/pm-guide.md
@@ -8,10 +8,14 @@ lang: en
 # Guide for Project Managers
 {: .no_toc }
 
+<details markdown="block">
+<summary>Table of Contents</summary>
 
 - Table of Contents
 {:toc}
 
+</details>
+
 ## Introduction
 {:toc}
 A project manager (PM) is responsible for planning, organizing, and directing a project from start to finish. PMs ensure that projects are completed on time, on budget, and meet all requirements. They also act as the main point of communication between clients, vendors, and teammates. 

diff --git a/_project-managers/pm-identify-analyze-risks.md b/_project-managers/pm-identify-analyze-risks.md
@@ -7,6 +7,13 @@ lang: en
 # Identify and analyze risks
 {: .no_toc }
 
+<details markdown="block">
+<summary>Table of Contents</summary>
+
+- Table of Contents
+{:toc}
+
+</details>
 
 Project managers have several risk management tasks, including:
 

diff --git a/_project-managers/pm-lifecycle-plan.md b/_project-managers/pm-lifecycle-plan.md
@@ -7,6 +7,14 @@ lang: en
 # Plan satellite lifecycle
 {: .no_toc }
 
+<details markdown="block">
+<summary>Table of Contents</summary>
+
+- Table of Contents
+{:toc}
+
+</details>
+
 Most student satellite projects aim to start and complete satellite design and launch within two years. To achieve this requires meticulate planning and forsight.
 
 - Table of Contents

diff --git a/_project-managers/pm-mdr.md b/_project-managers/pm-mdr.md
@@ -7,6 +7,14 @@ lang: en
 # Mission Definition Review 
 {: .no_toc }
 
+<details markdown="block">
+<summary>Table of Contents</summary>
+
+- Table of Contents
+{:toc}
+
+</details>
+
 What does a project manager need to know and do before MDR?
 
 The PM should ensure each subsystem understands what they are required to present at each milestone review.

diff --git a/_project-managers/pm-monitor-risk.md b/_project-managers/pm-monitor-risk.md
@@ -7,6 +7,13 @@ lang: en
 # Communicate and Monitor risks
 {: .no_toc }
 
+<details markdown="block">
+<summary>Table of Contents</summary>
+
+- Table of Contents
+{:toc}
+
+</details>
 
 ## Communicating risks: 
 Communicating the right risk to the right person at the right level. 

diff --git a/_project-managers/pm-naming-conventions.md b/_project-managers/pm-naming-conventions.md
@@ -3,7 +3,17 @@ title: Naming Conventions
 layout: default
 lang: en
 ---
+
 # File/ Folder Naming Conventions
+{: .no_toc }
+
+<details markdown="block">
+<summary>Table of Contents</summary>
+
+- Table of Contents
+{:toc}
+
+</details>
 
 In addition to using a strong folder structure, appropriately naming your files and folders is a boon to managing your records properly. However, it requires a establishing a system that's robust enough to help you organize and find your information while being straightforward enough that it can be understood and implemented without significant effort. This resource is designed to help you strike that appropriate balance.