Revise GitHub Pages overview in README.md

Updated the README.md to improve clarity on GitHub Pages features and usage.

Author: brown9804

demos/1_GitHubPagesOverview/README.md

@@ -10,25 +10,13 @@ Last updated: 2026-03-26
 
 > **GitHub Pages** is a feature provided by GitHub that allows you to `host static websites directly from a GitHub repository`. It's a great way to showcase your projects, create personal websites, or host documentation for your repositories. `That means it serves whatever files you put in your repository, without running backend code.`
 
-> [!TIP]
-> What is GitHub Pages? <br/>
-> GitHub Pages is a `free service that turns your GitHub repositories into websites`. You can host HTML, CSS, and JavaScript files, and it’s perfect for static websites that `don’t require server-side processing`. GitHub Pages supports custom domains, making it easy to create a professional-looking website.
-
-- Markdown (.md) → converted to HTML automatically if you use Jekyll.
-- HTML, CSS, JavaScript → served directly as static files.
-- Jekyll templates (Liquid) → processed by GitHub Pages if you keep Jekyll enabled.
-- Static assets → images, fonts, PDFs, JSON, etc.
-
-> [!NOTE]
-> - If you need dynamic behavior, you can use JavaScript frameworks (React, Vue, Angular) that compile down to static files and deploy them to GitHub Pages.
-> - For backend logic, you’d need to connect to external APIs or use another service (like Firebase, Supabase, or a traditional server).
-
 <details>
 <summary><b>List of References</b> (Click to expand)</summary>
 
 - [Websites for you and your projects](https://pages.github.com/)
 - [Essentials of automated application deployment with GitHub Actions and GitHub Pages](https://resources.github.com/learn/pathways/automation/essentials/automated-application-deployment-with-github-actions-and-pages/)
-
+- [Microsoft Cloud Sandbox - Unofficial](https://microsoftcloudessentials-learninghub.github.io/org-catalog/) One example was a catalog that aggregated multiple repositories from my GitHub organization. The idea behind it was to create a user‑friendly page that listed all repositories hosted within the organization, while also allowing them to be filtered based on GitHub metadata by [Org Catalog (GitHub Pages)](https://github.com/MicrosoftCloudEssentials-LearningHub/org-catalog)
+- [TechWorkshop L300: Win the database acceleration](https://microsoft.github.io/TechExcel-Win-the-Database-Platform/) Example of Workshops documented using GitHub Pages
 
 </details>
 
@@ -43,6 +31,19 @@ Last updated: 2026-03-26
 
 </details>
 
+> [!TIP]
+> What is GitHub Pages? <br/>
+> GitHub Pages is a `free service that turns your GitHub repositories into websites`. You can host HTML, CSS, and JavaScript files, and it’s perfect for static websites that `don’t require server-side processing`. GitHub Pages supports custom domains, making it easy to create a professional-looking website.
+
+- Markdown (.md) → converted to HTML automatically if you use Jekyll.
+- HTML, CSS, JavaScript → served directly as static files.
+- Jekyll templates (Liquid) → processed by GitHub Pages if you keep Jekyll enabled.
+- Static assets → images, fonts, PDFs, JSON, etc.
+
+> [!NOTE]
+> - If you need dynamic behavior, you can use JavaScript frameworks (React, Vue, Angular) that compile down to static files and deploy them to GitHub Pages.
+> - For backend logic, you’d need to connect to external APIs or use another service (like Firebase, Supabase, or a traditional server).
+
 ## How is GitHub Pages Used?
 - **Personal Websites**: Showcase your portfolio, resume, or blog.
 - **Project Documentation**: Host documentation for your open-source projects.