Repository Guidelines

Project Structure & Module Organization

• Jekyll site configuration lives in _config.yml.
• Page content is authored in index.md and the _sites/ collection (e.g., _sites/team.md, _sites/publications/).
• Shared layouts and partials are in _layouts/ and _includes/.
• Styles are in _sass/ with the compiled entrypoint in assets/css/style.scss.
• Static assets (images, icons, SVGs) are under assets/.
• _site/ contains generated output; do not edit it directly.

Build, Test, and Development Commands

• bundle exec jekyll serve: run the local development server and rebuild on change.
• bundle update: update Ruby gem dependencies in Gemfile.lock.

Coding Style & Naming Conventions

• Follow existing formatting in each file; SCSS and HTML use spaces and consistent alignment.
• Keep Markdown front matter in YAML at the top of content files.
• Prefer descriptive, kebab-case filenames for new pages (e.g., _sites/new-section.md).
• Keep inline HTML minimal and consistent with existing patterns in index.md and _includes/.

Testing Guidelines

• No automated test suite is configured in this repository.
• Validate changes by running bundle exec jekyll serve and checking the relevant pages in the browser.

Commit & Pull Request Guidelines

• Commit history uses short, lowercase, imperative messages like update or update team.
• No PR template is defined; include a brief summary and screenshots for visible UI changes.
• Link related issues if they exist and note any content or asset updates explicitly.

Security & Configuration Tips

• Avoid committing secrets; this is a static site with no server-side runtime.
• When adding analytics or embeds, document them in README.md or legal.md as appropriate.