AGENTS.md

Agent guidance for wrocnet.org (Jekyll + Minimal Mistakes).

Purpose

• Keep changes small, content-safe, and compatible with the current Jekyll site structure.
• Prefer updating existing files and patterns over introducing new architecture.

First Read

• Main project guide: README.md
• Jekyll config and site defaults: _config.yml
• CI validation pipeline: .github/workflows/validate.yml
• YAML lint rules: .yamllint
• Navigation/content data: _data/navigation.yml, _data/schedule.yml, _data/organizers.yml

Core Commands

Run from repository root.

1. Install dependencies
   • bundle install
2. Local dev server
   • bundle exec jekyll serve –livereload
3. YAML lint (same scope as CI)
   • yamllint -c .yamllint _data _config.yml
4. Strict build
   • bundle exec jekyll build –strict_front_matter
5. HTML/internal link checks
   • bundle exec htmlproofer ./_site –disable-external –no-enforce-https

Repository Conventions

• Site uses remote theme mmistakes/minimal-mistakes@4.28.0 and custom skin wrocnet.
• No custom _layouts directory: rely on theme layouts and local overrides in _includes.
• Post files live in _posts and follow naming pattern:
  • YYYY-MM-DD-NR-spotkanie-wroclawskiej-grupy-net.md
• Default post category is spotkania via _config.yml defaults.
• Main pages are in _pages, data-driven content is in _data.
• Default branch is main.
• Do not commit directly to main: create a topic branch for each task and merge via Pull Request.

Known Pitfalls

• Keep aligned colons in _data/ui-text.yml. The lint config intentionally allows extra spaces before colons.
• If adding links/images in old posts, avoid empty markdown links and missing local assets because htmlproofer runs in CI.
• Prefer preserving Polish content style and existing URL/permalink patterns.
• Images/Photos: Do not use external URLs for profile photos. Download the image to assets/images/organizers/, ensure it’s in JPG/PNG format, and resize it to a reasonable size (e.g., 400x400px) before committing.

Change Strategy For Agents

• Link, do not duplicate: if details exist in README or workflow files, reference them.
• Verify with lint/build/proofer when changing content, data files, or templates.
• Avoid broad formatting rewrites in historical posts unless explicitly requested.
• Keep includes and data schema changes backward-compatible with existing pages.

Where To Start For Typical Tasks

• Add/update meeting post: _posts + optional assets under assets/images or slides.
• Update organizer or schedule info: files in _data and related page under _pages.
• Navigation or labels: _data/navigation.yml and _data/ui-text.yml.
• Theme/header behavior: _includes and _sass/minimal-mistakes/skins/_wrocnet.scss.