Using Sandbox Without Rake

Basic Setup

Direct Jekyll Usage

# Start development server
bundle exec jekyll serve --livereload --livereload-min-delay 5

# Build for production
JEKYLL_ENV=production bundle exec jekyll build

Prerequisites

# Install Ruby dependencies
gem install bundler

# Install project dependencies
bundle install

Built-in Features

Sass Processing

# _config.yml
sass:
  style: compressed
  sass_dir: _sass
  sourcemap: never

Image Processing

Manual Image Optimization

# Convert single image
magick convert input.webp -quality 90 output.webp

# Batch convert (PowerShell)
Get-ChildItem -Path "assets/img" -Recurse -Include *.webp,*.webp | 
ForEach-Object { magick convert $_.FullName -quality 90 "$($_.DirectoryName)\$($_.BaseName).webp" }

# Batch convert (Bash/Linux)
find assets/img -type f \( -iname "*.webp" -o -iname "*.webp" \) -exec convert {} -quality 90 {}.webp \;

Development Workflow

Recommended Steps

Development workflow without Rake:

1. Start Jekyll server: bundle exec jekyll serve --livereload
2. Make changes to source files (Sass compiles automatically)
3. Process images manually as needed
4. Build for production: JEKYLL_ENV=production bundle exec jekyll build

Troubleshooting

Common Issues

Solutions for frequent problems:

• Sass Compilation Errors: Check _sass directory structure
• Server Start Issues: Verify port availability
• Build Failures: Check Jekyll environment settings
• Image Processing: Confirm ImageMagick installation

Debugging

Debug Jekyll processes:

• Use verbose mode: jekyll serve --verbose
• Check build output in _site directory
• Enable trace mode with --trace
• Review Jekyll’s error messages

Shell Scripts

Automation Scripts

#!/bin/bash
# build.sh - Production build script

echo "Building site for production..."
JEKYLL_ENV=production bundle exec jekyll build

echo "Processing images..."
find assets/img -type f \( -iname "*.webp" -o -iname "*.webp" \) -exec convert {} -quality 90 {}.webp \;