Skip to content

Commit 3d633a1

Browse files
committed
Create AGENTS.md
1 parent 02a44b7 commit 3d633a1

File tree

1 file changed

+49
-0
lines changed

1 file changed

+49
-0
lines changed

AGENTS.md

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
# Repository Guidelines
2+
3+
## Project Structure & Module Organization
4+
- `index.html`: Site entry point.
5+
- `_config.yml`: Jekyll configuration (site, collections, plugins).
6+
- `_layouts/` and `_includes/`: HTML/Liquid templates and partials.
7+
- `_team/`: Team member Markdown files with front matter (collection).
8+
- `images/`, `css/`, `js/`: Static assets.
9+
- `_site/`: Generated output. Do not edit by hand.
10+
11+
## Build, Test, and Development Commands
12+
- `bundle install`: Install Ruby gems per `Gemfile`.
13+
- `bundle exec jekyll serve --livereload`: Run local dev server at `http://127.0.0.1:4000`.
14+
- `bundle exec jekyll build`: Build the site into `_site/`.
15+
- `JEKYLL_ENV=production bundle exec jekyll build`: Production build.
16+
- `bundle exec jekyll doctor`: Check for common configuration issues.
17+
18+
## Coding Style & Naming Conventions
19+
- Indentation: 2 spaces for HTML/Liquid, YAML, CSS, and JS.
20+
- Filenames: kebab-case (e.g., `team-member.html`, `jiayu-zhou.md`).
21+
- Liquid: Keep logic in layouts/includes; keep pages mostly declarative.
22+
- Assets: Place images under `images/` and reference with absolute paths (e.g., `/images/...`).
23+
- Team entries: `_team/*.md` with front matter:
24+
```yaml
25+
---
26+
layout: team-member
27+
name: Full Name
28+
title: Role
29+
picture: /images/profile/name.jpg
30+
email: user@example.com
31+
category: 0
32+
---
33+
Brief bio or links.
34+
```
35+
36+
## Testing Guidelines
37+
- Local verification: Build and browse key pages; check nav, links, and images.
38+
- Link/config checks: Run `bundle exec jekyll doctor`.
39+
- Optional: Open dev tools console to catch JS/CSS errors.
40+
41+
## Commit & Pull Request Guidelines
42+
- Commits: Present tense, concise summary (e.g., "Update news", "Fix typo"). Group related changes.
43+
- Do not edit `_site/` directly; changes should originate from sources.
44+
- PRs: Include a clear description, before/after screenshots for visual changes, and reference related issues.
45+
- Verify locally (`jekyll serve`) and ensure no broken links/images before requesting review.
46+
47+
## Security & Configuration Tips
48+
- Review `_config.yml` changes carefully; they affect site-wide behavior.
49+
- Avoid committing secrets or API keys; this site is static and should not require them.

0 commit comments

Comments
 (0)