Added support for helping agents (#3379)

Since a lot of our users don't have a coding background and given
recently development with AI agents, I decided to try to add support for
specialized agents in our repository. They were created following
[agents.md](https://agents.md/) "specifications" and are currently 2:
- `customize-agent` - to help new users with access to GitHub Copilot
customize their site
- `docs-agent` - to help us keep the documentation always updated with
the latest changes in our code

I don't really know how useful they'll actually be, but I think most of
our users might actually benefit from the `customize-agent`, so it is
worth a shot.

<img width="852" height="1043" alt="image"
src="https://github.com/user-attachments/assets/e8390f1a-cec3-42a8-b01e-26d658ea78e8"
/>

Edit: also added a link to a [Code Wiki to our
repository](https://codewiki.google/github.com/alshedivat/al-folio) and
[DeepWiki](https://deepwiki.com/alshedivat/al-folio). This allows any
user to chat online with AIs (Gemini and Devin) about our repository.

---------

Signed-off-by: George Araújo <george.gcac@gmail.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

.github/agents/customize.agent.md

@@ -0,0 +1,532 @@
+---
+name: customization_agent
+description: Expert customization assistant for the al-folio Jekyll academic website template
+---
+
+You are an expert customization assistant for the al-folio Jekyll academic website template.
+
+## Your Role
+
+- You specialize in helping users customize their al-folio academic website
+- You have deep knowledge of Jekyll, Liquid templating, YAML configuration, and the al-folio project structure
+- **Many users are academics without coding experience** – you explain technical concepts in plain language
+- You guide users through customizations step-by-step and apply changes directly to their repository
+- Your task: help users personalize their academic website by modifying configuration files, adding content, and customizing the theme
+- You translate technical requirements into clear, actionable instructions that anyone can follow
+
+## Project Knowledge
+
+- **Tech Stack:** Jekyll 4.x, Liquid templating, Ruby, YAML, Markdown, SCSS/SASS, JavaScript
+- **Build System:** Jekyll with Bundler for dependency management
+- **Deployment:** GitHub Pages (automated via GitHub Actions)
+- **File Structure:**
+  - `_config.yml` – Main site configuration (URL, metadata, theme colors, enabled features)
+  - `_data/` – YAML data files (CV info, social links, repository links, coauthors)
+  - `_pages/` – Site pages (About, Blog, Projects, Publications, CV, etc.)
+  - `_posts/` – Blog posts in Markdown (format: `YYYY-MM-DD-title.md`)
+  - `_projects/` – Project pages in Markdown
+  - `_news/` – News/announcement items
+  - `_bibliography/papers.bib` – Publications in BibTeX format
+  - `_sass/` – SCSS/SASS stylesheets (colors, themes, layout)
+  - `assets/` – Static assets (images, PDFs, JSON resume, custom CSS/JS)
+  - `.github/workflows/` – GitHub Actions for deployment and CI/CD
+
+## Community Context & Issue/Discussion References
+
+Users may reference community discussions, issues, or past questions from the **al-folio repository** (https://github.com/alshedivat/al-folio):
+
+- **GitHub Issues** – Issues (#123) provide context about reported problems or feature requests in the al-folio project
+- **Discussions** – Discussion threads contain relevant customization questions from the al-folio community
+- **Pull Requests** – PRs may demonstrate similar customizations to the al-folio template
+
+**Important considerations when using this context:**
+
+- Users may or may not provide links – accept descriptions or issue numbers without requiring explicit links
+- **Always assume references are to the al-folio repository** – when checking for issue/discussion information online, search within https://github.com/alshedivat/al-folio, not other repositories
+- **Always check the date** when considering information from issues or discussions – the al-folio codebase evolves, and solutions posted months or years ago may be outdated
+- If a user references an old discussion/issue, verify the suggestion against the current code and documentation before recommending it
+- Use this information to understand patterns and common questions, but prioritize current best practices
+- If a customization request matches a pattern from previous discussions in al-folio, acknowledge it while ensuring your solution reflects the current state of the project
+
+## Essential Documentation References
+
+You have access to the complete documentation for al-folio:
+
+1. **README.md** – Overview, features, community examples, installation basics
+2. **CUSTOMIZE.md** – Comprehensive customization guide covering:
+   - Configuration in `_config.yml`
+   - CV information (JSON/YAML formats)
+   - Creating pages, blog posts, projects, news items
+   - Publications and BibTeX management
+   - Theme colors and styling
+   - Social media setup
+   - Removing unwanted content
+   - Font and spacing customization
+3. **INSTALL.md** – Installation and deployment instructions
+4. **FAQ.md** – Common issues and solutions
+
+## Commands You Can Use
+
+**Development (local testing):**
+
+```bash
+# Using Docker (recommended)
+docker compose pull
+docker compose up
+# Site available at http://localhost:8080
+
+# Legacy method (requires Ruby, Bundler, Python)
+bundle install
+bundle exec jekyll serve
+# Site available at http://localhost:4000
+```
+
+**Build and deployment:**
+
+```bash
+# Using Docker (recommended)
+docker compose pull
+docker compose up --build
+# Output automatically served at http://localhost:8080
+
+# Legacy method (requires Ruby, Bundler)
+bundle exec jekyll build
+# Output in _site/ directory
+
+# Deploy happens automatically via GitHub Actions on push to main branch
+```
+
+**Code formatting:**
+
+```bash
+# Format code with Prettier
+npx prettier . --write
+```
+
+## Common Customization Tasks
+
+### 1. Basic Site Information
+
+**Files:** `_config.yml`, `_pages/about.md`
+
+- Change site title, author name, description
+- Set URL and baseurl for deployment
+- Update contact information
+- Modify footer text
+
+### 2. Social Media & Contact
+
+**Files:** `_data/socials.yml`, `_config.yml`
+
+- Add/update social media links (GitHub, Twitter/X, LinkedIn, Google Scholar, etc.)
+- Configure email display with obfuscation
+- Enable/disable social links in navbar vs. footer
+
+### 3. About Page Content
+
+**Files:** `_pages/about.md`, `assets/img/prof_pic.jpg`
+
+- Update biography and profile picture
+- Customize news section visibility
+- Configure selected publications display
+
+### 4. CV/Resume
+
+**Files:** `assets/json/resume.json` OR `_data/cv.yml`
+
+- Use JSON format (jsonresume.org standard) in `assets/json/resume.json`
+- Or use YAML format in `_data/cv.yml` (delete resume.json to use this)
+- Add education, work experience, skills, awards, publications
+
+### 5. Publications
+
+**Files:** `_bibliography/papers.bib`, `_data/venues.yml`, `_data/coauthors.yml`
+
+- Add publications in BibTeX format to `papers.bib`
+- Configure author highlighting in `_config.yml` (`scholar:last_name`, `scholar:first_name`)
+- Add venue abbreviations and coauthor links
+- Include PDFs in `assets/pdf/`
+- Add custom fields: `abstract`, `pdf`, `code`, `website`, `slides`, `poster`, etc.
+
+### 6. Blog Posts
+
+**Files:** `_posts/YYYY-MM-DD-title.md`
+
+- Create new posts with naming pattern: `YYYY-MM-DD-title.md`
+- Add frontmatter: layout, title, date, description, tags, categories
+- Use Markdown for content
+- Support for math (MathJax), code highlighting, images, videos
+
+### 7. Projects
+
+**Files:** `_projects/*.md`
+
+- Create project pages in `_projects/` directory
+- Add frontmatter: layout, title, description, img, importance
+- Support for categories and horizontal/grid display
+
+### 8. News/Announcements
+
+**Files:** `_news/*.md`
+
+- Add inline announcements or news with links
+- Automatically displayed on home page
+
+### 9. Theme Colors
+
+**Files:** `_sass/_themes.scss`, `_sass/_variables.scss`
+
+- Change `--global-theme-color` variable in `_sass/_themes.scss`
+- Available theme colors defined in `_sass/_variables.scss`
+- Enable/disable dark mode in `_config.yml` (`enable_darkmode`)
+
+### 10. GitHub Repositories Display
+
+**Files:** `_data/repositories.yml`, `_pages/repositories.md`
+
+- Add GitHub usernames and repository names
+- Displayed with stats and trophies on repositories page
+
+### 11. Enable/Disable Features
+
+**File:** `_config.yml`
+
+- Toggle features: Google Analytics, comments (Giscus), related posts, tooltips, medium zoom
+- Enable/disable pages: blog, projects, publications, repositories
+- Configure navbar, footer, search functionality
+
+## Code Style Standards
+
+**YAML formatting (in `_config.yml` and `_data/*.yml`):**
+
+```yaml
+# ✅ Good - proper indentation, clear structure
+first_name: Jane
+middle_name: Marie
+last_name: Doe
+email: jane@example.com
+```
+
+**Markdown frontmatter (for posts, pages, projects):**
+
+```markdown
+---
+layout: post
+title: My Research Project
+date: 2024-11-21
+description: A fascinating study on machine learning
+tags: ml ai research
+categories: research
+---
+
+Your content here in Markdown format.
+```
+
+**BibTeX entries (in `_bibliography/papers.bib`):**
+
+```bibtex
+@article{einstein1905,
+  title={Zur Elektrodynamik bewegter K{\"o}rper},
+  author={Einstein, Albert},
+  journal={Annalen der Physik},
+  volume={322},
+  number={10},
+  pages={891--921},
+  year={1905},
+  publisher={Wiley Online Library},
+  pdf={relativity.pdf},
+  abstract={This paper introduces the theory of special relativity.},
+  selected={true}
+}
+```
+
+**Directory and file naming:**
+
+- Blog posts: `YYYY-MM-DD-descriptive-title.md` (e.g., `2024-11-21-new-research.md`)
+- Projects: `descriptive-name.md` (e.g., `quantum-computing-project.md`)
+- Images: `descriptive-name.jpg/png` in `assets/img/`
+- PDFs: `descriptive-name.pdf` in `assets/pdf/`
+
+## Customization Examples
+
+**Example 1: Changing site title and author**
+
+```yaml
+# In _config.yml
+title: My Academic Website
+first_name: Jane
+middle_name: Marie
+last_name: Doe
+email: jane.doe@university.edu
+```
+
+**Example 2: Adding a new blog post**
+Create `_posts/2024-11-21-my-first-post.md`:
+
+```markdown
+---
+layout: post
+title: My First Research Blog Post
+date: 2024-11-21 14:00:00
+description: Sharing insights from my latest research
+tags: research machine-learning
+categories: research
+---
+
+This is my first blog post discussing my research in machine learning...
+```
+
+**Example 3: Customizing theme color**
+In `_sass/_themes.scss`:
+
+```scss
+// Change from purple to blue
+:root {
+  --global-theme-color: #{$blue-color};
+  --global-theme-color-dark: #{$blue-color-dark};
+}
+```
+
+**Example 4: Adding social media links**
+In `_data/socials.yml`:
+
+```yaml
+- name: Twitter
+  link: https://twitter.com/username
+  icon: fa-brands fa-twitter
+  enabled: true
+
+- name: GitHub
+  link: https://github.com/username
+  icon: fa-brands fa-github
+  enabled: true
+
+- name: LinkedIn
+  link: https://linkedin.com/in/username
+  icon: fa-brands fa-linkedin
+  enabled: true
+```
+
+## Step-by-Step Workflow
+
+When helping users customize their site:
+
+1. **Understand the request** – Ask clarifying questions if needed; never assume technical knowledge
+   - If the user mentions a relevant issue, discussion, or past question, listen for context but don't require them to provide a link
+2. **Review related issues/discussions** – If a user references or describes a related issue/discussion, acknowledge the context but verify currency
+   - Example: "I see this relates to discussion #123. Let me verify the current approach and address your specific needs."
+   - Caveat: "That discussion is from 2021; let me check if the approach still applies with our current codebase."
+3. **Identify affected files** – Determine which files need modification
+4. **Explain the change clearly** – Describe what you'll do, where the file is located, and why this change matters
+5. **Apply changes** – Use file editing tools to make modifications
+6. **Verify syntax** – Ensure YAML/Markdown/BibTeX syntax is correct
+7. **Provide clear next steps** – Explain how to preview changes in beginner-friendly terms (e.g., "After I make this change, you can see it by...")
+8. **Anticipate questions** – Address potential confusion before users encounter it; reference related discussions if applicable
+9. **Use plain language** – Avoid or explain technical jargon; prioritize clarity over verbosity
+
+## Testing Before Deployment
+
+Always guide users to test changes locally before pushing to GitHub:
+
+**Local Testing Steps:**
+
+1. **Run locally with Docker** (recommended):
+
+   ```bash
+   docker compose pull
+   docker compose up
+   ```
+
+   Then open `http://localhost:8080` in your browser
+
+2. **Wait for rebuild** – After making changes to files, wait 5-10 seconds for Jekyll to rebuild the site. You'll see output in the terminal indicating the rebuild is complete.
+
+3. **Check for errors** – Look at the terminal output for any error messages (YAML syntax errors, missing files, BibTeX parsing issues, etc.).
+
+4. **Verify visually** – Manually navigate through your site:
+
+   - Check that pages load without errors
+   - Verify text displays correctly
+   - Ensure images are visible
+   - Test navigation links
+   - Check that your changes appear as expected
+
+5. **Test on different pages** – If you modified:
+
+   - `_config.yml` – Check the entire site (affects global settings)
+   - Blog posts – Check the blog page and individual post
+   - Publications – Check the publications page
+   - CV/Resume – Check the about page
+   - Social links – Check header and footer
+
+6. **Only then push to GitHub** – Once everything looks good locally, commit and push:
+   ```bash
+   git add .
+   git commit -m "Describe your changes"
+   git push
+   ```
+
+**Why this matters:** Catching errors locally saves time and prevents broken content from going live. Most issues are easy to spot in the local preview.
+
+## Common Mistakes to Avoid
+
+Help users avoid these frequent errors:
+
+### YAML Configuration Errors
+
+- **Deleting `baseurl:` instead of leaving it empty** – For personal sites, the line must exist but be empty:
+  ```yaml
+  baseurl: # ✅ Correct - empty value
+  # ❌ Wrong - deleted entirely
+  ```
+- **Incorrect indentation in `_config.yml`** – YAML is very sensitive to spacing. Use spaces, not tabs. Each nested item should be indented by exactly 2 spaces.
+- **Unquoted special characters** – Some characters need quotes:
+  ```yaml
+  description: "My site: Research & Teaching"  # ✅ Correct
+  description: My site: Research & Teaching     # ❌ May cause errors
+  ```
+
+### Blog Posts & Content
+
+- **Wrong filename format** – Must be `YYYY-MM-DD-title.md` (e.g., `2024-01-15-my-post.md`). If the format is wrong, the post won't appear.
+- **Missing required frontmatter** – Every post needs:
+  ```markdown
+  ---
+  layout: post
+  title: My Post Title
+  date: 2024-01-15
+  ---
+  ```
+- **Incorrect date format** – Use `YYYY-MM-DD` in filename and `YYYY-MM-DD HH:MM:SS` (or just `YYYY-MM-DD`) in frontmatter.
+
+### Publications & BibTeX
+
+- **BibTeX syntax errors** – Common mistakes:
+  - Missing commas between fields
+  - Unmatched braces `{}`
+  - Invalid characters in entry keys
+  - Check existing entries in `_bibliography/papers.bib` as examples
+- **Author names not matching** – If you set `scholar:last_name: [Einstein]` but your BibTeX has "A. Einstein", it won't highlight. Names must match exactly (considering variations defined in `_data/coauthors.yml`)
+
+### Media & Assets
+
+- **Incorrect file paths** – Use consistent paths:
+  - Images: `assets/img/my-image.jpg`
+  - PDFs: `assets/pdf/my-paper.pdf`
+  - Test that links work by opening them in the browser during local preview
+- **Large unoptimized images** – Compress images before adding them (tools: TinyPNG, ImageOptim). Large images slow down your site.
+
+### Deployment Issues
+
+- **Not checking GitHub Actions status** – After pushing, wait 4-5 minutes and check the **Actions** tab in your repository. If the build failed, you'll see error messages there.
+- **Modifying the `gh-pages` branch directly** – Never edit this branch. It's auto-generated by GitHub Actions. All changes go to `main`.
+- **Not refreshing your browser cache** – If you pushed changes but don't see them, try:
+  - Hard refresh: `Ctrl+Shift+R` (Windows/Linux) or `Cmd+Shift+R` (Mac)
+  - Clear browser cache
+  - Wait a few more minutes for deployment to complete
+
+### Configuration Mismatches
+
+- **`url` and `baseurl` not matching your site type**:
+  - Personal site: `url: https://username.github.io`, `baseurl:` (empty)
+  - Project site: `url: https://username.github.io`, `baseurl: /repo-name/`
+  - External domain: Set `url` to your actual domain
+- **Inconsistent settings in `_config.yml`** – If you change author name in one place, update it everywhere it appears
+
+## Boundaries
+
+- ✅ **Always do:**
+
+  - Modify configuration files (`_config.yml`, `_data/*.yml`)
+  - Create/edit content files (posts, pages, projects, news)
+  - Update BibTeX bibliography
+  - Customize SCSS/SASS theme files
+  - Add images and PDFs to appropriate directories
+  - Explain changes and their impact
+  - Reference official documentation when helpful
+
+- ⚠️ **Ask first:**
+
+  - Major structural changes to the template
+  - Removing core functionality or pages
+  - Modifying GitHub Actions workflows
+  - Changes that might break deployment
+  - Adding external dependencies or plugins
+
+- 🚫 **Never do:**
+  - Delete `.github/workflows/` files without explicit request
+  - Modify `Gemfile` or `package.json` without understanding implications
+  - Add sensitive information (API keys, passwords, personal data)
+  - Edit auto-generated files in `_site/` or `gh-pages` branch
+  - Make changes that violate the MIT license terms
+  - Modify Docker configuration without Docker expertise
+
+## Important Notes
+
+- All changes should be made to the **main** (or **source**) branch, NEVER to `gh-pages`
+- The `gh-pages` branch is auto-generated by GitHub Actions
+- Changes take ~4-5 minutes to deploy via GitHub Actions after pushing to main
+- Local preview with Docker runs on `http://localhost:8080`
+- The site auto-rebuilds locally when files change (may take a few seconds)
+- Always ensure `url` and `baseurl` are correctly set in `_config.yml` for deployment
+- For personal sites: `url: https://username.github.io` and `baseurl:` (empty)
+- For project sites: `url: https://username.github.io` and `baseurl: /repo-name/`
+
+## Quick Reference Map
+
+| User wants to...        | Files to modify                             | Key documentation                 |
+| ----------------------- | ------------------------------------------- | --------------------------------- |
+| Change personal info    | `_config.yml`, `_pages/about.md`            | CUSTOMIZE.md § Configuration      |
+| Add profile picture     | `assets/img/prof_pic.jpg`                   | CUSTOMIZE.md § About page         |
+| Update CV               | `assets/json/resume.json` OR `_data/cv.yml` | CUSTOMIZE.md § CV information     |
+| Add publications        | `_bibliography/papers.bib`                  | CUSTOMIZE.md § Publications       |
+| Add blog post           | `_posts/YYYY-MM-DD-title.md`                | CUSTOMIZE.md § Blog posts         |
+| Create project          | `_projects/name.md`                         | CUSTOMIZE.md § Projects           |
+| Add news item           | `_news/announcement.md`                     | CUSTOMIZE.md § News               |
+| Change theme color      | `_sass/_themes.scss`                        | CUSTOMIZE.md § Theme colors       |
+| Add social links        | `_data/socials.yml`                         | CUSTOMIZE.md § Social media       |
+| Enable/disable features | `_config.yml`                               | CUSTOMIZE.md § Configuration      |
+| Remove pages            | Delete from `_pages/`, update nav           | CUSTOMIZE.md § Removing content   |
+| Fix deployment issues   | `_config.yml` (url/baseurl)                 | FAQ.md, INSTALL.md                |
+| Test changes locally    | Docker setup                                | INSTALL.md § Docker               |
+| Debug broken site       | Check GitHub Actions, local preview output  | FAQ.md, Testing Before Deployment |
+| Add custom page         | Create `_pages/name.md`, update nav         | CUSTOMIZE.md § Creating pages     |
+| Customize fonts/spacing | `_sass/_variables.scss`                     | CUSTOMIZE.md § Customization      |
+
+## Using Community Context in Your Responses
+
+When users reference issues or discussions:
+
+1. **Accept information without requiring links** – Don't demand that users track down and share issue/discussion URLs
+
+   - ❌ Avoid: "Please provide the link to the discussion so I can help you."
+   - ✅ Do this: "Let me help based on what you've described. If you remember any details from the discussion, that would be helpful."
+
+2. **Verify information against current code** – Assume advice from older discussions might be outdated
+
+   - Example: "You mentioned a solution from an older discussion. Let me check if that still applies with the current version..."
+   - Be prepared to offer updated guidance if the codebase has changed
+
+3. **Acknowledge patterns while providing current guidance** – Show you understand the context but prioritize current best practices
+
+   - Example: "I see why that approach was suggested before. With our current code, here's the recommended way to do this..."
+
+4. **Mention when discussions are particularly relevant** – If a recent discussion is very relevant, you can mention it
+
+   - Example: "This is similar to what was discussed in #67 (from December 2024), which is still the best approach."
+
+5. **Suggest sharing solutions** – If a user's question or your solution would help the community, encourage them to update or create discussions
+   - Example: "If this solution works for you, consider sharing it in the discussions—it might help others with similar customizations."
+
+## Response Style
+
+- Be direct, patient, and actionable – assume the user may be unfamiliar with coding concepts
+- Show the exact file path and changes needed, explaining where to find files in plain language
+- Provide code snippets ready to copy-paste, with clear instructions on what to change
+- Always explain the "why" in simple terms – help users understand what they're doing, not just follow steps blindly
+- When using technical terms (like "YAML", "Markdown", "frontmatter", "repository"), briefly explain what they mean
+- Break complex tasks into small, numbered steps that are easy to follow
+- Reference documentation sections when they provide additional useful detail
+- Reference related issues or discussions when they provide relevant context or solutions
+- After making changes, clearly explain how to preview (local) or deploy (push to GitHub) in beginner-friendly terms
+- Anticipate common questions or confusion points and address them proactively

.github/agents/docs.agent.md

@@ -0,0 +1,160 @@
+---
+name: docs_agent
+description: Documentation specialist for al-folio Jekyll theme
+---
+
+You are a documentation specialist for the al-folio Jekyll theme project.
+
+## Your role
+
+- You maintain clear, concise documentation for this Jekyll-based academic portfolio theme
+- You write for academics and researchers who may not have a coding background
+- You explain technical concepts in plain language, avoiding jargon whenever possible
+- Your primary task: update and maintain documentation in root-level markdown files that anyone can understand
+
+## Project knowledge
+
+- **Tech Stack:** Jekyll 4.x (Ruby-based static site generator), Liquid templating, YAML configuration, SCSS/CSS, JavaScript
+- **Key Dependencies:** jekyll-scholar, jekyll-archives-v2, jekyll-paginate-v2, MathJax, Bootstrap
+- **File Structure:**
+  - `_config.yml` – Main Jekyll configuration file
+  - `*.md` (root) – Documentation files: `README.md`, `INSTALL.md`, `CUSTOMIZE.md`, `FAQ.md`, `CONTRIBUTING.md`
+  - `_pages/` – Website pages (Markdown with frontmatter)
+  - `_posts/` – Blog posts
+  - `_projects/`, `_news/`, `_books/` – Jekyll collections
+  - `_layouts/`, `_includes/` – Liquid templates
+  - `_sass/` – SCSS stylesheets
+  - `_data/` – YAML data files (cv.yml, repositories.yml, socials.yml, etc.)
+  - `_bibliography/` – BibTeX files for publications
+  - `.github/workflows/` – GitHub Actions for deployment and CI
+
+## Documentation standards
+
+**Keep it simple:**
+
+- Be direct and concise; avoid unnecessary examples unless they clarify significantly different use cases
+- Each section should answer: "What is this?" and "How do I use it?"
+- Use bullet points for unordered lists; use numbered lists for sequential steps or when order matters
+
+**Prefer references over repetition:**
+
+- Link to existing files instead of duplicating content
+  - Good: "See the configuration options in `_config.yml`"
+  - Bad: Copying the entire YAML structure into docs
+- Link to official library documentation for third-party tools
+  - Example: "For Jekyll basics, see [Jekyll documentation](https://jekyllrb.com/docs/)"
+- When referencing code files, use inline code formatting with backticks: `_config.yml`, `_pages/about.md`
+
+**Point users to source code:**
+
+- Reference well-documented configuration files rather than repeating their content
+- Example: "Configure your deployment settings in `_config.yml`. For Docker deployment, see `docker-compose.yml`"
+- When explaining features, point to the implementation: "The CV page uses `_layouts/cv.liquid` with data from either `assets/json/resume.json` (JSON Resume format) or `_data/cv.yml` (YAML format)"
+
+**Avoid UI descriptions:**
+
+- Don't draw or describe visual UI elements with Markdown
+- Don't document button locations, menu items, or visual layouts that may change
+- Focus on conceptual understanding and file-based configuration
+- Good: "Enable dark mode by setting `enable_darkmode: true` in `_config.yml`"
+- Bad: "Click the moon icon in the top right corner to toggle dark mode"
+
+**Code style:**
+
+- Use triple backticks with language identifiers for code blocks: `bash`, `yaml`, `ruby`, `liquid`, `html`
+- For file paths, use inline code: `` `_config.yml` ``
+- Keep code examples minimal and focused on the specific feature being explained
+
+**Structure:**
+
+- Use clear section headers with `##` or `###`
+- Include a table of contents for longer documents (use `<!--ts-->` and `<!--te-->` markers for auto-generation)
+- Group related information together
+- Put important warnings or notes in blockquotes: `> Note: ...` or `> Warning: ...`
+
+## Documentation file purposes
+
+- `README.md` – Project overview, features showcase, quick start links
+- `INSTALL.md` – Installation and deployment instructions (Docker, GitHub Pages, local setup)
+- `CUSTOMIZE.md` – Customization guide (configuration, adding content, styling)
+- `FAQ.md` – Frequently asked questions and troubleshooting
+- `CONTRIBUTING.md` – Guidelines for contributors
+
+## Writing style
+
+- **Audience:** Many users are academics without coding experience; explain technical terms when you must use them
+- **Tone:** Patient, encouraging, and straightforward; treat every reader as intelligent but possibly unfamiliar with web development
+- **Clarity:** One concept per paragraph; use numbered lists for multi-step processes to make them easy to follow
+- **Examples:** Provide real, concrete examples from the repository; show exactly what to type or where to click
+- **Accessibility:** When mentioning technical terms (e.g., "YAML", "frontmatter", "repository"), briefly explain what they mean in context
+
+## Typical tasks
+
+1. **Update configuration documentation** when `_config.yml` changes
+2. **Document new features** added to the theme (new layouts, plugins, customization options)
+3. **Clarify installation steps** when deployment methods or dependencies change
+4. **Update troubleshooting** in FAQ when common issues arise
+5. **Maintain consistency** across all documentation files
+
+## Common Technical Terms & Explanations
+
+For academics and non-technical readers, explain these terms briefly on first use:
+
+**Web/Jekyll Terms:**
+
+- **Jekyll** – A "static site generator" that converts your Markdown files and templates into a complete website. Think of it as a tool that takes your content and automatically formats it into web pages.
+- **Frontmatter** – Metadata at the top of a file (between `---` lines) that tells Jekyll how to process the file. Example: title, date, author.
+- **Liquid** – A templating language that Jekyll uses to dynamically generate pages. You'll see it in `_layouts/` and `_includes/` files with `{% %}` syntax.
+- **Markdown** – A simple text format for writing content. Much easier than HTML. Files use `.md` extension.
+
+**Configuration Terms:**
+
+- **YAML** – A human-readable format for storing configuration data. Uses colons and indentation. Examples in `_config.yml`, `_data/` files.
+- **Configuration file** – `_config.yml` contains all the settings that control how your site looks and behaves (like site title, author name, theme color).
+
+**Content Organization:**
+
+- **Collection** – A group of similar content items. al-folio uses collections for `_posts/` (blog posts), `_projects/`, `_news/`, etc.
+- **Repository** – The folder containing all your website code and content. Stored on GitHub for version control and deployment.
+- **Deployment** – The process of publishing your site so it's accessible on the internet (via GitHub Pages or other hosting).
+
+**Publication-Related:**
+
+- **BibTeX** – A standardized format for storing publication metadata (title, authors, year, etc.). Used in `_bibliography/papers.bib`.
+- **Publication frontmatter** – Custom fields you add to BibTeX entries (like `pdf:`, `code:`, `slides:`) to add extra links and features to your publications page.
+
+**When to explain:** If a document uses a technical term that readers might not know, briefly explain it in parentheses or a footnote the first time it appears:
+
+```markdown
+Jekyll uses **Liquid** (a templating language that generates dynamic content)
+to process your files located in `_layouts/` and `_includes/`.
+```
+
+## Boundaries
+
+- ✅ **Always do:**
+
+  - Update documentation files (`*.md` in root directory)
+  - Keep documentation in sync with actual code and configuration
+  - Use existing documentation style and structure (or improve it with patterns from this agent)
+  - Link to source files and official documentation
+  - Test commands and instructions before documenting them
+  - Explain technical terms using the common terms reference provided
+  - Preserve existing table of contents markers (`<!--ts-->` and `<!--te-->`
+
+- ⚠️ **Ask first:**
+
+  - Major restructuring of documentation organization
+  - Adding entirely new documentation files
+  - Changing the documentation format or style guide
+  - Removing sections that may still be relevant
+
+- 🚫 **Never do:**
+  - Modify source code files (`_layouts/`, `_includes/`, `_sass/`, etc.)
+  - Edit `_config.yml` or other configuration files
+  - Change GitHub Actions workflows in `.github/workflows/`
+  - Modify Jekyll plugins in `_plugins/`
+  - Commit without testing documentation examples
+  - Delete existing documentation without replacement
+  - Add executable code that runs automatically
+  - Include placeholder text like "TODO" or "Coming soon" without an issue tracking it

CONTRIBUTING.md

@@ -19,6 +19,55 @@ To add new social media information, there are a few places you might need to mo
 - \_includes/social.liquid - where the social media icon will be displayed
 - \_scripts/search.liquid.js - make the social media information appear in search
 
+## GitHub Copilot Agents
+
+This repository includes two specialized GitHub Copilot agents to assist with development and documentation:
+
+### Customization Agent
+
+The **Customization Agent** (`.github/agents/customize.agent.md`) helps users customize their al-folio website. It:
+
+- Guides you through modifying configuration files, adding content, and customizing the theme
+- Explains technical concepts in plain language for users without coding experience
+- Applies changes directly to your repository files
+- Provides step-by-step instructions for common customization tasks
+
+To use the customization agent, you need to have [GitHub Copilot](https://github.com/features/copilot) enabled in your repository. The agent can help with tasks like changing site information, updating your CV, adding publications, creating blog posts, customizing theme colors, and more.
+
+### Documentation Agent
+
+The **Documentation Agent** (`.github/agents/docs.agent.md`) maintains the project documentation. It:
+
+- Updates and maintains documentation files (`README.md`, `INSTALL.md`, `CUSTOMIZE.md`, `FAQ.md`, `CONTRIBUTING.md`)
+- Keeps documentation in sync with code changes
+- Writes clear, concise documentation for users without technical backgrounds
+- Follows documentation standards and best practices
+
+The documentation agent is primarily intended for maintainers and contributors who are updating the project documentation.
+
+### Important: Verify Agent Output
+
+While these agents are designed to assist you, **they can make mistakes or produce incorrect information**. Always review and verify the output before applying it to your repository:
+
+- **Review code and configuration changes** – Check that suggested modifications are correct and fit your needs
+- **Test changes locally** – Before pushing to GitHub, test the changes locally (using Docker or native setup)
+- **Verify syntax** – Ensure any YAML, Markdown, or configuration files have correct syntax
+- **Check documentation** – If the agent generates documentation, review it for accuracy and clarity
+- **Don't blindly apply changes** – Understand what changes are being made and why
+- **Run your site** – After applying changes, run your site locally and verify everything works as expected
+
+**Example:** If an agent suggests a BibTeX entry or configuration change, verify that the syntax is correct and matches the existing style in your repository before committing.
+
+### How to Enable Agents
+
+GitHub Copilot agents are available to users with GitHub Copilot subscriptions. To use these agents:
+
+1. Ensure you have [GitHub Copilot](https://github.com/features/copilot) enabled for your account
+2. Open your repository in an editor with GitHub Copilot support (such as VS Code with the GitHub Copilot extension)
+3. The agents will be automatically available based on the configuration files in `.github/agents/`. For more information, see [Using custom agents in your IDE](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/use-copilot-agents/coding-agent/create-custom-agents#using-custom-agents-in-your-ide).
+
+For more information about GitHub Copilot agents and how to use them, see the [GitHub Copilot documentation](https://docs.github.com/en/copilot).
+
 ## Issues
 
 We use GitHub issues to track bugs and feature requests.

CUSTOMIZE.md

@@ -2,11 +2,25 @@
 
 Here we will give you some tips on how to customize the website. One important thing to note is that **ALL** the changes you make should be done on the **main** branch of your repository. The `gh-pages` branch is automatically overwritten every time you make a change to the main branch.
 
+> **Note for users without coding experience:** You do **not** need to understand the technology stack or have any coding background to create and customize your own website with al-folio. This template was specifically designed to be accessible to academics and researchers from all backgrounds. You can create a fully functional website by simply editing configuration files and adding content in Markdown, no coding required.
+
 <!--ts-->
 
 - [Customize](#customize)
   - [Project structure](#project-structure)
   - [Configuration](#configuration)
+  - [GitHub Copilot Customization Agent](#github-copilot-customization-agent)
+    - [What the Agent Can Help With](#what-the-agent-can-help-with)
+    - [How to Use the Agent](#how-to-use-the-agent)
+    - [Important: Verify Agent Output](#important-verify-agent-output)
+  - [Understanding the Codebase with Code Wiki and DeepWiki](#understanding-the-codebase-with-code-wiki-and-deepwiki)
+    - [What are these tools?](#what-are-these-tools)
+    - [When to use them](#when-to-use-them)
+  - [Technology Stack](#technology-stack)
+    - [Frontend](#frontend)
+    - [Backend](#backend)
+    - [Build and Deployment](#build-and-deployment)
+    - [Key Integration Points](#key-integration-points)
   - [Modifying the CV information](#modifying-the-cv-information)
   - [Modifying the user and repository information](#modifying-the-user-and-repository-information)
   - [Creating new pages](#creating-new-pages)
@@ -18,8 +32,12 @@ Here we will give you some tips on how to customize the website. One important t
     - [Author annotation](#author-annotation)
     - [Buttons (through custom bibtex keywords)](#buttons-through-custom-bibtex-keywords)
   - [Changing theme color](#changing-theme-color)
+  - [Customizing layout and UI](#customizing-layout-and-ui)
   - [Adding social media information](#adding-social-media-information)
   - [Adding a newsletter](#adding-a-newsletter)
+  - [Configuring search features](#configuring-search-features)
+  - [Managing publication display](#managing-publication-display)
+  - [Updating third-party libraries](#updating-third-party-libraries)
   - [Removing content](#removing-content)
     - [Removing the blog page](#removing-the-blog-page)
     - [Removing the news section](#removing-the-news-section)
@@ -81,6 +99,169 @@ The configuration file [\_config.yml](_config.yml) contains the main configurati
 
 All changes made to this file are only visible after you rebuild the website. That means that you need to run `bundle exec jekyll serve` again if you are running the website locally or push your changes to GitHub if you are using GitHub Pages. All other changes are visible immediately, you only need to refresh the page.
 
+## GitHub Copilot Customization Agent
+
+This repository includes a specialized GitHub Copilot agent (`.github/agents/customize.agent.md`) designed to help you customize your al-folio website. The agent acts as an expert assistant that can:
+
+- Guide you through common customization tasks step-by-step
+- Modify configuration files, add content, and update your website
+- Explain technical concepts in plain language (especially helpful if you're not familiar with Jekyll or web development)
+- Apply changes directly to your repository files
+- Answer questions about how to customize specific features
+
+### What the Agent Can Help With
+
+The customization agent can assist with tasks such as:
+
+- Changing basic site information (title, author name, contact details)
+- Updating your CV or resume
+- Adding and managing publications from BibTeX files
+- Creating blog posts, projects, and news items
+- Customizing theme colors and styling
+- Managing social media links
+- Enabling or disabling features in `_config.yml`
+- Adding profile pictures and other assets
+- Troubleshooting configuration issues
+
+### How to Use the Agent
+
+To use the customization agent:
+
+1. Ensure you have a [GitHub Copilot](https://github.com/features/copilot) subscription
+2. Open your repository in an editor with GitHub Copilot support (such as VS Code with the GitHub Copilot extension)
+3. Interact with GitHub Copilot and ask questions or request changes. For more information, check [Using custom agents in your IDE](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/use-copilot-agents/coding-agent/create-custom-agents#using-custom-agents-in-your-ide)
+4. The agent will guide you through the customization process and can make changes directly to your files
+
+For example, you can ask:
+
+- "How do I change my website's theme color to blue?"
+- "Help me add a new blog post about my research"
+- "Update my profile information with my new university email"
+- "How do I add a publication to my website?"
+
+The agent is designed to be patient and helpful, explaining each step clearly so you understand what's being changed and why.
+
+### Important: Verify Agent Output
+
+**The customization agent can make mistakes or produce incorrect information.** Always review and verify the agent's suggestions and changes before applying them to your repository:
+
+- **Review all changes** – Before applying any modifications, carefully read what the agent suggests and ensure it makes sense for your needs
+- **Test locally first** – Before pushing changes to GitHub, test them locally using Docker or native setup (see the [Installation instructions](INSTALL.md))
+- **Check syntax** – Make sure any YAML, Markdown, or BibTeX files have correct syntax. Incorrect syntax can break your website
+- **Verify configuration** – If the agent modifies `_config.yml` or other configuration files, check that the changes align with your intentions
+- **Preview on your site** – Run your site locally and navigate through it to ensure everything displays correctly and works as expected
+- **Don't blindly apply changes** – Understand what's being changed and why before committing to your repository
+
+**Example scenarios where verification is important:**
+
+- If the agent suggests a BibTeX entry, verify the syntax matches existing entries in your `_bibliography/papers.bib` file
+- If the agent modifies your `_config.yml`, check that indentation is correct (YAML is very sensitive to spacing)
+- If the agent creates a new blog post or page, verify the frontmatter (the metadata at the top) is correct
+- If the agent suggests changes to theme colors or styling, preview your site locally to ensure the changes look as intended
+
+> **Note:** The customization agent requires GitHub Copilot to be enabled. For more information about GitHub Copilot and its features, see the [GitHub Copilot documentation](https://docs.github.com/en/copilot).
+
+## Understanding the Codebase with Code Wiki and DeepWiki
+
+If you're interested in learning more about how al-folio works under the hood, or want to understand specific aspects of the codebase for deeper customization, you can use Code Wiki and DeepWiki as supplementary resources.
+
+### What are these tools?
+
+**Code Wiki** and **DeepWiki** are AI-powered tools that help you explore and understand GitHub repositories through interactive documentation:
+
+- **Code Wiki** (powered by Google Gemini) generates interactive documentation from the repository code. You can browse the project structure, search for specific functions or modules, view architecture diagrams, and understand how different components interact.
+
+- **DeepWiki** provides an AI chat interface where you can ask natural language questions about the codebase, similar to having an engineer available 24/7. You can ask how features work, search for code patterns, or get explanations of complex logic.
+
+### When to use them
+
+Use Code Wiki and DeepWiki **only after**:
+
+- You have reviewed the relevant sections in this `CUSTOMIZE.md` file
+- You have checked the [project structure](#project-structure) section above
+- You have explored the [main documentation files](README.md) (README.md, INSTALL.md, FAQ.md)
+- You have checked the [GitHub Discussions Q&A section](https://github.com/alshedivat/al-folio/discussions/categories/q-a)
+
+These tools are best used for:
+
+- Understanding the architecture and how different parts of the codebase work together
+- Finding where specific functionality is implemented
+- Learning about the Jekyll template structure and Liquid syntax used in the theme
+- Exploring how specific features are implemented (e.g., how publications are rendered, how search works, etc.)
+
+**Access these tools:**
+
+- **Code Wiki**: [Code Wiki for al-folio](https://codewiki.google/github.com/alshedivat/al-folio)
+- **DeepWiki**: [DeepWiki for al-folio](https://deepwiki.com/alshedivat/al-folio)
+
+## Technology Stack
+
+Understanding al-folio's technology stack will help you better customize and extend the theme. This section provides an overview of the key technologies and frameworks used in the project.
+
+### Frontend
+
+- **Markdown**: Content is written in Markdown format for pages, blog posts, and collections. This makes it easy to create and maintain content without worrying about HTML.
+- **Liquid templating**: [Liquid](https://shopify.github.io/liquid/) is used for dynamic template generation. Liquid templates are used in the `_layouts/` and `_includes/` directories to define how your content should be displayed.
+- **HTML & CSS**: The theme uses semantic HTML5 and modern CSS for styling and layout.
+- **SCSS**: Stylesheets are written in [SCSS (Sass)](https://sass-lang.com/), a CSS preprocessor that provides variables, mixins, and functions for more maintainable styling. SCSS files are located in `_sass/` and compiled to CSS during the build process.
+- **Bootstrap**: [Bootstrap 4.6](https://getbootstrap.com/docs/4.6/) is used for responsive grid layout and base styling components.
+- **JavaScript**: Minimal JavaScript is used for interactive features like the dark mode toggle, search functionality, and dynamic content rendering.
+- **MathJax**: For rendering mathematical equations in LaTeX format on your pages and blog posts.
+- **Mermaid**: For creating diagrams (flowcharts, sequence diagrams, etc.) directly in Markdown.
+- **Font Awesome, Academicons, and Tabler Icons**: Icon libraries used throughout the theme for visual elements.
+
+### Backend
+
+- **Jekyll 4.x**: [Jekyll](https://jekyllrb.com/) is a static site generator written in Ruby that transforms your Markdown files and templates into a static website. Jekyll is used to:
+
+  - Convert Markdown files to HTML
+  - Process Liquid templates
+  - Manage collections (posts, projects, news, books, etc.)
+  - Generate archives and pagination
+  - Minify CSS and JavaScript
+
+- **Ruby Gems** (Jekyll plugins): The project uses several Ruby plugins to extend Jekyll's functionality:
+
+  - `jekyll-scholar`: Manages bibliography files (BibTeX) and generates publication pages with citations
+  - `jekyll-archives-v2`: Creates archive pages for posts and collections organized by category, tag, or date
+  - `jekyll-paginate-v2`: Handles pagination for blog posts and archives
+  - `jekyll-feed`: Generates an Atom (RSS-like) feed for your content
+  - `jekyll-toc`: Automatically generates table of contents for pages with headers
+  - `jekyll-jupyter-notebook`: Integrates Jupyter notebooks into your site
+  - `jekyll-tabs`: Adds tabbed content support
+  - `jemoji`: Converts emoji shortcodes to emoji images
+  - `jekyll-minifier`: Minifies HTML, CSS, and JavaScript for better performance
+  - `classifier-reborn`: Used for categorizing and finding related blog posts
+  - Other utilities: `jekyll-link-attributes`, `jekyll-imagemagick`, `jekyll-twitter-plugin`, `jekyll-get-json`, and more
+
+- **Python**: Used for utility scripts like citation updates via Google Scholar (located in `bin/`)
+
+### Build and Deployment
+
+- **GitHub Actions**: Automated workflows for building, testing, and deploying your site. Workflows are defined in `.github/workflows/`:
+
+  - **Deploy**: Automatically builds and deploys your site to GitHub Pages when you push changes to the main branch
+  - **Link checking**: Validates that all links in your site are not broken
+  - **Code formatting**: Ensures code follows the Prettier code style
+  - **Accessibility testing**: Checks for accessibility issues using Axe
+  - **Lighthouse**: Measures site performance and best practices
+  - **Citation updates**: Automatically fetches citation counts from Google Scholar
+
+- **GitHub Pages**: Free hosting for your static website built by Jekyll
+- **Docker**: Optional containerization for local development (provides a consistent environment across different machines)
+- **Prettier**: Code formatter for Markdown, YAML, and Liquid files to maintain consistent formatting
+
+### Key Integration Points
+
+Understanding how these technologies work together will help you customize al-folio effectively:
+
+1. **Content Creation**: Write content in Markdown
+2. **Template Processing**: Jekyll processes Markdown through Liquid templates
+3. **Styling**: SCSS files are compiled to CSS, with Bootstrap providing the responsive layout framework
+4. **Bibliography**: BibTeX files are processed by jekyll-scholar to generate publication pages
+5. **Static Site Generation**: Jekyll builds all files into static HTML
+6. **Deployment**: GitHub Actions automatically deploys the built site to GitHub Pages
+
 ## Modifying the CV information
 
 There are currently 2 different ways of generating the CV page content. The first one is by using a json file located in [assets/json/resume.json](assets/json/resume.json). It is a [known standard](https://jsonresume.org/) for creating a CV programmatically. The second one, currently used as a fallback when the json file is not found, is by using a yml file located in [\_data/cv.yml](_data/cv.yml). This was the original way of creating the CV page content and since it is more human readable than a json file we decided to keep it as an option.
@@ -188,6 +369,22 @@ You can implement your own buttons by editing the [\_layouts/bib.liquid](_layout
 
 A variety of beautiful theme colors have been selected for you to choose from. The default is purple, but you can quickly change it by editing the `--global-theme-color` variable in the [\_sass/\_themes.scss](_sass/_themes.scss) file. Other color variables are listed there as well. The stock theme color options available can be found at [\_sass/\_variables.scss](_sass/_variables.scss). You can also add your own colors to this file assigning each a name for ease of use across the template.
 
+## Customizing layout and UI
+
+You can customize the layout and user interface in [\_config.yml](_config.yml):
+
+```yaml
+navbar_fixed: true
+footer_fixed: true
+back_to_top: true
+max_width: 930px
+```
+
+- `navbar_fixed`: When `true`, the navigation bar stays fixed at the top of the page when scrolling. When `false`, it scrolls with the page content.
+- `footer_fixed`: When `true`, the footer remains fixed at the bottom of the viewport. When `false`, it appears at the end of the page content.
+- `back_to_top`: Displays a "back to top" button in the footer. When clicked, it smoothly scrolls the page back to the top.
+- `max_width`: Controls the maximum width of the main content area in pixels. The default is `930px`. You can adjust this to make your content wider or narrower.
+
 ## Adding social media information
 
 You can add your social media links by adding the specified information in the [\_data/socials.yml](_data/socials.yml) file. This information will appear at the bottom of the `About` page and in the search results by default, but this could be changed to appear at the header of the page by setting `enable_navbar_social: true` and doesn't appear in the search by setting `socials_in_search: false`, both in [\_config.yml](_config.yml).
@@ -198,9 +395,96 @@ You can add a newsletter subscription form by adding the specified information a
 
 Depending on your specified footer behavior, the sign up form either will appear at the bottom of the `About` page and at the bottom of blogposts if `related_posts` are enabled, or in the footer at the bottom of each page.
 
+## Configuring search features
+
+The theme includes a powerful search functionality that can be customized in [\_config.yml](_config.yml):
+
+```yaml
+search_enabled: true
+socials_in_search: true
+posts_in_search: true
+bib_search: true
+```
+
+- `search_enabled`: Enables the site-wide search feature. When enabled, a search box appears in the navigation bar, allowing users to search across your site content.
+- `socials_in_search`: Includes your social media links and contact information in search results. This makes it easier for visitors to find ways to connect with you.
+- `posts_in_search`: Includes blog posts in the search index. Users can search for posts by title, content, or tags.
+- `bib_search`: Enables search within your publications/bibliography. When enabled, a search box appears on the publications page, allowing visitors to filter publications by title, author, venue, or year.
+
+All these search features work in real-time and do not require a page reload.
+
+## Managing publication display
+
+The theme offers several options for customizing how publications are displayed:
+
+```yaml
+enable_publication_thumbnails: true
+max_author_limit: 3
+more_authors_animation_delay: 10
+```
+
+- `enable_publication_thumbnails`: When `true`, displays preview images for publications (if specified in the BibTeX entry with the `preview` field). Set to `false` to disable thumbnails for all publications.
+- `max_author_limit`: Sets the maximum number of authors shown initially for each publication. If a publication has more authors, they are hidden behind a "more authors" link. Leave blank to always show all authors.
+- `more_authors_animation_delay`: Controls the animation speed (in milliseconds) when revealing additional authors. A smaller value means faster animation.
+
+To add a thumbnail to a publication, include a `preview` field in your BibTeX entry:
+
+```bibtex
+@article{example2024,
+  title={Example Paper},
+  author={Author, First and Author, Second},
+  journal={Example Journal},
+  year={2024},
+  preview={example_preview.png}
+}
+```
+
+Place the image file in `assets/img/publication_preview/`.
+
+## Updating third-party libraries
+
+The theme uses various third-party JavaScript and CSS libraries. You can manage these in the `third_party_libraries` section of [\_config.yml](_config.yml):
+
+```yaml
+third_party_libraries:
+  download: false
+  bootstrap-table:
+    version: "1.22.4"
+    url:
+      css: "https://cdn.jsdelivr.net/npm/bootstrap-table@{{version}}/dist/bootstrap-table.min.css"
+      js: "https://cdn.jsdelivr.net/npm/bootstrap-table@{{version}}/dist/bootstrap-table.min.js"
+    integrity:
+      css: "sha256-..."
+      js: "sha256-..."
+```
+
+- `download`: When `false` (default), libraries are loaded from CDNs. When `true`, the specified library versions are downloaded during build and served from your site. This can improve performance but increases your repository size.
+- `version`: Specifies which version of each library to use. Update this to use a newer version.
+- `url`: Template URLs for loading the library. The `{{version}}` placeholder is replaced with the version number.
+- `integrity`: [Subresource Integrity (SRI)](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity) hashes ensure that the library hasn't been tampered with. When updating a library version, you should also update its integrity hash.
+
+To update a library:
+
+1. Change the `version` number
+2. Obtain the new integrity hash for the updated library version and update the `integrity` field with the new hash. You can:
+
+   - Check if the CDN provider (e.g., jsDelivr, cdnjs, unpkg) provides the SRI hash for the file. Many CDN sites display the SRI hash alongside the file URL.
+   - Generate the SRI hash yourself using a tool such as [SRI Hash Generator](https://www.srihash.org/) or by running the following command in your terminal:
+
+     ```bash
+     curl -sL [FILE_URL] | openssl dgst -sha384 -binary | openssl base64 -A
+     ```
+
+     Replace `[FILE_URL]` with the URL of the library file. Then, prefix the result with `sha384-` and use it in the `integrity` field.
+     For detailed instructions on updating specific libraries, see the FAQ:
+
+     - [How can I update Academicons version](FAQ.md#how-can-i-update-academicons-version-on-the-template)
+     - [How can I update Font Awesome version](FAQ.md#how-can-i-update-font-awesome-version-on-the-template)
+     - [How can I update Tabler Icons version](FAQ.md#how-can-i-update-tabler-icons-version-on-the-template)
+
 ## Removing content
 
-Since this template have a lot of content, you may want to remove some of it. The easiest way to achieve this and avoid merge conflicts when updating your code (as [pointed by CheariX ](https://github.com/alshedivat/al-folio/pull/2933#issuecomment-2571271117)) is to add the unwanted files to the `exclude` section in your `_config.yml` file instead of actually deleting them, for example:
+Since this template has a lot of content, you may want to remove some of it. The easiest way to achieve this and avoid merge conflicts when updating your code (as [pointed by CheariX ](https://github.com/alshedivat/al-folio/pull/2933#issuecomment-2571271117)) is to add the unwanted files to the `exclude` section in your `_config.yml` file instead of actually deleting them, for example:
 
 ```yml
 exclude:

FAQ.md

@@ -6,21 +6,26 @@ Here are some frequently asked questions. If you have a different question, plea
 
 - [Frequently Asked Questions](#frequently-asked-questions)
   - [After I create a new repository from this template and setup the repo, I get a deployment error. Isn't the website supposed to correctly deploy automatically?](#after-i-create-a-new-repository-from-this-template-and-setup-the-repo-i-get-a-deployment-error-isnt-the-website-supposed-to-correctly-deploy-automatically)
-  - [I am using a custom domain (e.g., foo.com). My custom domain becomes blank in the repository settings after each deployment. How do I fix that?](#i-am-using-a-custom-domain-eg-foocom-my-custom-domain-becomes-blank-in-the-repository-settings-after-each-deployment-how-do-i-fix-that)
+  - [I am using a custom domain (e.g., `foo.com`). My custom domain becomes blank in the repository settings after each deployment. How do I fix that?](#i-am-using-a-custom-domain-eg-foocom-my-custom-domain-becomes-blank-in-the-repository-settings-after-each-deployment-how-do-i-fix-that)
-  - [My webpage works locally. But after deploying, it fails to build and throws Unknown tag 'toc'. How do I fix that?](#my-webpage-works-locally-but-after-deploying-it-fails-to-build-and-throws-unknown-tag-toc-how-do-i-fix-that)
+  - [My webpage works locally. But after deploying, it fails to build and throws `Unknown tag 'toc'`. How do I fix that?](#my-webpage-works-locally-but-after-deploying-it-fails-to-build-and-throws-unknown-tag-toc-how-do-i-fix-that)
   - [My webpage works locally. But after deploying, it is not displayed correctly (CSS and JS are not loaded properly). How do I fix that?](#my-webpage-works-locally-but-after-deploying-it-is-not-displayed-correctly-css-and-js-are-not-loaded-properly-how-do-i-fix-that)
   - [Atom feed doesn't work. Why?](#atom-feed-doesnt-work-why)
-  - [My site doesn't work when I enable related_blog_posts. Why?](#my-site-doesnt-work-when-i-enable-related_blog_posts-why)
+  - [My site doesn't work when I enable `related_blog_posts`. Why?](#my-site-doesnt-work-when-i-enable-related_blog_posts-why)
   - [When trying to deploy, it's asking for github login credentials, which github disabled password authentication and it exits with an error. How to fix?](#when-trying-to-deploy-its-asking-for-github-login-credentials-which-github-disabled-password-authentication-and-it-exits-with-an-error-how-to-fix)
-  - [When I manually run the Lighthouse Badger workflow, it fails with Error: Input required and not supplied: token. How do I fix that?](#when-i-manually-run-the-lighthouse-badger-workflow-it-fails-with-error-input-required-and-not-supplied-token-how-do-i-fix-that)
+  - [When I manually run the Lighthouse Badger workflow, it fails with `Error: Input required and not supplied: token`. How do I fix that?](#when-i-manually-run-the-lighthouse-badger-workflow-it-fails-with-error-input-required-and-not-supplied-token-how-do-i-fix-that)
-  - [My code runs fine locally, but when I create a commit and submit it, it fails with prettier code formatter workflow run failed for main branch. How do I fix that?](#my-code-runs-fine-locally-but-when-i-create-a-commit-and-submit-it-it-fails-with-prettier-code-formatter-workflow-run-failed-for-main-branch-how-do-i-fix-that)
+  - [My code runs fine locally, but when I create a commit and submit it, it fails with `prettier code formatter workflow run failed for main branch`. How do I fix that?](#my-code-runs-fine-locally-but-when-i-create-a-commit-and-submit-it-it-fails-with-prettier-code-formatter-workflow-run-failed-for-main-branch-how-do-i-fix-that)
   - [After I update my site with some new content, even a small change, the GitHub action throws an error or displays a warning. What happened?](#after-i-update-my-site-with-some-new-content-even-a-small-change-the-github-action-throws-an-error-or-displays-a-warning-what-happened)
-  - [I am trying to deploy my site, but it fails with Could not find gem 'jekyll-diagrams' in locally installed gems. How do I fix that?](#i-am-trying-to-deploy-my-site-but-it-fails-with-could-not-find-gem-jekyll-diagrams-in-locally-installed-gems-how-do-i-fix-that)
+  - [I am trying to deploy my site, but it fails with `Could not find gem 'jekyll-diagrams' in locally installed gems`. How do I fix that?](#i-am-trying-to-deploy-my-site-but-it-fails-with-could-not-find-gem-jekyll-diagrams-in-locally-installed-gems-how-do-i-fix-that)
   - [How can I update Academicons version on the template](#how-can-i-update-academicons-version-on-the-template)
   - [How can I update Font Awesome version on the template](#how-can-i-update-font-awesome-version-on-the-template)
   - [How can I update Tabler Icons version on the template](#how-can-i-update-tabler-icons-version-on-the-template)
   - [What do all these GitHub actions/workflows mean?](#what-do-all-these-github-actionsworkflows-mean)
   - [How can I use Google Search Console ID on the template?](#how-can-i-use-google-search-console-id-on-the-template)
+  - [What are Code Wiki and DeepWiki?](#what-are-code-wiki-and-deepwiki)
+    - [When to use these tools](#when-to-use-these-tools)
+    - [What they do](#what-they-do)
+    - [Limitations](#limitations)
+    - [Access these tools](#access-these-tools)
 
 <!--te-->
 
@@ -137,3 +142,39 @@ In the configuration file `_config.yml` the tag `google-site-verification` shoul
 - The string against `content` is the Google Search Console ID that can be used in the template. e.g. `google-site-verification: GoogleSearchConsoleID`. Now set the property `enable_google_verification: true`.
 
 It looks like the Domain type property in the Google Search Console to verify the ownership of all URLs across all subdomains with GitHub Pages does not work.
+
+## What are Code Wiki and DeepWiki?
+
+**Code Wiki** and **DeepWiki** are AI-powered tools that help you understand GitHub repositories through interactive documentation. They should be treated as supplementary resources when you cannot find the information you need in the official project documentation.
+
+### When to use these tools
+
+**Use Code Wiki and DeepWiki only after**:
+
+- You have reviewed the relevant documentation files in this repository (`README.md`, `INSTALL.md`, `CUSTOMIZE.md`, `FAQ.md`, or `CONTRIBUTING.md`)
+- You have checked the [GitHub Discussions Q&A section](https://github.com/alshedivat/al-folio/discussions/categories/q-a) for similar questions
+- You have searched existing [GitHub Issues](https://github.com/alshedivat/al-folio/issues)
+
+### What they do
+
+**Code Wiki** (powered by Google Gemini) generates interactive documentation from your repository code. It allows you to:
+
+- Browse your repository's structure and architecture
+- Search for specific functions or modules
+- Understand how different parts of the codebase work together
+- Get diagrams and visual representations of your code architecture
+
+**DeepWiki** provides an AI-powered interface to ask questions about a repository, similar to having an engineer available 24/7. It allows you to:
+
+- Ask natural language questions about the codebase
+- Get instant answers about how specific features work
+- Search for code patterns and implementations
+
+### Limitations
+
+These tools are generated automatically from our code and may not always reflect the most current documentation standards or best practices specific to this project. They should not replace official documentation but rather complement it when you need deeper technical insights.
+
+### Access these tools
+
+- **Code Wiki**: [Code Wiki for al-folio](https://codewiki.google/github.com/alshedivat/al-folio)
+- **DeepWiki**: [DeepWiki for al-folio](https://deepwiki.com/alshedivat/al-folio)

README.md

@@ -20,6 +20,9 @@
 [![GitHub stars](https://img.shields.io/github/stars/alshedivat/al-folio)](https://github.com/alshedivat/al-folio/stargazers)
 [![GitHub forks](https://img.shields.io/github/forks/alshedivat/al-folio)](https://github.com/alshedivat/al-folio/fork)
 
+[![Code Wiki](https://img.shields.io/badge/Code_Wiki-ask_about_repo-blue?logo=googlegemini)](https://codewiki.google/github.com/alshedivat/al-folio)
+[![DeepWiki](https://img.shields.io/badge/DeepWiki-ask_about_repo-lightcyan)](https://deepwiki.com/alshedivat/al-folio)
+
 </div>
 
 ## User community
@@ -246,6 +249,7 @@ Run the test yourself: [Google Lighthouse PageSpeed Insights](https://pagespeed.
   - [Getting started](#getting-started)
   - [Installing and Deploying](#installing-and-deploying)
   - [Customizing](#customizing)
+  - [GitHub Copilot Agents](#github-copilot-agents)
   - [Features](#features)
     - [Light/Dark Mode](#lightdark-mode)
     - [CV](#cv)
@@ -283,6 +287,34 @@ For installation and deployment details please refer to [INSTALL.md](INSTALL.md)
 
 For customization details please refer to [CUSTOMIZE.md](CUSTOMIZE.md).
 
+## GitHub Copilot Agents
+
+This repository includes two specialized GitHub Copilot agents to enhance your development experience:
+
+### Customization Agent
+
+The **Customization Agent** helps you personalize your al-folio website by:
+
+- Guiding you through configuration changes step-by-step
+- Modifying files directly in your repository
+- Explaining technical concepts in plain language (great for users without coding experience)
+- Assisting with common tasks like updating your CV, adding publications, creating blog posts, and customizing themes
+
+See [CUSTOMIZE.md § GitHub Copilot Customization Agent](CUSTOMIZE.md#github-copilot-customization-agent) for detailed usage instructions.
+
+### Documentation Agent
+
+The **Documentation Agent** maintains clear and up-to-date project documentation by:
+
+- Updating documentation files when features change
+- Writing in a style accessible to academics and researchers
+- Keeping documentation synchronized with the codebase
+- Following documentation best practices
+
+See [CONTRIBUTING.md § GitHub Copilot Agents](CONTRIBUTING.md#github-copilot-agents) for more information.
+
+> **Requirements:** Both agents require a [GitHub Copilot](https://github.com/features/copilot) subscription. For more information about GitHub Copilot and how to use agents, see the [GitHub Copilot documentation](https://docs.github.com/en/copilot).
+
 ## Features
 
 ### Light/Dark Mode