This guide shows you how to contribute to the ELIXIR Training SPLASH website using GitHub. Choose the workflow that suits your experience level.
Prerequisites
Create a free GitHub account if you don’t have one already.
Contributing via web browser
Perfect if you’re new to Git/GitHub or want to make changes without installing software.
1. Discuss your proposal
Before making changes, create or find a relevant issue:
- Visit the ELIXIR Training SPLASH repository
- Search existing issues to avoid duplicates
- Create a new issue if needed (use one of our templates)
- Discuss your idea with editors in the issue comments
Learn more: GitHub’s guide to creating issues
2. Fork the repository
Create your own copy of the repository:
- Go to the ELIXIR Training SPLASH repository
- Click the Fork button in the top-right corner
- Select your account as the destination
- Wait for GitHub to create your fork
Your fork will be at https://github.com/YOUR-USERNAME/ELIXIR-Training-SPLASH
Learn more: Forking a repository
3. Make your changes
To edit an existing file:
- In your fork, navigate to the file you want to edit (e.g.,
pages/resources/) - Click the pencil icon (✏️ Edit this file) in the top-right
- Make your changes using Markdown
- Preview your changes using the “Preview” tab
To create a new resource:
- In your fork, go to
pages/resources/ - Click Add file → Create new file
- Copy content from
TEMPLATE_resource_page.md - Name your file (e.g.,
my-resource.md) - Fill in the template with your resource information
Formatting guidelines:
- Follow our style guide
- Check the page metadata guide for frontmatter
- See adding resources for resource-specific instructions
4. Commit your changes
- Scroll to the bottom of the edit page to “Commit changes”
- Select “Create a new branch for this commit and start a pull request”
- Give your branch a descriptive name (e.g.,
add-my-resource) - Write a brief commit message describing what you changed
- Click Propose changes
Learn more: Committing changes
5. Create a pull request
After proposing changes, you’ll be taken to the “Open a pull request” page:
- Write a clear title for your pull request
- In the description:
- Explain what you changed and why
- Link to the related issue by typing
#issue_number(e.g.,Fixes #123)
- Choose the pull request type:
- “Create draft pull request” - if you’re still working (can mark “Ready for review” later)
- “Create pull request” - if you’re ready for editor review
- Click the green button to create the pull request
Your pull request will appear at ELIXIR-Training-SPLASH/pulls
Learn more: Creating a pull request from a fork
6. Make additional changes (if needed)
If you need to update your pull request before or after review:
- Go to your fork:
https://github.com/YOUR-USERNAME/ELIXIR-Training-SPLASH - Switch to your branch using the branch dropdown
- Navigate to the file and click the pencil icon (✏️)
- Make your changes
- Commit directly to your branch (same branch name as before)
- Changes automatically appear in your pull request
7. Respond to review comments
When editors review your pull request:
- You’ll receive notifications about comments
- Read the feedback and respond to questions
- Make requested changes following step 6 above
- Reply to comments to let editors know you’ve addressed them
- Editors will mark conversations as “Resolved” when satisfied
Learn more: Commenting on pull requests
8. Merge and celebrate! 🎉
Once editors approve your changes:
- An editor will merge your pull request
- Your contributions will appear on the live website
- You’ll be listed as a contributor (if you added yourself to the metadata)
Git workflow
For contributors familiar with Git who want to work locally and preview changes.
Fork and clone
# Fork the repository via GitHub web interface first, then:
git clone https://github.com/YOUR-USERNAME/ELIXIR-Training-SPLASH.git
cd ELIXIR-Training-SPLASH
# Add upstream remote to sync with main repository
git remote add upstream https://github.com/elixir-europe-training/ELIXIR-Training-SPLASH.git
Keep your fork updated
# Sync your fork with the main repository before starting new work
git fetch upstream
git checkout main
git merge upstream/main
git push origin main
Create a feature branch
# Create and switch to a new branch for your changes
git checkout -b descriptive-feature-name
Make changes and commit
# Make your changes using your preferred editor
# Stage all changes
git add .
# Or stage specific files
git add path/to/file
# Commit with a descriptive message
git commit -m "Brief description of your changes"
Push and create pull request
# Push your branch to your fork
git push origin descriptive-feature-name
Then visit github.com/elixir-europe-training/ELIXIR-Training-SPLASH and click “Compare & pull request”.
Learn more: Creating a pull request from a fork
Preview changes locally
See our preview changes guide for instructions on running the website locally using Docker or Jekyll.
Need help?
- Check GitHub’s documentation
- Ask questions in your issue or pull request
- Contact the editorial team via training-splash@elixir-europe.org