This website is built using Docusaurus, a modern static website generator.
The site may be previewed at llm-d.github.io before it goes live
If you spot any errors or ommisions in the site, please open an issue at github.com/llm-d/llm-d.github.io
- Make sure you are familiar with how docusaurus builds menus and links to images
- Make sure there are no relative links to any of the llm-d component repositories in your markdown.
- Fork the website repo and deploy a preview version of your proposed change for reviewers to check. This will make obvious any missed links from step 2
$ npm install
$ npm start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
-
Fork the Repository
- Click the "Fork" button on the llm-d.github.io repository
- Clone your fork locally:
git clone https://github.com/YOUR-USERNAME/llm-d.github.io.git
-
Create a Branch
- Create a new branch for your changes:
git checkout -b feature/your-feature-name
- Make your changes locally
- Create a new branch for your changes:
-
Commit Your Changes
- Stage your changes:
git add .
- Commit with sign-off:
git commit -s -m "Your commit message"
- Push to your fork:
git push origin feature/your-feature-name
- Stage your changes:
-
Open a Pull Request
- Go to your fork on GitHub
- Click "New Pull Request"
- Select the main branch of llm-d/llm-d.github.io as the base
- Fill out the pull request template with details about your changes
When you open a pull request, a preview of your changes will be automatically generated and deployed. This allows reviewers to see your changes in a live environment before they are merged into the main website.
- The preview URL will be posted as a comment on your pull request
- The preview site will be automatically updated as you push new commits
- The preview will be removed when the pull request is closed
- All code changes must be submitted as pull requests (no direct pushes)
- All changes must be reviewed and approved by a maintainer
- All changes must pass automated checks and tests
- Commit messages should have:
- Short, descriptive titles
- Description of why the change was needed
- Enough detail for someone reviewing git history to understand the scope
- DCO Sign-off: All commits must include a valid DCO sign-off line (
Signed-off-by: Name <[email protected]>
)- Add automatically with
git commit -s
- See PR_SIGNOFF.md for configuration details
- Required for all contributions per Developer Certificate of Origin
- Add automatically with
- For immediate help: Join llm-d.slack.com -> Invite Link
- For issues: Create an issue in llm-d/llm-d.github.io