Skip to content

Commit a035aff

Browse files
chengjiahao1234chengjiahao1234
committed
initial commit
0 parents  commit a035aff

File tree

124 files changed

+9940
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

124 files changed

+9940
-0
lines changed

‎.editorconfig‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
#==============================================================================
2+
# EditorConfig (.editorconfig)
3+
#
4+
# Purpose:
5+
# Defines coding style conventions for editors and IDEs.
6+
# Maintains consistent formatting across different editors.
7+
#
8+
# Settings:
9+
# - 2-space indentation for all files
10+
# - LF line endings (Unix-style)
11+
# - UTF-8 character encoding
12+
# - Trim trailing whitespace (except Markdown)
13+
# - No final newline
14+
#
15+
# Support:
16+
# Works with VS Code, Sublime Text, Vim, IntelliJ, Atom, etc.
17+
# Requires EditorConfig plugin in most editors.
18+
#
19+
# Documentation:
20+
# https://editorconfig.org
21+
#==============================================================================
22+
23+
# editorconfig.org
24+
root = true
25+
26+
[*]
27+
indent_style = space
28+
indent_size = 2
29+
end_of_line = lf
30+
charset = utf-8
31+
trim_trailing_whitespace = true
32+
insert_final_newline = false
33+
34+
[*.md]
35+
trim_trailing_whitespace = false

‎.gitattributes‎

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
#==============================================================================
2+
# Git Attributes (.gitattributes)
3+
#
4+
# Purpose:
5+
# Defines attributes for Git to handle files correctly.
6+
# Controls language detection, line endings, and merge strategies.
7+
#
8+
# Settings:
9+
# - Mark vendor/plugin files as linguist-vendored (excluded from stats)
10+
# - Use union merge for CHANGELOG.md and history files
11+
# - Treat .md files as text
12+
#
13+
# Documentation:
14+
# https://git-scm.com/docs/gitattributes
15+
#==============================================================================
16+
17+
assets/fonts/* linguist-vendored
18+
assets/js/main.min.js linguist-vendored
19+
assets/js/lunr/* linguist-vendored
20+
assets/js/plugins/* linguist-vendored
21+
assets/js/vendor/* linguist-vendored
22+
_sass/minimal-mistakes/vendor/* linguist-vendored
23+
CHANGELOG.md text merge=union
24+
docs/_docs/18-history.md text merge=union
25+
26+
*.md text

‎.github/CONTRIBUTING.md‎

Lines changed: 90 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,90 @@
1+
# Contributing to Atlas Analytics Lab Website
2+
3+
Thank you for your interest in contributing to the Atlas Analytics Lab website!
4+
5+
## For Lab Members
6+
7+
If you're a lab member looking to update content (news, publications, team info), please see:
8+
- **Quick Guide:** [README.md](../README.md)
9+
- **Detailed Instructions:** [DEVELOPMENT.md](../DEVELOPMENT.md) - Git Workflow section
10+
11+
## Reporting Issues
12+
13+
Found a bug, typo, or have a suggestion?
14+
15+
1. Check [existing issues](https://github.com/AtlasAnalyticsLab/AtlasAnalyticsLab.github.io/issues) first
16+
2. If it's new, [create an issue](https://github.com/AtlasAnalyticsLab/AtlasAnalyticsLab.github.io/issues/new)
17+
3. Provide as much detail as possible:
18+
- What page or section is affected?
19+
- What did you expect vs. what happened?
20+
- Screenshots if applicable
21+
22+
## Submitting Pull Requests
23+
24+
### Content Updates (News, Publications, Team)
25+
26+
1. **Create a feature branch** from `main`:
27+
```bash
28+
git checkout main
29+
git pull origin main
30+
git checkout -b feature/add-news-YYYY-MM-DD
31+
```
32+
33+
2. **Make your changes:**
34+
- Edit `_data/news.yml` for news
35+
- Edit `_data/publications.yml` for publications
36+
- Edit `_data/[role].yml` for team members
37+
- Add images to appropriate `images/` subdirectory
38+
39+
3. **Test locally:**
40+
```bash
41+
bundle exec jekyll serve --livereload
42+
# Visit http://127.0.0.1:4000
43+
```
44+
45+
4. **Commit with descriptive message:**
46+
```bash
47+
git add .
48+
git commit -m "content: add news about [topic]"
49+
git push origin feature/add-news-YYYY-MM-DD
50+
```
51+
52+
5. **Open a pull request** on GitHub
53+
54+
### Code/Layout Changes
55+
56+
1. **Follow the same branch workflow** above
57+
2. **Test thoroughly** on different screen sizes and both themes (light/dark)
58+
3. **Update documentation** if you change structure or add features
59+
4. **Use semantic commit messages:**
60+
- `feat:` - New features
61+
- `fix:` - Bug fixes
62+
- `style:` - CSS/styling changes
63+
- `refactor:` - Code restructuring
64+
- `docs:` - Documentation updates
65+
- `chore:` - Maintenance tasks
66+
67+
### Code Standards
68+
69+
- **Indentation:** 2 spaces (HTML, CSS, JavaScript)
70+
- **Comments:** Follow standards in [DEVELOPMENT.md](../DEVELOPMENT.md)
71+
- **File headers:** Add descriptive headers to new files
72+
- **Test locally:** Always test before pushing
73+
74+
## Review Process
75+
76+
- All PRs require review before merging
77+
- Content updates: Quick review by Dr. Hosseini or designated team member
78+
- Code changes: More thorough review for functionality and style
79+
- Address review comments promptly
80+
- Squash commits if requested
81+
82+
## Questions?
83+
84+
For help:
85+
- **Jekyll/Technical:** [Jekyll Documentation](https://jekyllrb.com/docs/) or [Jekyll Talk Forums](https://talk.jekyllrb.com/)
86+
- **Lab Website:** Open an issue or contact Dr. Mahdi S. Hosseini at mahdi.hosseini@concordia.ca
87+
88+
## License
89+
90+
By contributing, you agree that your contributions will be licensed under the MIT License.

‎.github/ISSUE_TEMPLATE/bug_report.yml‎

Lines changed: 73 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,73 @@
1+
name: Bug Report
2+
description: Report a problem with the Atlas Analytics Lab website
3+
body:
4+
- type: markdown
5+
attributes:
6+
value: |
7+
Before opening a bug report, please:
8+
9+
- Check [existing issues](https://github.com/AtlasAnalyticsLab/AtlasAnalyticsLab.github.io/issues)
10+
to avoid duplicates
11+
- Try running `bundle exec jekyll clean` and `bundle exec jekyll serve` to see
12+
if the issue persists
13+
- Check the documentation at [README.md](../../README.md) and
14+
[DEVELOPMENT.md](../../DEVELOPMENT.md)
15+
16+
If the issue still occurs, please continue below.
17+
18+
- type: textarea
19+
id: environment
20+
attributes:
21+
label: Environment Information
22+
description: |
23+
Please provide details about your environment. This helps us reproduce and fix the issue.
24+
value: |-
25+
- Jekyll version: (run `bundle exec jekyll --version`)
26+
- Ruby version: (run `ruby --version`)
27+
- Operating system: (e.g., macOS 14, Ubuntu 22.04, Windows 11)
28+
- Browser: (e.g., Chrome 120, Safari 17, Firefox 121)
29+
- URL where issue occurs: (e.g., homepage, /publications, /team)
30+
validations:
31+
required: true
32+
33+
- type: textarea
34+
id: expected-behavior
35+
attributes:
36+
label: Expected behavior
37+
description: |
38+
Please describe the expected behavior and the actual result you got.
39+
placeholder: >
40+
What is it you expected to happen? This should be a description of how the
41+
functionality you tried to use is supposed to work.
42+
validations:
43+
required: true
44+
45+
- type: textarea
46+
id: steps-to-reproduce
47+
attributes:
48+
label: Steps to reproduce the behavior
49+
description: |
50+
Describe the steps you took for this problem to come up. Such as: you installed
51+
the theme, customized _config.yml, added your own posts, and started up a
52+
Jekyll server locally.
53+
54+
If an error occurred on GitHub Pages when pushing, please test a local version
55+
following these setup instructions:
56+
https://help.github.com/articles/setting-up-your-github-pages-site-locally-with-jekyll/
57+
58+
Then provide a complete log by running `bundle exec jekyll build --trace --verbose`
59+
and include this output in the filed issue.
60+
61+
Screenshots can also be included if they help illustrate a behavior.
62+
validations:
63+
required: true
64+
65+
- type: textarea
66+
id: other
67+
attributes:
68+
label: Other
69+
description: |
70+
Please provide a code repository, gist, code snippet, sample files,
71+
screenshots, or anything else you think will aid in reproducing the issue.
72+
validations:
73+
required: false

‎.github/ISSUE_TEMPLATE/config.yml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: 📚 Documentation
4+
url: https://github.com/AtlasAnalyticsLab/AtlasAnalyticsLab.github.io/blob/main/README.md
5+
about: Check the README for quick start and common tasks
6+
- name: 👨‍💻 Development Guide
7+
url: https://github.com/AtlasAnalyticsLab/AtlasAnalyticsLab.github.io/blob/main/DEVELOPMENT.md
8+
about: Full development documentation and workflow guide
9+
- name: 💬 Jekyll Support
10+
url: https://talk.jekyllrb.com/
11+
about: General Jekyll questions and support

‎.github/ISSUE_TEMPLATE/documentation.yml‎

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
name: Documentation Update
2+
description: Found a typo, unclear instructions, or something that needs clarification?
3+
body:
4+
- type: markdown
5+
attributes:
6+
value: |-
7+
Thanks for helping improve our documentation!
8+
9+
This template is for issues with README.md, DEVELOPMENT.md, or website content.
10+
11+
- type: dropdown
12+
id: doc-type
13+
attributes:
14+
label: Documentation Type
15+
description: Which documentation needs updating?
16+
options:
17+
- README.md (quick start guide)
18+
- DEVELOPMENT.md (developer documentation)
19+
- Website content (text on pages)
20+
- Instructions_members.md
21+
- CONTRIBUTING.md
22+
- Other
23+
validations:
24+
required: true
25+
26+
- type: textarea
27+
id: issue
28+
attributes:
29+
label: What's the problem?
30+
description: |-
31+
What is incorrect, unclear, or missing?
32+
placeholder: |-
33+
Example: "The instructions for adding news items don't mention that items should be added to the TOP of the file"
34+
validations:
35+
required: true
36+
37+
- type: textarea
38+
id: suggestion
39+
attributes:
40+
label: Suggested improvement
41+
description: |-
42+
How should we fix or improve this?
43+
placeholder: |-
44+
Example: "Add a note that says 'Add new items to the TOP of the file' in step 1"
45+
validations:
46+
required: true
47+
48+
- type: textarea
49+
id: location
50+
attributes:
51+
label: Location
52+
description: |-
53+
Where is this in the documentation? (file name, section, line number if known)
54+
placeholder: |-
55+
Example: "README.md, section 'Updating Content > News & Announcements'"
56+
validations:
57+
required: false

0 commit comments

Comments
 (0)