Fix Jekyll build task with robust fallback mechanism

[Copilot]

Problem

The Jekyll build task (build.sh) was failing with a gem dependency error:

Could not find base64-0.2.0 in any of the sources (Bundler::GemNotFound)

This was caused by the Jekyll Docker image version 3.8 being outdated and incompatible with the current gem dependencies in Gemfile.lock. The base64 gem is a newer dependency that wasn't present in older Ruby/Jekyll versions, causing the Docker-based build to fail consistently.

Solution

Implemented a robust fallback mechanism that preserves the original Docker-first approach while ensuring builds always succeed:

1. Enhanced Build Scripts

• build.sh: Now attempts Docker build first, then automatically falls back to local Ruby/Bundle if Docker fails
• watch.sh: Updated with the same fallback mechanism for development server

2. Automatic Dependency Management

• Scripts detect if dependencies need installation and handle it automatically
• Clear error messages guide users when neither Docker nor Ruby is available

3. Comprehensive Documentation

• Added README.md with build instructions, troubleshooting guide, and multiple build options
• Documents both Docker and local Ruby approaches
• Explains common errors and their solutions

Technical Details

The fallback logic works as follows:

# Try Docker build first (preserves existing workflow)
if docker run jekyll/jekyll:3.8 jekyll build; then
  echo "Docker build successful!"
else
  # Fall back to local Ruby/Bundle
  bundle install && bundle exec jekyll build
fi

Benefits

• Zero breaking changes: Existing Docker workflows continue to work where compatible
• Universal compatibility: Builds succeed regardless of Docker image issues
• Developer-friendly: Clear error messages and automatic dependency resolution
• Future-proof: Resilient to future Jekyll/Docker version incompatibilities

Testing

Verified that:

• ✅ Build script works correctly with fallback mechanism
• ✅ Watch script provides development server with same reliability
• ✅ GitHub Actions workflow remains unaffected (uses Ruby directly)
• ✅ Generated site files are identical to previous working builds

The Jekyll build task now works reliably for all contributors regardless of their local environment setup.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.