AI Skill Report Card

Managing Jekyll Netlify

B+75·Jan 16, 2026

Jekyll + Netlify Development

Bash
# Start development server in Codespaces bundle exec jekyll serve --host 0.0.0.0 --port 4000

Navigate to the forwarded port 4000 to preview your site.

Recommendation
Add concrete debugging examples showing actual error messages and solutions (e.g., 'Build failed with exit code 127: Command not found: bundle' → solution: add Ruby buildpack)

Development Process:

  • Make changes to content or code
  • Test locally with bundle serve
  • Commit and push to trigger Netlify build
  • Verify deployment on Netlify dashboard

Initial Setup:

  1. Create netlify.toml in root:
TOML
[build] command = "bundle exec jekyll build" publish = "_site" [build.environment] JEKYLL_ENV = "production" RUBY_VERSION = "3.1"
  1. Configure Codespaces port forwarding for port 4000
  2. Connect repository to Netlify for automatic deployments
Recommendation
Include example directory structure and sample _config.yml settings specific to Netlify deployment requirements

Example 1 - Local Development: Input: Changes to _posts/2024-01-01-new-post.md Output:

Bash
bundle exec jekyll serve --host 0.0.0.0 --livereload # Site accessible at forwarded port, auto-refreshes on changes

Example 2 - Deploy Trigger: Input: git push origin main Output: Netlify automatically builds and deploys within 1-2 minutes

Recommendation
Provide specific Netlify dashboard screenshots or exact steps for connecting GitHub repository and configuring build settings
  • Use --host 0.0.0.0 for Codespaces compatibility
  • Pin Ruby version in netlify.toml to match Gemfile
  • Test builds locally before pushing with JEKYLL_ENV=production bundle exec jekyll build
  • Use branch deploys for testing: push feature branches for preview URLs
  • Set up Netlify Forms for contact forms (no backend needed)
  • Port not accessible: Ensure Codespaces port 4000 is set to "Public"
  • Build failures: Check Ruby version mismatch between local and Netlify
  • Missing gems: Run bundle install after pulling changes
  • Path issues: Use {{ site.baseurl }} for assets in production
  • Cache problems: Clear Netlify cache if builds seem stale
0
Grade B+AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
11/15
Workflow
11/15
Examples
15/20
Completeness
15/20
Format
11/15
Conciseness
11/15