Skip to content

Commit 0ad3695

Browse files
authored
Merge pull request elizaOS#3906 from elizaOS/jin-docs-march
chore: major docs cleanup
2 parents 132be32 + f5a57ec commit 0ad3695

File tree

726 files changed

+20935
-21860
lines changed

Some content is hidden

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

726 files changed

+20935
-21860
lines changed

.github/workflows/fetch-news.yml

+27
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
name: Fetch News Files
2+
3+
on:
4+
schedule:
5+
- cron: '0 0 * * *' # Run daily at midnight UTC
6+
workflow_dispatch: # Allow manual triggering
7+
8+
jobs:
9+
fetch-news:
10+
runs-on: ubuntu-latest
11+
steps:
12+
- name: Checkout repository
13+
uses: actions/checkout@v4
14+
with:
15+
ref: autodocs
16+
17+
- name: Run news fetcher
18+
run: |
19+
chmod +x docs/scripts/fetch-news.sh
20+
./docs/scripts/fetch-news.sh
21+
22+
- name: Commit and push if changes exist
23+
run: |
24+
git config --global user.name 'GitHub Actions Bot'
25+
git config --global user.email 'github-actions[bot]@users.noreply.github.com'
26+
git add docs/news/
27+
git diff --quiet && git diff --staged --quiet || (git commit -m "Auto-update news files" && git push origin autodocs)
+48-28
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,50 @@
1-
name: Generate Changelog
1+
name: Update Changelog
2+
23
on:
3-
push:
4-
tags:
5-
- "*"
4+
release:
5+
types: [published]
6+
67
jobs:
7-
changelog:
8-
runs-on: ubuntu-latest
9-
permissions:
10-
contents: write
11-
steps:
12-
- uses: actions/checkout@v4
13-
with:
14-
ref: main
15-
token: ${{ secrets.CHANGELOG_GITHUB_TOKEN }}
16-
- name: Generate Changelog
17-
run: |
18-
export PATH="$PATH:/home/runner/.local/share/gem/ruby/3.0.0/bin"
19-
gem install --user-install github_changelog_generator
20-
github_changelog_generator \
21-
-u ${{ github.repository_owner }} \
22-
-p ${{ github.event.repository.name }} \
23-
--token ${{ secrets.CHANGELOG_GITHUB_TOKEN }}
24-
- name: Commit Changelog
25-
uses: stefanzweifel/git-auto-commit-action@v5
26-
with:
27-
commit_message: "chore: update changelog"
28-
branch: main
29-
file_pattern: "CHANGELOG.md"
30-
commit_author: "GitHub Action <actions@github.com>"
8+
update_changelog:
9+
runs-on: ubuntu-latest
10+
permissions:
11+
contents: write
12+
pull-requests: write
13+
14+
steps:
15+
- name: Checkout repository
16+
uses: actions/checkout@v4
17+
18+
- name: Set up Python
19+
uses: actions/setup-python@v5
20+
with:
21+
python-version: '3.x'
22+
23+
- name: Configure Git
24+
run: |
25+
git config user.name "GitHub Actions"
26+
git config user.email "actions@github.com"
27+
28+
- name: Check if autodocs branch exists and create or switch to it
29+
run: |
30+
if git ls-remote --heads origin autodocs | grep autodocs; then
31+
echo "Branch autodocs exists, checking out"
32+
git checkout autodocs
33+
git pull origin autodocs
34+
else
35+
echo "Branch autodocs doesn't exist, creating"
36+
git checkout -b autodocs
37+
fi
38+
39+
- name: Generate changelog
40+
run: python3 docs/scripts/get-changelog.py --output docs/docs/changelog.md
41+
env:
42+
GITHUB_TOKEN: ${{ secrets.CHANGELOG_GITHUB_TOKEN }}
43+
44+
- name: Commit and push changes
45+
run: |
46+
git add docs/changelog.md
47+
git commit -m "docs: update changelog for ${{ github.event.release.tag_name }}" || echo "No changes to commit"
48+
git push origin autodocs
49+
env:
50+
GITHUB_TOKEN: ${{ secrets.CHANGELOG_GITHUB_TOKEN }}

CONTRIBUTING.md

+62-6
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
1-
# Contributing to Eliza
1+
# Contributing to eliza
22

3-
First off, thank you for considering contributing to Eliza! We welcome contributions from everyone, regardless of experience level.
3+
First off, thank you for considering contributing to eliza! We welcome contributions from everyone, regardless of experience level.
44

55
## Contribution License Agreement
66

7-
By contributing to Eliza, you agree that your contributions will be licensed under the MIT License. This means:
7+
By contributing to eliza, you agree that your contributions will be licensed under the MIT License. This means:
88

99
1. You grant us (and everyone else) a perpetual, worldwide, non-exclusive, royalty-free license to use your contributions.
1010
2. Your contributions are and will be available as Free and Open Source Software (FOSS).
@@ -20,11 +20,13 @@ We believe in the power of the OODA Loop - a decision-making framework that emph
2020
- **Decide**: Choose a course of action based on your analysis. This could be proposing a new feature, fixing a bug, or creating content.
2121
- **Act**: Execute your decision and share your work with the community.
2222

23+
---
24+
2325
## How to Contribute
2426

2527
### For Developers
2628

27-
1. **Extend Eliza's Capabilities**
29+
1. **Extend eliza's Capabilities**
2830

2931
- Develop new actions, evaluators, and providers
3032
- Improve existing components and modules
@@ -44,6 +46,60 @@ We believe in the power of the OODA Loop - a decision-making framework that emph
4446
6. Make sure your code lints.
4547
7. Issue that pull request!
4648

49+
### For Designers
50+
51+
1. **Improve User Experience**
52+
53+
- Conduct user research and usability testing
54+
- Design intuitive user interfaces and interactions
55+
- Create high-fidelity mockups and prototypes
56+
57+
2. **Enhance Visual Design**
58+
- Develop a consistent visual language and style guide
59+
- Create engaging illustrations, icons, and graphics
60+
- Optimize designs for accessibility and inclusivity
61+
62+
### For Writers and Storytellers
63+
64+
1. **Craft Compelling Narratives**
65+
66+
- Write blog posts, articles, and stories that communicate our vision
67+
- Develop characters and scenarios that showcase the potential of AI agents
68+
- Collaborate with artists to create immersive, multimedia experiences
69+
70+
2. **Improve Documentation**
71+
- Write clear, concise, and accessible documentation
72+
- Create tutorials, guides, and FAQs to help users get started
73+
- Provide examples and use cases to demonstrate eliza's capabilities
74+
75+
### For Artists and Creators
76+
77+
1. **Illustrate the Future**
78+
79+
- Create concept art, illustrations, and infographics that bring our vision to life
80+
- Design characters, avatars, and virtual environments for AI agents
81+
- Experiment with new mediums and formats to communicate ideas
82+
83+
2. **Produce Multimedia Content**
84+
- Create videos, animations, and interactive experiences
85+
- Develop podcasts, interviews, and audio content
86+
- Collaborate with writers and developers to create integrated campaigns
87+
88+
### For Community Builders
89+
90+
1. **Foster Engagement**
91+
92+
- Moderate forums, chat rooms, and social media channels
93+
- Organize events, meetups, and hackathons
94+
- Facilitate discussions and collaborations among contributors
95+
96+
2. **Provide Support**
97+
- Answer questions and provide guidance to new contributors
98+
- Triage issues and help prioritize bug fixes and feature requests
99+
- Act as a liaison between the community and the core development team
100+
101+
---
102+
47103
## Styleguides
48104

49105
### Git Commit Messages
@@ -90,7 +146,7 @@ This section lists the labels we use to help us track and manage issues and pull
90146

91147
## Contributor Guide
92148

93-
Welcome to the Eliza contributor guide! This document is designed to help you understand how you can be part of building the future of autonomous AI agents, regardless of your technical background.
149+
Welcome to the eliza contributor guide! This document is designed to help you understand how you can be part of building the future of autonomous AI agents, regardless of your technical background.
94150

95151
### Code of Conduct
96152

@@ -126,4 +182,4 @@ Project maintainers have the right and responsibility to remove, edit, or reject
126182

127183
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
128184

129-
Thank you for contributing to Eliza and helping build the future of autonomous AI agents! 🎉
185+
Thank you for contributing to eliza and helping build the future of autonomous AI agents! 🎉

docs/blog/eliza-february-2025-recap.md

-103
This file was deleted.

0 commit comments

Comments
 (0)