Merge branch 'main' into branchsam

Author: fragandi

README.md

@@ -5,6 +5,28 @@ This repository is designed to help you quickly get started with [PreTeXt](https
 ---
 
 ## 🚀 Quick Start Guide
+
+## 🚀 How to Create Your Own PreTeXt-Codespace Repository
+
+There are two easy ways to set up your own PreTeXt-enabled Codespace:
+
+### ✅ Option 1: Fork This Repository
+
+1. Visit [fragandi/CURITutorialDevelopment2025](https://github.com/fragandi/CURITutorialDevelopment2025).
+
+2. Click **"Fork"** (top-right) to copy it to your GitHub account.
+3. Open your new forked repository and click **"Code" → "Create codespace on main"**.
+
+### 🛠️ Option 2: Set Up a Fresh Repository Manually
+
+1. Create a new GitHub repository in your account.
+2. Copy the entirity of `.devcontainer/`, `.github/`, `.gitignore`, `requirements.txt` folder from [fragandi/CURITutorialDevelopment2025](https://github.com/fragandi/CURITutorialDevelopment2025).
+3. (Recommended) Also copy the following for a smoother experience:
+   - The `README_images/` folder and `README.md` file (for guidance and troubleshooting)
+4. Push your changes and create a Codespace from the repository.
+
+This option gives you more flexibility to customize your setup while keeping the essential PreTeXt environment.
+
 Once the Codespace has finished creating, **check that PreTeXt is installed** by running:
 
 ```bash
@@ -45,17 +67,27 @@ If you see an error like **command not found**, follow these steps:
 
 ## 🌐 GitHub Pages Configuration
 
-Make sure to configure GitHub Pages to use **GitHub Actions** as the build and deployment source.
+Make sure to configure GitHub Pages to use **GitHub Actions** as the build and deployment source:
+
+1. Go to your repository’s **Settings** → **Pages**.
+2. Under **Build and deployment**, set the source to **GitHub Actions**.
+
+<img src="README_images/image-pages_source.png" alt="GitHub Pages Source" style="border: 2px solid green;">
+
+---
+
+## 🛠 GitHub Environment Configuration
 
-1. Go to your repository's **Settings** → **Pages**.
-2. Under **Build and deployment**, set the source to **GitHub Actions** as shown below:
+Go to your repository **Settings** → **Environments** → click on `github-pages`, and make sure it looks similar to the following:
 
-![GitHub Pages Source](README_images/image-pages_source.png)
+<img src="README_images/image-environment-pages.png" alt="GitHub Pages Environment Setup" style="border: 2px solid green;">
+<br>
+<img src="README_images/image-environment.png" alt="Environment Overview" style="border: 2px solid green;">
 
 ---
 
 ## ⏱ Deployment Time
 
-Deployment takes about **4 minutes**. After triggering the deployment, wait a few minutes, then check your site via the GitHub Pages link.
+Deployment usually takes about **4 minutes**. After triggering the deployment, wait a few minutes and then visit your GitHub Pages URL.
 
-![GitHub Actions Deployment](README_images/image-actions-deployment.png)
+<img src="README_images/image-actions-deployment.png" alt="GitHub Actions Deployment" style="border: 2px solid green;">

README_images/image-actions-deployment.png

@@ -5,39 +5,9 @@
         <p>
 This chapter is co-authored by Francesca Gandini, Sumner Strom, Al Ashir Intisar
         </p>
-    </introduction>
-    <!-- <section xml:id="sec-template">
-        <title>Template </title>
-        <p>
-            This is the introduction to the template.
-        </p>
-        <subsection xml:id="subsec-template">
-            <title>Template Subsection</title>
-            <p>
-                This is the template subsection.
-            </p>
-            
-        </subsection>
-    </section> -->
-    
-       <!-- <section xml:id="sec-notes">
-            <title>Notes</title>
-            
-            <subsection xml:id="subsec-notes">
-            <title>Notes Subsection</title>
-            <p>
-                To build in pretext use the template subsection and pretext environment features.
-                Make sure that you are building and compiling from main using preview code chat.
-                Additionally, when running if the compilation fails run the command "pretext build web" in terminal.
-                Make sure that all of the xml have unique ids so that you dont run into compilation errors. 
-                Follow the other chapters to find out how things are used.
-                Make sure that the sections are properly linked within the main.ptx. Additionally, use the subsections and sections for organization.
-                If something doesnt display there is a paragraph line missing.
-
-            </p>
-            
-        </subsection>
-    </section>-->
+ 
+   
+    
     <section xml:id="sec-m2-codespace">
       <title>Creating a M2 Codespace</title>
 
@@ -514,4 +484,5 @@ This chapter is co-authored by Francesca Gandini, Sumner Strom, Al Ashir Intisar
         </section>
 
     </section>
+
 </chapter>