Next button

.github/workflows/pages.yml → .github/workflows/jekyll.yml

@@ -7,6 +7,7 @@
 name: Deploy Jekyll site to Pages
 
 on:
+  # Runs on pushes targeting the default branch
   push:
     branches: ["main"]
 
@@ -19,35 +20,37 @@ permissions:
   pages: write
   id-token: write
 
-# Allow one concurrent deployment
+# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
 concurrency:
   group: "pages"
-  cancel-in-progress: true
+  cancel-in-progress: false
 
 jobs:
   # Build job
   build:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
       - name: Setup Ruby
-        uses: ruby/setup-ruby@v1
+        # https://github.com/ruby/setup-ruby/releases/tag/v1.207.0
+        uses: ruby/setup-ruby@4a9ddd6f338a97768b8006bf671dfbad383215f4
         with:
           ruby-version: '3.1' # Not needed with a .ruby-version file
           bundler-cache: true # runs 'bundle install' and caches installed gems automatically
           cache-version: 0 # Increment this number if you need to re-download cached gems
       - name: Setup Pages
         id: pages
-        uses: actions/configure-pages@v3
+        uses: actions/configure-pages@v5
       - name: Build with Jekyll
         # Outputs to the './_site' directory by default
         run: bundle exec jekyll build --baseurl "${{ steps.pages.outputs.base_path }}"
         env:
           JEKYLL_ENV: production
       - name: Upload artifact
         # Automatically uploads an artifact from the './_site' directory by default
-        uses: actions/upload-pages-artifact@v1
+        uses: actions/upload-pages-artifact@v3
 
   # Deployment job
   deploy:
@@ -59,4 +62,4 @@ jobs:
     steps:
       - name: Deploy to GitHub Pages
         id: deployment
-        uses: actions/deploy-pages@v2
+        uses: actions/deploy-pages@v4

Gemfile

@@ -5,3 +5,8 @@ gem "jekyll", "~> 4.3.3" # installed by `gem jekyll`
 
 gem "just-the-docs", "0.8.1" # pinned to the current release
 # gem "just-the-docs"        # always download the latest release
+
+gem "csv"
+gem "base64"
+gem "logger"
+gem "bigdecimal"

Gemfile.lock

@@ -3,15 +3,20 @@ GEM
   specs:
     addressable (2.8.6)
       public_suffix (>= 2.0.2, < 6.0)
+    base64 (0.2.0)
+    bigdecimal (3.1.9)
     colorator (1.1.0)
     concurrent-ruby (1.2.2)
+    csv (3.3.3)
     em-websocket (0.5.3)
       eventmachine (>= 0.12.9)
       http_parser.rb (~> 0)
     eventmachine (1.2.7)
     ffi (1.16.3)
     forwardable-extended (2.6.0)
     google-protobuf (3.25.1)
+    google-protobuf (3.25.1-arm64-darwin)
+    google-protobuf (3.25.1-x86_64-darwin)
     http_parser.rb (0.8.0)
     i18n (1.14.1)
       concurrent-ruby (~> 1.0)
@@ -52,6 +57,7 @@ GEM
     listen (3.8.0)
       rb-fsevent (~> 0.10, >= 0.10.3)
       rb-inotify (~> 0.9, >= 0.9.10)
+    logger (1.7.0)
     mercenary (0.4.0)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
@@ -63,8 +69,13 @@ GEM
     rexml (3.2.6)
     rouge (4.2.0)
     safe_yaml (1.0.5)
+    sass-embedded (1.69.5)
+      google-protobuf (~> 3.23)
+      rake (>= 13.0.0)
     sass-embedded (1.69.5-arm64-darwin)
       google-protobuf (~> 3.23)
+    sass-embedded (1.69.5-x64-mingw-ucrt)
+      google-protobuf (~> 3.23)
     sass-embedded (1.69.5-x86_64-darwin)
       google-protobuf (~> 3.23)
     sass-embedded (1.69.5-x86_64-linux-gnu)
@@ -76,12 +87,20 @@ GEM
 
 PLATFORMS
   arm64-darwin-23
+  arm64-darwin-24
+  ruby
+  x64-mingw-ucrt
+  x86_64-darwin-22
   x86_64-darwin-23
   x86_64-linux
 
 DEPENDENCIES
+  base64
+  bigdecimal
+  csv
   jekyll (~> 4.3.3)
   just-the-docs (= 0.8.1)
+  logger
 
 BUNDLED WITH
-   2.3.26
+   2.6.7

README.md

@@ -1 +1,124 @@
-# open-devsecops Website
+<!-- PROJECT SHIELDS -->
+[![contributors][contributors-shield]][contributors-url]
+[![commits][commits-shield]][commits-url]
+
+<!-- PROJECT LOGO --> 
+<br />
+<div align="center">
+  <a href=“katieshi413.github.io/open-devsecops.github.io/”> 
+    <img src="assets/images/opendevsecops-transparent.png" alt="open DevSecOps triangle logo" width="200" height="200">
+  </a>
+  <h1 align="center">Open DevSecOps v2</h1>
+</div>
+
+<!-- TABLE OF CONTENTS -->
+<details>
+  <summary>Table of Contents</summary>
+  <ol>
+    <li>
+      <a href="#about-the-project">About The Project</a>
+      <ul>
+        <li><a href="#built-with">Built With</a></li>
+      </ul>
+    </li>
+    <li>
+      <a href="#getting-started">Getting Started</a>
+      <ul>
+        <li><a href="#prerequisites">Prerequisites</a></li>
+        <li><a href="#installation">Installation</a></li>
+      </ul>
+    </li>
+    <li><a href="#contact">Contact</a></li>
+  </ol>
+</details>
+
+<!-- ABOUT THE PROJECT -->
+
+## About The Project
+
+Many students entering the software industry are unprepared for the newest expectations of entry-level roles, where understanding security and efficient operations are the bare-minimum at every phase of the software development lifecycle. The "Open-DevSecOps" project addresses this significant gap in education concerning DevSecOps and CI/CD principles. Our extensively researched online modules aim to offer a free educational service to enhance the understanding and application of these crucial skills. This project strives to provide essential up-to-date training, and shape the security industry's future for the better starting with every new-grad employee. 
+
+### Final Website
+
+www.katieshi413.github.io/open-devsecops.github.io/
+
+### Final Presentation
+
+https://docs.google.com/presentation/d/1ESrzQka0eZ1L1KLqiXgI0yj2_FuhhFSfokiGwJE8K3o/edit?usp=sharing
+
+### Built With
+
+* [![Jekyll][Jekyll]][Jekyll-url]
+* [![Ruby][Ruby]][Ruby-url]
+* [![Markdown][Markdown]][Markdown-url]
+
+
+<p align=“right”>(<a href=“#readme-top”>back to top</a>)</p>
+
+<!-- GETTING STARTED -->
+
+## Getting Started
+
+ To get a local copy up and running follow these steps.
+
+### Prerequisites
+-   Ruby 3.4.1
+-   [Bundler](https://bundler.io/)
+-   [Jekyll](https://jekyllrb.com/) 
+
+### Installation
+
+1.  Install Ruby and Bundler
+
+    ```sh
+    # If you haven’t already, install Ruby (version 3.4.1), then install Bundler:
+    gem install bundler
+    ```
+
+2.  Navigate to the project directory
+
+    ```sh
+    cd your-project-directory
+    ```
+
+3.  Install project dependencies
+
+    ```sh
+    bundle install
+    ```
+
+4.  Serve the site locally
+
+    ```sh
+    bundle exec jekyll serve
+    ```
+5.  Open your browser and visit:
+
+    ```sh
+    http://localhost:4000
+    ```
+
+<p align=“right”>(<a href=“#readme-top”>back to top</a>)</p>
+
+<!-- CONTACT -->
+## Contact
+
+<p>Katie Shi - <a href="https://www.linkedin.com/in/katie-shi-ab4973185/">LinkedIn</a> - <a href= "mailto: katieshi413@gmail.com"> katieshi413@gmail.com </a></p>
+<p>Emily Choi - <a href="https://www.linkedin.com/in/emily-choii/">LinkedIn</a> - <a href= "mailto: eemilychoi@gmail.com"> eemilychoi@gmail.com </a></p>
+<p>Jocelyn Margarones - <a href="https://www.linkedin.com/in/jocelyn-margarones-666770236/">LinkedIn</a> - <a href= "mailto: jsmargarones@gmail.com"> jsmargarones@gmail.com </a></p>
+<p>Mor Vered - <a href="https://www.linkedin.com/in/mor-vered-470a36257/">LinkedIn</a> - <a href= "mailto: mvered9@gmail.com"> mvered9@gmail.com </a></p>
+<p>Mira Nair - <a href="https://www.linkedin.com/in/miranair/">LinkedIn</a> - <a href= "mailto: miranair004@gmail.com"> miranair004@gmail.com </a></p>
+
+<p align="right">(<a href="#readme-top">back to top</a>)</p>
+
+<!-- MARKDOWN LINKS & IMAGES -->
+[contributors-shield]: https://img.shields.io/github/contributors/katieshi413/open-devsecops.github.io?style=for-the-badge&color=rgb(68%2C%20204%2C%2017)
+[contributors-url]: https://github.com/katieshi413/open-devsecops.github.io/graphs/contributors
+[commits-shield]: https://img.shields.io/github/commit-activity/t/katieshi413/open-devsecops.github.io?style=for-the-badge
+[commits-url]: https://github.com/katieshi413/open-devsecops.github.io/commits/main/
+[Jekyll]: https://img.shields.io/static/v1?style=for-the-badge&message=Jekyll&color=CC0000&logo=Jekyll&logoColor=FFFFFF&label=
+[Jekyll-url]: https://jekyllrb.com/
+[Ruby]: https://img.shields.io/badge/Ruby-CC342D?logo=Ruby&logoColor=white
+[Ruby-url]: https://www.ruby-lang.org/en/
+[Markdown]: https://img.shields.io/badge/markdown-%23000000.svg?style=for-the-badge&logo=markdown&logoColor=white
+[Markdown-url]: https://www.markdownguide.org/

_config.yml

@@ -2,12 +2,18 @@ title: open-devsecops
 description: 'From Classroom to Industry: Bridging the DevSecOps Knowledge Gap with Open, Practical Learning.'
 theme: just-the-docs
 
-logo: "/assets/images/opendevsecops-transparent.png"
-favicon_ico: "/assets/images/opendevsecops-favicon.ico"
+logo: "/assets/images/2.0logobig.png"
+favicon_ico: "/assets/images/2.0logobig.png"
 
-url: https://open-devsecops.github.io
+# url: https://open-devsecops.github.io
+url: "https://katieshi413.github.io"
+baseurl: "/open-devsecops.github.io"
 search_enabled: false
 
+include:
+   - assets/js/quiz.js
+   - assets/js/quiz-reset.js
+
 aux_links:
   Github: https://github.com/open-devsecops
   Contribute: https://github.com/open-devsecops/open-devsecops.github.io
@@ -24,4 +30,8 @@ callouts:
     color: blue
   lab:
     title: Access The Lab
-    color: purple
+    color: purple
+
+sass:
+  sass_dir: _sass
+  style: compressed

_data/quizzes/topic1/chapter1.yml

@@ -0,0 +1,43 @@
+questions:
+    - prompt: "What is the primary purpose of the Software Development Life Cycle (SDLC)?"
+      options:
+        - "To design user interfaces for software applications"
+        - "To manage and structure software development and maintenance through distinct phases"
+        - "To write code in a specific programming language"
+        - "To automate deployment using CI/CD tools"
+      correct_index: 1
+      explanation: "The SDLC is a structured process that helps manage and guide software development and maintenance through specific phases."
+
+    - prompt: "Which of the following is NOT one of the phases in the traditional SDLC?"
+      options:
+        - "Design"
+        - "Test"
+        - "Automate"
+        - "Deploy"
+      correct_index: 2
+      explanation: "<b>Automate</b> is not a standard SDLC phase; the typical phases include Planning, Design, Implement, Test, Deploy, and Maintain."
+
+    - prompt: "True or False: The <b>Maintain</b> phase in SDLC focuses on releasing software into production."
+      options:
+        - "True"
+        - "False"
+      correct_index: 1
+      explanation: "The <b>Deploy</b> phase handles release into production, while the <b>Maintain</b> phase involves ongoing updates and support."
+
+    - prompt: "What is a key benefit of following a structured SDLC process?"
+      options:
+        - "Faster typing speed for developers"
+        - "Reduces testing requirements"
+        - "Ensures secure and reliable software delivery"
+        - "Eliminates the need for project planning"
+      correct_index: 2
+      explanation: "One of the main benefits of SDLC is enabling faster, more secure, and reliable delivery of software through structured processes."
+
+    - prompt: "Which SDLC methodology is best suited for projects with fixed, well-defined requirements?"
+      options:
+        - "Waterfall"
+        - "Agile"
+        - "Scrum"
+        - "Iterative"
+      correct_index: 0
+      explanation: "Waterfall is ideal for projects where requirements are fixed and unlikely to change."

_data/quizzes/topic1/chapter2.yml

@@ -0,0 +1,41 @@
+questions:
+    - prompt: "What is one key issue that arises when development and operations teams work in isolation?"
+      options:
+        - "Decreased development speed"
+        - "Better coordination between teams"
+        - "Conflicting goals and communication gaps"
+        - "More secure deployment pipelines"
+      correct_index: 2
+      explanation: "Isolated Dev and Ops teams often face communication gaps and misaligned objectives, leading to inefficiencies."
+
+    - prompt: "True or False: Manual testing and deployment processes often result in slower release cycles and delayed feedback."
+      options:
+        - "True"
+        - "False"
+      correct_index: 0
+      explanation: "Manual processes slow down software delivery, making it harder to respond quickly to feedback."
+
+    - prompt: "Which of the following best explains the 'But it works on my machine' syndrome?"
+      options:
+        - "A feature passes QA but fails in production due to network issues"
+        - "Code behaves inconsistently across environments due to configuration mismatches"
+        - "A user reports a bug that developers can’t reproduce"
+        - "Developers forget to merge the correct branch"
+      correct_index: 1
+      explanation: "Environment inconsistencies lead to unexpected behavior that doesn't match the developer’s local setup."
+
+    - prompt: "Fill in the blank: Manual infrastructure scaling increases the risk of __________ due to human error and slow responsiveness."
+      options:
+        - "Bugs"
+        - "Data corruption"
+        - "Deployment automation"
+        - "System instability"
+      correct_index: 3
+      explanation: "Manual processes are more prone to mistakes and can't respond quickly to load changes, causing instability."
+
+    - prompt: "True or False: DevOps is only about automation tools and does not affect team culture or communication."
+      options:
+        - "True"
+        - "False"
+      correct_index: 1
+      explanation: "DevOps promotes collaboration and culture change, not just tool adoption."