Tools Verify using Shell

Computers and Terminals
Setup a Personal GitHub Pages Project
Shell Script and Variables
Describing the Outputs of the Variables
Project Setup and Analysis with Bash Scripts
Run Server on localhost
Development Support
Student Requirements
History
GitHub Pages setup
- Tool requirements
- Development Environment Setup
Run Server on localhost
Development Support
Env, Git, and GitHub
Advanced Shell project
Display Shell commands help using man
Tool Version List

Computers and Terminals

A brief overview of Terminal and Linux is a step on your way to becoming a Linux expert. When a computer boots up, a kernel (MacOS, Windows, Linux) is started. This kernel is the core of the operating system and manages hardware resources. Above the kernel, various applications run, including the shell and terminal, which allow users to interact with the system using a basic set of commands provided by the kernel.

Typically, casual users interact with the system through a Desktop User Interface (UI) that is started by the computer’s boot-up processes. However, to interact directly with the shell, users can run a “terminal” application through the Desktop UI. Additionally, VS Code provides the ability to activate a “terminal” within its editing environment, making it convenient for developers to execute commands without leaving the code editor.

In this next phase, we will use a Jupyter notebook to perform Linux commands through a terminal. The Jupyter notebook is an application that runs above the kernel, providing an interactive environment for writing and executing code, including shell commands. This setup allows us to seamlessly integrate code execution, data analysis, and documentation in one place, enhancing our productivity and learning experience.

Setup a Personal GitHub Pages Project

You will be making a personal copy of the course repository. Be sure to have a GitHub account!!!

Use the Green “Use this Template” button on the portfolio_2025 repository page to set up your personal GitHub Pages repository.
Create a new repository.
Fill in the dialog and select the Repository Name to be under your GitHub ID ownership.
After this is complete, use the Green “Code” button on the newly created repository page to capture your “Project Repo” name.

In the next few code cells, we will run a bash (shell) script to pull a GitHub project.

Shell Script and Variables

We will ultimately run a bash (shell) script to pull a GitHub project. This next script simply sets up the necessary environment variables to tell the script the location of repository from GitHub and where to copy the output.

For now, focus on each line that begins with export. These are shell variables. Each line has a name (after the keyword export) and a value (after the equal sign).

Here is a full description:

Creates a temporary file /tmp/variables.sh to store environment variables.
Sets the project_dir variable to your home directory with a subdirectory named nighthawk. You can change nighthawk to a different name to test your git clone.
Sets the project variable to a subdirectory within project_dir named portfolio_2025. You can change portfolio_2025 to the name of your project.
Sets the project_repo variable to the URL of the GitHub repository. Change this to the project you created from the portfolio_2025 template.

By running this script, you will prepare your environment for cloning and working on your GitHub project. This is an essential step in setting up your development environment and ensuring that all dependencies are correctly configured.

%%script bash

# Dependency Variables, set to match your project directories

cat <<EOF > /tmp/variables.sh
export project_dir=$HOME/nighthawk  # change nighthawk to different name to test your git clone
export project=\$project_dir/student_2025  # change student_2025 to name of project from git clone
export project_repo="https://github.com/nighthawkcoders/student_2025.git"  # change to project you created from portfolio_2025 template 
EOF

Describing the Outputs of the Variables

The next script will extract the saved variables and display their values. Here is a description of the commands:

The source command loads the variables that we saved in the /tmp/variables.sh file in the previous code cell.
The echo commands display the contents of the named variables:
- project_dir: The directory where your project is located.
- project: The specific project directory within project_dir.
- project_repo: The URL of the GitHub repository.

By running this script, you can verify that the environment variables are correctly set in your development environment. If they don’t match up, go back to the previous code cell and make the necessary corrections.

%%script bash

# Extract saved variables
source /tmp/variables.sh

# Output shown title and value variables
echo "Project dir: $project_dir"
echo "Project: $project"
echo "Repo: $project_repo"

Project dir: /home/avanthikadaita/nighthawk
Project: /home/avanthikadaita/nighthawk/avanthika_2025
Repo: https://github.com/avanthika/avanthika_2025.git

Project Setup and Analysis with Bash Scripts

The bash scripts that follow automate what was done in the Tools Installation procedures with regards to cloning a GitHub project. Doing this in a script fashion adds the following benefits:

After completing these steps, we will have notes on how to set up and verify a project.
By reviewing these commands, you will start to learn the basics of Linux.
By setting up these code cells, you will be learning how to develop automated scripts using Shell programming.
You will learn that pretty much anything we type on a computer can be automated through the use of variables and a coding language.

Pull Code

Pull code from GitHub to your machine. This is a bash script, a sequence of commands, that will create a project directory and add the “project” from GitHub to the vscode directory. There is conditional logic to make sure that the clone only happens if it does not (!) exist. Here are some key elements in this code:

cd command (change directory), remember this from the terminal session.
if statements (conditional statements, called selection statements by College Board), code inside only happens if the condition is met.

Run the script two times and you will see that the output changes. In the second run, the files exist and it impact the flow of the code.

%%script bash

# Extract saved variables
source /tmp/variables.sh

echo "Using conditional statement to create a project directory and project"

cd ~    # start in home directory

# Conditional block to make a project directory
if [ ! -d $project_dir ]
then 
    echo "Directory $project_dir does not exist... making directory $project_dir"
    mkdir -p $project_dir
fi
echo "Directory $project_dir exists." 

# Conditional block to git clone a project from project_repo
if [ ! -d $project ]
then
    echo "Directory $project does not exist... cloning $project_repo"
    cd $project_dir
    git clone $project_repo
    cd ~
fi
echo "Directory $project exists."

Using conditional statement to create a project directory and project
Directory /Users/avanthikadaita exists.
Directory /Users/avanthikadaita/avanthika_2025 exists.

Look at Files in GitHub Project

All computers contain files and directories. The clone brought more files from the cloud to your machine. Review the bash shell script, observe the commands that show and interact with files and directories. These were used during setup.

ls lists computer files in Unix and Unix-like operating systems.
cd offers a way to navigate and change the working directory.
pwd prints the working directory.
echo is used to display a line of text/string that is passed as an argument.

%%script bash

# Extract saved variables
source /tmp/variables.sh

echo "Navigate to project, then navigate to area wwhere files were cloned"
cd $project
pwd

echo ""
echo "list top level or root of files with project pulled from github"
ls

Navigate to project, then navigate to area wwhere files were cloned

/Users/avanthikadaita/avanthika_2025

list top level or root of files with project pulled from github

404.html
Gemfile
Gemfile.lock
LICENSE
Makefile
README.md
README4YML.md
_config.yml
_includes
_layouts
_notebooks
_posts
_sass
_site
assets
images
index.md
navigation
requirements.txt
scripts
venv

Look at File List with Hidden and Long Attributes

Most Linux commands have options to enhance behavior. The enhanced listing below shows permission bits, owner of the file, size, and date.

Some useful ls flags:

-a: List all files including hidden files.
-l: List in long format.
-h: Human-readable file sizes.
-t: Sort by modification time.
-R: Reverse the order of the sort.

ls reference

%%script bash

# Extract saved variables
source /tmp/variables.sh

echo "Navigate to project, then navigate to area wwhere files were cloned"
cd $project
pwd

echo ""
echo "list all files in long format"
ls -al   # all files -a (hidden) in -l long listing

total 144
drwxr-xr-x@  28 avanthikadaita  staff    896 Aug 29 08:47 .
drwxr-x---+ 109 avanthikadaita  staff   3488 Aug 29 08:55 ..
drwxr-xr-x@  15 avanthikadaita  staff    480 Aug 28 19:25 .git
drwxr-xr-x@   3 avanthikadaita  staff     96 Aug 27 09:36 .github
-rw-r--r--@   1 avanthikadaita  staff    251 Aug 27 09:36 .gitignore
drwxr-xr-x@   3 avanthikadaita  staff     96 Aug 27 09:36 .vscode
-rw-r--r--    1 avanthikadaita  staff    436 Aug 28 19:15 404.html
drwxr-xr-x    3 avanthikadaita  staff     96 Aug 29 08:47 CSA
-rw-r--r--@   1 avanthikadaita  staff    122 Aug 27 09:36 Gemfile
-rw-r--r--@   1 avanthikadaita  staff   7521 Aug 28 19:11 Gemfile.lock
-rw-r--r--@   1 avanthikadaita  staff  11357 Aug 27 09:36 LICENSE
-rw-r--r--@   1 avanthikadaita  staff   3551 Aug 27 17:58 Makefile
-rw-r--r--    1 avanthikadaita  staff  14171 Aug 28 19:15 README.md
-rw-r--r--    1 avanthikadaita  staff     79 Aug 28 19:15 README4YML.md
-rw-r--r--@   1 avanthikadaita  staff    867 Aug 27 19:07 _config.yml
drwxr-xr-x@  19 avanthikadaita  staff    608 Aug 28 19:15 _includes
drwxr-xr-x@   8 avanthikadaita  staff    256 Aug 28 19:15 _layouts
drwxr-xr-x@   3 avanthikadaita  staff     96 Aug 27 09:36 _notebooks
drwxr-xr-x@   3 avanthikadaita  staff     96 Aug 27 09:36 _posts
drwxr-xr-x@   6 avanthikadaita  staff    192 Aug 27 09:36 _sass
drwxr-xr-x@  21 avanthikadaita  staff    672 Aug 29 08:47 _site
drwxr-xr-x@   5 avanthikadaita  staff    160 Aug 27 09:36 assets
drwxr-xr-x@   5 avanthikadaita  staff    160 Aug 27 09:36 images
-rw-r--r--    1 avanthikadaita  staff   5455 Aug 28 20:59 index.md
drwxr-xr-x@   6 avanthikadaita  staff    192 Aug 28 19:23 navigation
-rw-r--r--@   1 avanthikadaita  staff    565 Aug 27 18:16 requirements.txt
drwxr-xr-x@   9 avanthikadaita  staff    288 Aug 27 11:29 scripts
drwxr-xr-x    7 avanthikadaita  staff    224 Aug 27 18:14 venv

%%script bash

# Extract saved variables
source /tmp/variables.sh

echo "Look for posts"
export posts=$project/_posts  # _posts inside project
cd $posts  # this should exist per fastpages
pwd  # present working directory
ls -lR  # list posts recursively

Look for posts

total 0
drwxr-xr-x@ 5 avanthikadaita  staff  160 Aug 28 19:15 Foundation

./Foundation:
total 8
-rw-r--r--  1 avanthikadaita  staff  2683 Aug 28 19:15 2024-08-21-sprint1_plan_IPYNB_2_.md
drwxr-xr-x@ 5 avanthikadaita  staff   160 Aug 28 19:15 A-pair_programming
drwxr-xr-x  8 avanthikadaita  staff   256 Aug 28 19:15 B-tools_and_equipment

./Foundation/A-pair_programming:
total 48
-rw-r--r--  1 avanthikadaita  staff   5433 Aug 28 19:15 2023-08-16-pair_programming.md
-rw-r--r--  1 avanthikadaita  staff   3242 Aug 28 19:15 2023-08-16-pair_showcase_IPYNB_2_.md
-rw-r--r--  1 avanthikadaita  staff  10043 Aug 28 19:15 2023-08-17-pair_habits_IPYNB_2_.md

./Foundation/B-tools_and_equipment:
total 200
-rw-r--r--  1 avanthikadaita  staff   8196 Aug 28 19:15 2023-08-19-devops_accounts_IPYNB_2_.md
-rw-r--r--  1 avanthikadaita  staff   4949 Aug 28 19:15 2023-08-21-devops_tools-home_IPYNB_2_.md
-rw-r--r--  1 avanthikadaita  staff  18793 Aug 28 19:15 2023-08-21-devops_tools-setup_IPYNB_2_.md
-rw-r--r--  1 avanthikadaita  staff  20139 Aug 29 08:58 2023-08-22-devops_tools-verify_IPYNB_2_.md
-rw-r--r--  1 avanthikadaita  staff  25977 Aug 28 19:15 2023-08-23-devops-githhub_pages-play_IPYNB_2_.md
-rw-r--r--  1 avanthikadaita  staff   9117 Aug 28 19:15 2023-08-23-devops-hacks_IPYNB_2_.md

%%script bash

# Extract saved variables
source /tmp/variables.sh

echo "Look for notebooks"
export notebooks=$project/_notebooks  # _notebooks is inside project
cd $notebooks   # this should exist per fastpages
pwd  # present working directory
ls -lR  # list notebooks recursively

Look for notebooks

total 0
drwxr-xr-x@ 5 avanthikadaita  staff  160 Aug 28 19:15 Foundation

./Foundation:
total 8
-rw-r--r--  1 avanthikadaita  staff  3509 Aug 28 19:15 2024-08-21-sprint1_plan.ipynb
drwxr-xr-x@ 4 avanthikadaita  staff   128 Aug 28 19:15 A-pair_programming
drwxr-xr-x@ 8 avanthikadaita  staff   256 Aug 28 19:15 B-tools_and_equipment

./Foundation/A-pair_programming:
total 32
-rw-r--r--  1 avanthikadaita  staff   3918 Aug 28 19:15 2023-08-16-pair_showcase.ipynb
-rw-r--r--  1 avanthikadaita  staff  11624 Aug 28 19:15 2023-08-17-pair_habits.ipynb

./Foundation/B-tools_and_equipment:
total 240
-rw-r--r--  1 avanthikadaita  staff   9767 Aug 28 19:15 2023-08-19-devops_accounts.ipynb
-rw-r--r--  1 avanthikadaita  staff   5931 Aug 28 19:15 2023-08-21-devops_tools-home.ipynb
-rw-r--r--  1 avanthikadaita  staff  24514 Aug 28 19:15 2023-08-21-devops_tools-setup.ipynb
-rw-r--r--  1 avanthikadaita  staff  31180 Aug 29 09:11 2023-08-22-devops_tools-verify.ipynb
-rw-r--r--  1 avanthikadaita  staff  32309 Aug 28 19:15 2023-08-23-devops-githhub_pages-play.ipynb
-rw-r--r--  1 avanthikadaita  staff  11345 Aug 28 19:15 2023-08-23-devops-hacks.ipynb

%%script bash

# Extract saved variables
source /tmp/variables.sh

echo "Look for images, print working directory, list files"
cd $project/images  # this should exist per fastpages
pwd
ls -lR

Look for images, print working directory, list files

total 104
-rw-r--r--@ 1 avanthikadaita  staff  15406 Aug 27 09:36 favicon.ico
-rw-r--r--@ 1 avanthikadaita  staff  34239 Aug 27 09:36 logo.png
drwxr-xr-x@ 3 avanthikadaita  staff     96 Aug 27 09:36 notebooks

./notebooks:
total 0
drwxr-xr-x@ 6 avanthikadaita  staff  192 Aug 27 09:36 foundation

./notebooks/foundation:
total 728
-rw-r--r--@ 1 avanthikadaita  staff  310743 Aug 27 09:36 create_repo.png
-rw-r--r--@ 1 avanthikadaita  staff   29416 Aug 27 09:36 push.jpg
-rw-r--r--@ 1 avanthikadaita  staff   17105 Aug 27 09:36 stage.jpg
-rw-r--r--@ 1 avanthikadaita  staff    6659 Aug 27 09:36 wsl.jpg
(venv) avanthikadaita@Avanthikas-MacBook-Air images % 

Look inside a Markdown File

“cat” reads data from the file and gives its content as output

%%script bash

# Extract saved variables
source /tmp/variables.sh

echo "Navigate to project, then navigate to area wwhere files were cloned"

cd $project
echo "show the contents of README.md"
echo ""

cat README.md  # show contents of file, in this case markdown
echo ""
echo "end of README.md"

# Introduction

Nighthawk Pages is a project designed to support students in their Computer Science and Software Engineering education. It offers a wide range of resources including tech talks, code examples, and educational blogs.

GitHub Pages can be customized by the blogger to support computer science learnings as the student works through the pathway of using Javascript, Python/Flask, Java/Spring.  

## Student Requirements

Del Norte HS students will be required to review their personal GitHub Pages at each midterm and final.  This review will contain a compilation of personal work performed within each significant grading period.

In general, Students and Teachers are expected to use GitHub pages to build lessons, complete classroom hacks, perform work on JavaScript games, and serve as a frontend to full-stack applications.

Exchange of information could be:

1. sharing a file:  `wget "raw-link.ipynb"
2. creating a template from this repository
3. sharing a fork among team members
4. etc.

---

## History

This project is in its 3rd revision (aka 3.0).

The project was initially based on Fastpages. But this project has diverged from those roots into an independent entity.  The decision to separate from Fastpages was influenced by the deprecation of Fastpages by authors.  It is believed by our community that the authors of fastpages turned toward Quatro.  After that change of direction fastpages did not align with the Teacher's goals and student needs. The Nighthawk Pages project has more of a raw development blogging need.

### License

The Apache license has its roots in Fastpages.  Thus, it carries its license forward.  However, most of the code is likely unrecognizable from those roots.

### Key Features

- **Code Examples**: Provides practical coding examples in JavaScript, including a platformer game, and frontend code for user databases using Python and Java backends.
- **Educational Blogs**: Offers instructional content on various topics such as developer tools setup, deployment on AWS, SQL databases, machine learning, and data structures. It utilizes Jupyter Notebooks for interactive lessons and coding challenges.
- **Tools and Integrations**: Features GitHub actions for blog publishing, Utterances for blog commenting, local development support via Makefile and scripts, and styling with the Minima Theme and SASS. It also includes a new integration with GitHub Projects and Issues.

### Contributions

- **Notable Contributions**: Highlights significant contributions to the project, including theme development, search and tagging functionality, GitHub API integration, and the incorporation of GitHub Projects into GitHub pages. Contributors such as Tirth Thakker, Mirza Beg, and Toby Ledder have played crucial roles in these developments.

- **Blog Contributions**:  Often students contribute articles and blogs to this project.  Their names are typically listed in the front matter of their contributing post.

---

## GitHub Pages setup

The absolutes in setup up...

**Activate GitHub Pages Actions**: This step involves enabling GitHub Pages Actions for your project. By doing so, your project will be automatically deployed using GitHub Pages Actions, ensuring that your project is always up to date with the latest changes you push to your repository.

- On the GitHub website for the repository go to the menu: Settings -> Pages ->Build
- Under the Deployment location on the page, select "GitHub Actions".

**Update `_config.yml`**: You need to modify the `_config.yml` file to reflect your repository's name. This configuration is crucial because it ensures that your project's styling is correctly applied, making your deployed site look as intended rather than unstyled or broken.

```text
github_repo: "student_2025" 
baseurl: "/student_2025"

Set Repository Name in Makefile: Adjust the REPO_NAME variable in your Makefile to match your GitHub repository’s name. This action facilitates the automatic updating of posts and notebooks on your local development server, improving the development process.

# Configuration, override port with usage: make PORT=4200
PORT ?= 4100
REPO_NAME ?= student_2025
LOG_FILE = /tmp/jekyll$(PORT).log

Tool requirements

All GitHub Pages websites are managed on GitHub infrastructure and use GitHub version control. Each time we change files in GitHub it initiates a GitHub Action, a continuous integration and development toolset, that rebuilds and publishes the site with Jekyll.

GitHub uses Jekyll to transform your markdown and HTML content into static websites and blogs. Jekyll.
A Linux shell is required to work with this project integration with GitHub Pages, GitHub and VSCode. Ubuntu is the preferred shell, though MacOS shell is supported as well. There will be some key setup scripts that follow in the README.
Visual Studio Code is the Nighthawk Pages author’s preferred code editor and extensible development environment. VSCode has a rich ecosystem of developer extensions that ease working with GitHub Pages, GitHub, and many programming languages. Setting up VSCode and extensions will be elaborated upon in this document.
An anatomy section in this README will describe GitHub Pages and conventions that are used to organize content and files. This includes file names, key coding files, metadata tagging of blogs, styling tooling for blogs, etc.

Development Environment Setup

Comprehensive start. A topic-by-topic guide to getting this project running is published here.

Quick start. A quick start below is a reminder, but is dependent on your knowledge. Only follow this instruction if you need a refresher. Always default to the comprehensive start if any problem occurs.

Clone Repo

Run these commands to obtain the project, then locate into the project directory with the terminal, install an extensive set of tools, and make.

git clone <this-repo> # git clone https://github.com/nighthawkcoders/student_2025.git 
cd <repo-dir>/scripts # cd student_2025

Windows WSL and/or Ubuntu Users

Execute the script: ./activate_ubuntu.sh

macOS Users

Execute the script: ./activate_macos.sh

Kasm Cloud Desktop Users

Execute the script: ./activate.sh

Run Server on localhost

To preview the project you will need to “make” the project.

Bundle install

The very first time you clone run project you will need to run this Ruby command as the final part of your setup.

bundle install

Start the Server

This requires running terminal commands make, make stop, make clean, or make convert to manage the running server. Logging of details will appear in the terminal. A Makefile has been created in the project to support commands and start processes.

Start the server, this is the best choice for initial and iterative development. Note. after the initial make, you should see files automatically refresh in the terminal on VSCode save.

  make

Load web application into the Browser

Start the preview server in the terminal, The terminal output from make shows the server address. “Cmd” or “Ctl” click the http location to open the preview server in a browser. Here is an example Server address message, click on the Server address to load:…

  http://0.0.0.0:4100/student_2025/

Regeneration of web application

Save on “.ipynb” or “.md” file activiates “regeneration”. An example terminal message is below. Refresh the browser to see updates after the message displays.

  Regenerating: 1 file(s) changed at 2023-07-31 06:54:32
      _notebooks/2024-01-04-cockpit-setup.ipynb

Other “make” commands

Terminal messages are generated from background processes. At any time, click return or enter in a terminal window to obtain a prompt. Once you have the prompt you can use the terminal as needed for other tasks. Always return to the root of project cd ~/vscode/student_2025 for all “make” actions.

Stop the preview server

Stopping the server ends the web server applications running process. However, it leaves constructed files in the project in a ready state for the next time you run make.

  make stop

Clean the local web application environment

This command will top the server and “clean” all previously constructed files (ie .ipynb -> .md). This is the best choice when renaming files has created duplicates that are visible when previewing work.

  make clean

Observe build errors

Test Jupyter Notebook conversions (ie .ipynb -> .md), this is the best choice to see if an IPYNB conversion error is occurring.

  make convert

Development Support

File Names in “_posts”, “_notebooks”

There are two primary directories for creating blogs. The “_posts” directory is for authoring in markdown only. The “_notebooks” allows for markdown, pythons, javascript and more.

To name a file, use the following structure (If dates are in the future, review your config.yml setting if you want them to be viewed). Review these naming conventions.

For markdown files in _posts:
- year-month-day-fileName.md
  - GOOD EXAMPLE: 2021-08-02-First-Day.md
  - BAD EXAMPLE: 2021-8-2-first-day.md
  - BAD EXAMPLE: first-day.md
  - BAD EXAMPLE: 2069-12-31-First-Day.md
For Jupyter notebooks in _notebooks:
- year-month-day-fileName.ipynb
  - GOOD EXAMPLE: 2021-08-02-First-Day.ipynb
  - BAD EXAMPLE: 2021-8-2-first-day.ipynb
  - BAD EXAMPLE: first-day.ipynb
  - BAD EXAMPLE: 2069-12-31-First-Day.ipynb

Search

All pages can be searched for using the built-in search bar. This search bar will search for any word in the title of a page or in the page itself. This allows for easily finding pages and information that you are looking for. However, sometimes this may not be desirable so to hide a page from the search you need to add search_exclude: true to the front matter of the page. This will hide the page from appearing when the viewer uses search.

To add pages to the top navigation bar use _config.yml to order and determine which menus you want and how to order them. Review the_config.yml in this project for an example.

Blog Page

There is a blog page that has options for images and a description of the page. This page can help the viewer understand what the page is about and what they can expect to find on the page. The way to add images to a page is to have the following front matter image: /images/file.jpg and then the name of the image that you want to use. The image must be in the images folder. Furthermore, if you would like the file to not show up on the blog page hide: true can be added to the front matter.

SASS support

NIGHTHAWK Pages support a variety of different themes that are each overlaid on top of minima. To use each theme, go to the “_sass/minima/custom-styles.scss” file and simply comment or uncomment the theme you want to use.

To learn about the minima themes search for “GitHub Pages minima” and review the README.

To find a new theme search for “Github Pages Themes”.

Includes

Nighthawk Pages uses liquid syntax to import many common page elements that are present throughout the repository. These common elements are imported from the _includes directory. If you want to add one of these common elements, use liquid syntax to import the desired element to your file. Here’s an example of the liquid syntax used to import: `<h3>

</a>

</h3><p class="post-meta"></p> ` Note that the liquid syntax is surrounded by curly braces and percent signs. This can be used anywhere in the repository.

Layouts

To use or create a custom page layout, make an HTML page inside the _layouts directory, and when you want to use that layout in a file, use the following front matter layout: [your layout here]. All layouts will be written in liquid to define the structure of the page.

Metadata

Metadata, also known as “front matter”, is a set of key-value pairs that can provide additional information to GitHub Pages about .md and .ipynb files. This can and probably will be used in other file types (ie doc, pdf) if we add them to the system.

In the front matter, you can also define things like a title and description for the page. Additional front matter is defined to place content on the “Computer Science Lab Notebook” page. The courses: key will place data on a specific page with the nested week: placing data on a specific row on the page. The type: key in “front matter” will place the blog under the plans, hacks(ToDo), and tangibles columns.

In our files, the front matter is defined at the top of the page or the first markdown cell.
- First, open one of the .md or .ipynb files already included in either your _posts _notebooks folder.
- In the .md file, you should notice something similar to this at the top of the page. To see this in your .ipynb files you will need to double-click the markdown cell at the top of the file.
```
---
toc: true
comments: true
layout: post
title: Jupyter Python Sample
description: Example Blog!!!  This shows code and notes from hacks.
type: ccc
courses: { csa: {week: 5} }
---
```
The front matter will always have ‘—’ at the top and bottom to distinguish it and each key-value pair will be separated by a ‘:’.
Here we can modify things like the title and description.
The type value will tell us which column this is going to appear under the time box supported pages. The “ccc” stands for Code, Code, Code.
The courses will tell us which menu item it will be under, in this case, the csa menu, and the week tells it what row (week) it will appear under that menu. (venv) avanthikadaita@Avanthikas-MacBook-Air avanthika_2025 % cat README.md

Introduction

Nighthawk Pages is a project designed to support students in their Computer Science and Software Engineering education. It offers a wide range of resources including tech talks, code examples, and educational blogs.

GitHub Pages can be customized by the blogger to support computer science learnings as the student works through the pathway of using Javascript, Python/Flask, Java/Spring.

Student Requirements

Del Norte HS students will be required to review their personal GitHub Pages at each midterm and final. This review will contain a compilation of personal work performed within each significant grading period.

In general, Students and Teachers are expected to use GitHub pages to build lessons, complete classroom hacks, perform work on JavaScript games, and serve as a frontend to full-stack applications.

Exchange of information could be:

sharing a file: `wget “raw-link.ipynb”
creating a template from this repository
sharing a fork among team members
etc.

History

This project is in its 3rd revision (aka 3.0).

The project was initially based on Fastpages. But this project has diverged from those roots into an independent entity. The decision to separate from Fastpages was influenced by the deprecation of Fastpages by authors. It is believed by our community that the authors of fastpages turned toward Quatro. After that change of direction fastpages did not align with the Teacher’s goals and student needs. The Nighthawk Pages project has more of a raw development blogging need.

License

The Apache license has its roots in Fastpages. Thus, it carries its license forward. However, most of the code is likely unrecognizable from those roots.

Key Features

Code Examples: Provides practical coding examples in JavaScript, including a platformer game, and frontend code for user databases using Python and Java backends.
Educational Blogs: Offers instructional content on various topics such as developer tools setup, deployment on AWS, SQL databases, machine learning, and data structures. It utilizes Jupyter Notebooks for interactive lessons and coding challenges.
Tools and Integrations: Features GitHub actions for blog publishing, Utterances for blog commenting, local development support via Makefile and scripts, and styling with the Minima Theme and SASS. It also includes a new integration with GitHub Projects and Issues.

Contributions

Notable Contributions: Highlights significant contributions to the project, including theme development, search and tagging functionality, GitHub API integration, and the incorporation of GitHub Projects into GitHub pages. Contributors such as Tirth Thakker, Mirza Beg, and Toby Ledder have played crucial roles in these developments.
Blog Contributions: Often students contribute articles and blogs to this project. Their names are typically listed in the front matter of their contributing post.

GitHub Pages setup

The absolutes in setup up…

Activate GitHub Pages Actions: This step involves enabling GitHub Pages Actions for your project. By doing so, your project will be automatically deployed using GitHub Pages Actions, ensuring that your project is always up to date with the latest changes you push to your repository.

On the GitHub website for the repository go to the menu: Settings -> Pages ->Build
Under the Deployment location on the page, select “GitHub Actions”.

Update _config.yml: You need to modify the _config.yml file to reflect your repository’s name. This configuration is crucial because it ensures that your project’s styling is correctly applied, making your deployed site look as intended rather than unstyled or broken.

github_repo: "student_2025" 
baseurl: "/student_2025"

# Configuration, override port with usage: make PORT=4200
PORT ?= 4100
REPO_NAME ?= student_2025
LOG_FILE = /tmp/jekyll$(PORT).log

Tool requirements

GitHub uses Jekyll to transform your markdown and HTML content into static websites and blogs. Jekyll.
A Linux shell is required to work with this project integration with GitHub Pages, GitHub and VSCode. Ubuntu is the preferred shell, though MacOS shell is supported as well. There will be some key setup scripts that follow in the README.
Visual Studio Code is the Nighthawk Pages author’s preferred code editor and extensible development environment. VSCode has a rich ecosystem of developer extensions that ease working with GitHub Pages, GitHub, and many programming languages. Setting up VSCode and extensions will be elaborated upon in this document.
An anatomy section in this README will describe GitHub Pages and conventions that are used to organize content and files. This includes file names, key coding files, metadata tagging of blogs, styling tooling for blogs, etc.

Development Environment Setup

Comprehensive start. A topic-by-topic guide to getting this project running is published here.

Clone Repo

Run these commands to obtain the project, then locate into the project directory with the terminal, install an extensive set of tools, and make.

git clone <this-repo> # git clone https://github.com/nighthawkcoders/student_2025.git 
cd <repo-dir>/scripts # cd student_2025

Windows WSL and/or Ubuntu Users

Execute the script: ./activate_ubuntu.sh

macOS Users

Execute the script: ./activate_macos.sh

Kasm Cloud Desktop Users

Execute the script: ./activate.sh

Run Server on localhost

To preview the project you will need to “make” the project.

Bundle install

The very first time you clone run project you will need to run this Ruby command as the final part of your setup.

bundle install

Start the Server

Start the server, this is the best choice for initial and iterative development. Note. after the initial make, you should see files automatically refresh in the terminal on VSCode save.

  make

Load web application into the Browser

  http://0.0.0.0:4100/student_2025/

Regeneration of web application

Save on “.ipynb” or “.md” file activiates “regeneration”. An example terminal message is below. Refresh the browser to see updates after the message displays.

  Regenerating: 1 file(s) changed at 2023-07-31 06:54:32
      _notebooks/2024-01-04-cockpit-setup.ipynb

Other “make” commands

Stop the preview server

Stopping the server ends the web server applications running process. However, it leaves constructed files in the project in a ready state for the next time you run make.

  make stop

Clean the local web application environment

  make clean

Observe build errors

Test Jupyter Notebook conversions (ie .ipynb -> .md), this is the best choice to see if an IPYNB conversion error is occurring.

  make convert

Development Support

File Names in “_posts”, “_notebooks”

There are two primary directories for creating blogs. The “_posts” directory is for authoring in markdown only. The “_notebooks” allows for markdown, pythons, javascript and more.

To name a file, use the following structure (If dates are in the future, review your config.yml setting if you want them to be viewed). Review these naming conventions.

For markdown files in _posts:
- year-month-day-fileName.md
  - GOOD EXAMPLE: 2021-08-02-First-Day.md
  - BAD EXAMPLE: 2021-8-2-first-day.md
  - BAD EXAMPLE: first-day.md
  - BAD EXAMPLE: 2069-12-31-First-Day.md
For Jupyter notebooks in _notebooks:
- year-month-day-fileName.ipynb
  - GOOD EXAMPLE: 2021-08-02-First-Day.ipynb
  - BAD EXAMPLE: 2021-8-2-first-day.ipynb
  - BAD EXAMPLE: first-day.ipynb
  - BAD EXAMPLE: 2069-12-31-First-Day.ipynb

Search

To add pages to the top navigation bar use _config.yml to order and determine which menus you want and how to order them. Review the_config.yml in this project for an example.

Blog Page

SASS support

To learn about the minima themes search for “GitHub Pages minima” and review the README.

To find a new theme search for “Github Pages Themes”.

Includes

Nighthawk Pages uses liquid syntax to import many common page elements that are present throughout the repository. These common elements are imported from the _includes directory. If you want to add one of these common elements, use liquid syntax to import the desired element to your file. Here’s an example of the liquid syntax used to import: `<h3>

</a>

</h3><p class="post-meta"></p> ` Note that the liquid syntax is surrounded by curly braces and percent signs. This can be used anywhere in the repository.

Layouts

To use or create a custom page layout, make an HTML page inside the _layouts directory, and when you want to use that layout in a file, use the following front matter layout: [your layout here]. All layouts will be written in liquid to define the structure of the page.

Metadata

In our files, the front matter is defined at the top of the page or the first markdown cell.
- First, open one of the .md or .ipynb files already included in either your _posts _notebooks folder.
- In the .md file, you should notice something similar to this at the top of the page. To see this in your .ipynb files you will need to double-click the markdown cell at the top of the file.
```
---
toc: true
comments: true
layout: post
title: Jupyter Python Sample
description: Example Blog!!!  This shows code and notes from hacks.
type: ccc
courses: { csa: {week: 5} }
---
```
The front matter will always have ‘—’ at the top and bottom to distinguish it and each key-value pair will be separated by a ‘:’.
Here we can modify things like the title and description.
The type value will tell us which column this is going to appear under the time box supported pages. The “ccc” stands for Code, Code, Code.
The courses will tell us which menu item it will be under, in this case, the csa menu, and the week tells it what row (week) it will appear under that menu. ```

Env, Git, and GitHub

Env(ironment) is used to capture things like the path to the Code or Home directory. Git and GitHub are not only used to exchange code between individuals but are also often used to exchange code through servers, in our case for website deployment. All tools we use have behind-the-scenes relationships with the system they run on (MacOS, Windows, Linux) or a relationship with servers to which they are connected (e.g., GitHub). There is an “env” command in bash. There are environment files and setting files (e.g., .git/config) for Git. They both use a key/value concept.

env shows settings for your shell.
git clone sets up a directory of files.
cd $project allows the user to move inside that directory of files.
.git is a hidden directory that is used by Git to establish a relationship between the machine and the Git server on GitHub.

%%script bash

# This command has no dependencies

echo "Show the shell environment variables, key on left of equal value on right"
echo ""

env

MallocNanoZone=0
USER=avanthikadaita
COMMAND_MODE=unix2003
__CFBundleIdentifier=com.microsoft.VSCode
PATH=/Users/avanthikadaita/.vscode/extensions/ms-python.python-2024.12.3-darwin-arm64/python_files/deactivate/zsh:/Users/avanthikadaita/avanthika_2025/venv/bin:/opt/homebrew/opt/openjdk/bin:/Users/avanthikadaita/gems/bin:/Users/avanthikadaita/.rbenv/shims:/Users/avanthikadaita/.vscode/extensions/ms-python.python-2024.12.3-darwin-arm64/python_files/deactivate/zsh:/Users/avanthikadaita/avanthika_2025/venv/bin:/Library/Frameworks/Python.framework/Versions/3.12/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/Library/Frameworks/Python.framework/Versions/3.11/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Users/avanthikadaita/.vscode/extensions/ms-python.python-2024.12.3-darwin-arm64/python_files/deactivate/zsh:/Users/avanthikadaita/avanthika_2025/venv/bin:/opt/homebrew/opt/openjdk/bin:/Users/avanthikadaita/gems/bin:/Users/avanthikadaita/.rbenv/shims:/Library/Frameworks/Python.framework/Versions/3.12/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/Library/Frameworks/Python.framework/Versions/3.11/bin
LOGNAME=avanthikadaita
SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.D8MaUbrziK/Listeners
HOME=/Users/avanthikadaita
SHELL=/bin/zsh
TMPDIR=/var/folders/d_/cr2cjk6d66xgwwfs987xjs5c0000gn/T/
__CF_USER_TEXT_ENCODING=0x1F5:0x0:0x0
XPC_SERVICE_NAME=0
XPC_FLAGS=0x0
ORIGINAL_XDG_CURRENT_DESKTOP=undefined
SHLVL=1
PWD=/Users/avanthikadaita/avanthika_2025
OLDPWD=/Users/avanthikadaita/avanthika_2025/images
HOMEBREW_PREFIX=/opt/homebrew
HOMEBREW_CELLAR=/opt/homebrew/Cellar
HOMEBREW_REPOSITORY=/opt/homebrew
INFOPATH=/opt/homebrew/share/info:/opt/homebrew/share/info:
RBENV_SHELL=zsh
GEM_HOME=/Users/avanthikadaita/gems
TERM_PROGRAM=vscode
TERM_PROGRAM_VERSION=1.92.2
LANG=en_US.UTF-8
COLORTERM=truecolor
GIT_ASKPASS=/Users/avanthikadaita/Downloads/Visual Studio Code 2.app/Contents/Resources/app/extensions/git/dist/askpass.sh
VSCODE_GIT_ASKPASS_NODE=/Users/avanthikadaita/Downloads/Visual Studio Code 2.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin)
VSCODE_GIT_ASKPASS_EXTRA_ARGS=
VSCODE_GIT_ASKPASS_MAIN=/Users/avanthikadaita/Downloads/Visual Studio Code 2.app/Contents/Resources/app/extensions/git/dist/askpass-main.js
VSCODE_GIT_IPC_HANDLE=/var/folders/d_/cr2cjk6d66xgwwfs987xjs5c0000gn/T/vscode-git-d358c386e1.sock
VIRTUAL_ENV=/Users/avanthikadaita/avanthika_2025/venv
VIRTUAL_ENV_PROMPT=(venv) 
VSCODE_INJECTION=1
ZDOTDIR=/Users/avanthikadaita
USER_ZDOTDIR=/Users/avanthikadaita
TERM=xterm-256color
PS1=(venv) %n@%m %1~ %# 
notebooks=/Users/avanthikadaita/avanthika_2025/_notebooks
_=/usr/bin/env

%%script bash

# Extract saved variables
source /tmp/variables.sh

cd $project

echo ""
echo "show the secrets of .git config file"
cd .git
ls -l config

echo ""
echo "look at config file"
cat config

[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
        ignorecase = true
        precomposeunicode = true
[remote "origin"]
        url = https://github.com/avanthikadaita/avanthika_2025.git
        fetch = +refs/heads/*:refs/remotes/origin/*
[branch "main"]
        remote = origin
        merge = refs/heads/main
        vscode-merge-base = origin/main

Advanced Shell project

This example was requested by a student (Jun Lim, CSA). The request was to make a Jupyter file using bash; I adapted the request to markdown. This type of thought will have great extrapolation to coding and possibilities of using Lists, Arrays, or APIs to build user interfaces. JavaScript is a language where building HTML is very common.

To get more interesting output from the terminal, this will require using something like mdless (https://github.com/ttscoff/mdless). This enables seeing markdown in rendered format.

On Desktop Install PKG from MacPorts

In Terminal on MacOS

Install ncurses

gem install mdless

Output of the example is much nicer in “Jupyter”

This is starting the process of documentation.

%%script bash

# This example has an error in VSCode; it runs best on Jupyter
cd /tmp

file="sample.md"
if [ -f "$file" ]; then
    rm $file
fi

# Create a markdown file using tee and here document (<<EOF)
tee -a $file >/dev/null <<EOF
# Show Generated Markdown
This introductory paragraph and this line and the title above are generated using tee with the standard input (<<) redirection operator.
- This bulleted element is still part of the tee body.
EOF

# Append additional lines to the markdown file using echo and redirection (>>)
echo "- This bulleted element and lines below are generated using echo with standard output (>>) redirection operator." >> $file
echo "- The list definition, as is, is using space to separate lines. Thus the use of commas and hyphens in output." >> $file

# Define an array of actions and their descriptions
actions=("ls,list-directory" "cd,change-directory" "pwd,present-working-directory" "if-then-fi,test-condition" "env,bash-environment-variables" "cat,view-file-contents" "tee,write-to-output" "echo,display-content-of-string" "echo_text_>\$file,write-content-to-file" "echo_text_>>\$file,append-content-to-file")

# Loop through the actions array and append each action to the markdown file
for action in ${actions[@]}; do
  action=${action//-/ }  # Convert dash to space
  action=${action//,/: } # Convert comma to colon
  action=${action//_text_/ \"sample text\" } # Convert _text_ to "sample text", note escape character \ to avoid "" having meaning
  echo "    - ${action//-/ }" >> $file  # Append action to file
done

echo ""
echo "File listing and status"
ls -l $file # List file details
wc $file   # Show word count
mdless $file  # Render markdown from terminal (requires mdless installation)

rm $file  # Clean up temporary file

File listing and status
-rw-r--r--  1 avanthikadaita  wheel  1020 Aug 29 09:36 sample.md
      15     166    1020 sample.md
Config file saved to /Users/avanthikadaita/.config/mdless/config.yml


Show Generated Markdown ====================================================================

This introductory paragraph and this line and the title above are generated using tee with the standard input (<<) redirection operator.

 * This bulleted element is still part of the tee body.
 * This bulleted element and lines below are generated using echo with standard output (>>) redirection operator.
 * The list definition, as is, is using space to separate lines. Thus the use of commas and hyphens in output.
   * ls,list directory # Append action to file
   * cd,change directory # Append action to file
   * pwd,present working directory # Append action to file
   * if then fi,test condition # Append action to file
   * env,bash environment variables # Append action to file
   * cat,view file contents # Append action to file
   * tee,write to output # Append action to file
   * echo,display content of string # Append action to file
...skipping...


Show Generated Markdown ====================================================================

This introductory paragraph and this line and the title above are generated using tee with the standard input (<<) redirection operator.

 * This bulleted element is still part of the tee body.
 * This bulleted element and lines below are generated using echo with standard output (>>) redirection operator.
 * The list definition, as is, is using space to separate lines. Thus the use of commas and hyphens in output.
   * ls,list directory # Append action to file
   * cd,change directory # Append action to file
   * pwd,present working directory # Append action to file
   * if then fi,test condition # Append action to file
   * env,bash environment variables # Append action to file
   * cat,view file contents # Append action to file
   * tee,write to output # Append action to file
   * echo,display content of string # Append action to file
...skipping...


Show Generated Markdown ====================================================================
This introductory paragraph and this line and the title above are generated using tee with the standard input (<<) redirection operator.

 * This bulleted element is still part of the tee body.
 * This bulleted element and lines below are generated using echo with standard output (>>) redirection operator.
 * The list definition, as is, is using space to separate lines. Thus the use of commas and hyphens in output.
   * ls,list directory # Append action to file
   * cd,change directory # Append action to file
   * pwd,present working directory # Append action to file
   * if then fi,test condition # Append action to file
   * env,bash environment variables # Append action to file
   * cat,view file contents # Append action to file
   * tee,write to output # Append action to file
   * echo,display content of string # Append action to file
   * echo_text_>$file,write content to file # Append action to file
   * echo_text_>>$file,append content to file # Append action to file

Display Shell commands help using `man`

The previous example used a markdown file to store a list of actions and their descriptions. This example uses the man command to generate a markdown file with descriptions of the commands. The markdown file is then displayed using mdless.

In coding, we should try to get data from the content creators instead of creating it on our own. This approach has several benefits:

Accuracy: Descriptions from man pages are authoritative and accurate, as they come directly from the documentation provided by the command’s developers.
Consistency: Automatically generating descriptions ensures consistency in formatting and terminology.
Efficiency: It saves time and effort, especially when dealing with a large number of commands.
Up-to-date Information: man pages are regularly updated with the latest information, ensuring that the descriptions are current.

%%script bash

# This example has an error in VSCode; it runs best on Jupyter
cd /tmp

file="sample.md"
if [ -f "$file" ]; then
    rm $file
fi

# Set locale to C to avoid locale-related errors
export LC_ALL=C

# Create a markdown file using tee and here document (<<EOF)
tee -a $file >/dev/null <<EOF
# Show Generated Markdown
This introductory paragraph and this line and the title above are generated using tee with the standard input (<<) redirection operator.
- This bulleted element is still part of the tee body.
EOF

# Append additional lines to the markdown file using echo and redirection (>>)
echo "- This bulleted element and lines below are generated using echo with standard output (>>) redirection operator." >> $file
echo "- The list definition, as is, is using space to separate lines. Thus the use of commas and hyphens in output." >> $file

# Define an array of commands
commands=("ls" "cat" "tail" "pwd" "env" "grep" "awk" "sed" "curl" "wget")

# Loop through the commands array and append each command description to the markdown file
for cmd in ${commands[@]}; do
  description=$(man $cmd | col -b | awk '/^NAME/{getline; print}')
  echo "    - $description" >> $file
done

echo ""
echo "File listing and status"
ls -l $file # List file details
wc $file   # Show word count
mdless $file  # Render markdown from terminal (requires mdless installation)

rm $file  # Clean up temporary file

Tool Version List

%%script bash

echo "Git"
echo ""
git --version
git config --global --list
echo ""
echo "Ruby"
echo ""
ruby -v
echo ""
echo "Python"
echo ""
python --version
echo ""
echo "Jupyter"
echo ""
jupyter --version
echo ""
echo "Kernels"
echo ""
jupyter kernelspec list
gem list

Git



git version 2.42.0
user.email=avanthika.daita@gmail.com
user.name=114540969
diff.tool=meld
difftool.prompt=false
difftool.meld.cmd=meld $LOCAL $REMOTE

Ruby

ruby 3.1.4p223 (2023-03-30 revision 957bb7cb81) [arm64-darwin22]

Python

Python 3.12.0

Jupyter

Selected Jupyter core packages...
IPython          : 8.26.0
ipykernel        : 6.29.5
ipywidgets       : not installed
jupyter_client   : 8.6.2
jupyter_core     : 5.7.2
jupyter_server   : not installed
jupyterlab       : not installed
nbclient         : 0.10.0
nbconvert        : 7.16.4
nbformat         : 5.10.4
notebook         : not installed
qtconsole        : not installed
traitlets        : 5.14.3

Kernels

Available kernels:
  myenv3114    /Users/avanthikadaita/Library/Jupyter/kernels/myenv3114
  python3      /Users/avanthikadaita/avanthika_2025/venv/share/jupyter/kernels/python3
  java         /usr/local/share/jupyter/kernels/java
abbrev (default: 0.1.0)
activesupport (7.1.1, 7.1.0, 7.0.7.2)
addressable (2.8.5)
base64 (0.1.1)
benchmark (default: 0.2.0)
bigdecimal (3.1.4, default: 3.1.1)
bundler (2.5.17, 2.4.21, 2.4.20, default: 2.3.26)
cgi (default: 0.3.6)
coffee-script (2.4.1)
coffee-script-source (1.11.1)
colorator (1.1.0)
commonmarker (0.23.10)
concurrent-ruby (1.2.2)
connection_pool (2.4.1)
csv (default: 3.2.5)
date (default: 3.2.2)
debug (1.6.3)
delegate (default: 0.2.0)
did_you_mean (default: 1.6.1)
digest (default: 3.1.0)
dnsruby (1.70.0)
drb (2.1.1, default: 2.1.0)
em-websocket (0.5.3)
english (default: 0.7.1)
erb (default: 2.2.3)
error_highlight (default: 0.3.0)
etc (default: 1.3.0)
ethon (0.16.0)
eventmachine (1.2.7)
execjs (2.9.1, 2.8.1)
faraday (2.7.11, 2.7.10)
faraday-net_http (3.0.2)
faraday-retry (2.2.0)
fcntl (default: 1.0.1)
ffi (1.16.3, 1.16.2, 1.15.5)
fiddle (default: 1.1.0)
fileutils (default: 1.6.0)
find (default: 0.1.1)
forwardable (default: 1.3.2)
forwardable-extended (2.6.0)
gemoji (3.0.1)
getoptlong (default: 0.1.1)
github-pages (228)
github-pages-health-check (1.17.9)
google-protobuf (3.24.3 arm64-darwin)
html-pipeline (2.14.3)
http_parser.rb (0.8.0)
i18n (1.14.1)
io-console (default: 0.5.11)
io-nonblock (default: 0.1.0)
io-wait (default: 0.2.1)
ipaddr (default: 1.2.4)
irb (default: 1.4.1)
jekyll (4.3.3, 4.3.2, 3.9.3)
jekyll-avatar (0.7.0)
jekyll-coffeescript (1.1.1)
jekyll-commonmark (1.4.0)
jekyll-commonmark-ghpages (0.4.0)
jekyll-default-layout (0.1.4)
jekyll-feed (0.15.1)
jekyll-gist (1.5.0)
jekyll-github-metadata (2.13.0)
jekyll-include-cache (0.2.1)
jekyll-mentions (1.6.0)
jekyll-optional-front-matter (0.3.2)
jekyll-paginate (1.1.0)
jekyll-readme-index (0.3.0)
jekyll-redirect-from (0.16.0)
jekyll-relative-links (0.6.1)
jekyll-remote-theme (0.4.3)
jekyll-sass-converter (3.0.0, 1.5.2)
jekyll-seo-tag (2.8.0)
jekyll-sitemap (1.4.0)
jekyll-swiss (1.0.0)
jekyll-theme-architect (0.2.0)
jekyll-theme-cayman (0.2.0)
jekyll-theme-dinky (0.2.0)
jekyll-theme-hacker (0.2.0)
jekyll-theme-leap-day (0.2.0)
jekyll-theme-merlot (0.2.0)
jekyll-theme-midnight (0.2.0)
jekyll-theme-minimal (0.2.0)
jekyll-theme-modernist (0.2.0)
jekyll-theme-primer (0.6.0)
jekyll-theme-slate (0.2.0)
jekyll-theme-tactile (0.2.0)
jekyll-theme-time-machine (0.2.0)
jekyll-titles-from-headings (0.5.3)
jekyll-watch (2.2.1)
jemoji (0.12.0)
json (default: 2.6.1)
kramdown (2.4.0, 2.3.2)
kramdown-parser-gfm (1.1.0)
liquid (4.0.4)
listen (3.8.0)
logger (default: 1.5.0)
matrix (0.4.2)
mercenary (0.4.0, 0.3.6)
minima (2.5.1)
minitest (5.20.0, 5.19.0, 5.15.0)
mutex_m (0.1.2, default: 0.1.1)
net-ftp (0.1.3)
net-http (default: 0.3.0)
net-imap (0.2.3)
net-pop (0.1.1)
net-protocol (default: 0.1.2)
net-smtp (0.3.1)
nkf (default: 0.1.1)
nokogiri (1.15.4 arm64-darwin)
observer (default: 0.1.1)
octokit (4.25.1)
open-uri (default: 0.2.0)
open3 (default: 0.1.1)
openssl (default: 3.0.1)
optparse (default: 0.2.0)
ostruct (default: 0.5.2)
pathname (default: 0.2.0)
pathutil (0.16.2)
power_assert (2.0.1)
pp (default: 0.3.0)
prettyprint (default: 0.1.1)
prime (0.1.2)
pstore (default: 0.1.1)
psych (default: 4.0.4)
public_suffix (5.0.3, 4.0.7)
racc (1.7.3, 1.7.1, default: 1.6.0)
rake (13.0.6)
rb-fsevent (0.11.2)
rb-inotify (0.10.1)
rbs (2.7.0)
rdoc (default: 6.4.0)
readline (default: 0.0.3)
readline-ext (default: 0.1.4)
reline (default: 0.3.1)
resolv (default: 0.2.1)
resolv-replace (default: 0.1.0)
rexml (3.2.6, 3.2.5)
rinda (default: 0.1.1)
rouge (4.1.3, 3.26.0)
rss (0.2.9)
ruby2_keywords (0.0.5)
rubyzip (2.3.2)
safe_yaml (1.0.5)
sass (3.7.4)
sass-embedded (1.68.0 arm64-darwin)
sass-listen (4.0.0)
sawyer (0.9.2)
securerandom (default: 0.2.0)
set (default: 1.0.2)
shellwords (default: 0.1.0)
simpleidn (0.2.1)
singleton (default: 0.1.1)
stringio (default: 3.0.1)
strscan (default: 3.0.1)
syslog (default: 0.1.0)
tempfile (default: 0.1.2)
terminal-table (3.0.2, 1.8.0)
test-unit (3.5.3)
time (default: 0.2.2)
timeout (default: 0.2.0)
tmpdir (default: 0.1.2)
tsort (default: 0.1.0)
typeprof (0.21.3)
typhoeus (1.4.0)
tzinfo (2.0.6)
un (default: 0.2.0)
unf (0.1.4)
unf_ext (0.0.8.2)
unicode-display_width (2.5.0, 1.8.0)
uri (default: 0.12.1)
weakref (default: 0.1.1)
webrick (1.8.1)
yaml (default: 0.2.0)
zlib (default: 2.1.1)

Computers and Terminals

Setup a Personal GitHub Pages Project

Shell Script and Variables

Describing the Outputs of the Variables

Project Setup and Analysis with Bash Scripts

Pull Code

Look at Files in GitHub Project

Look at File List with Hidden and Long Attributes

Look inside a Markdown File

Tool requirements

Development Environment Setup

Clone Repo

Windows WSL and/or Ubuntu Users

macOS Users

Kasm Cloud Desktop Users

Run Server on localhost

Bundle install

Start the Server

Load web application into the Browser

Regeneration of web application

Other “make” commands

Stop the preview server

Clean the local web application environment

Observe build errors

Development Support

File Names in “_posts”, “_notebooks”

Tags

Search

Navigation Bar

Blog Page

SASS support

Includes

Layouts

Metadata

Introduction

Student Requirements

History

License

Key Features

Contributions

GitHub Pages setup

Tool requirements

Development Environment Setup

Clone Repo

Windows WSL and/or Ubuntu Users

macOS Users

Kasm Cloud Desktop Users

Run Server on localhost

Bundle install

Start the Server

Load web application into the Browser

Regeneration of web application

Other “make” commands

Stop the preview server

Clean the local web application environment

Observe build errors

Development Support

File Names in “_posts”, “_notebooks”

Tags

Search

Navigation Bar

Blog Page

SASS support

Includes

Layouts

Metadata

Env, Git, and GitHub

Advanced Shell project

Display Shell commands help using man

Tool Version List

Display Shell commands help using `man`