Thanks for showing interest in contributing!
The following is a set of guidelines for contributing to BigCommerce's Developer Documentation. These are guidelines, not rules. Use your best judgment, and make proposed changes to this document in a pull request.
The easiest way to edit a file is using GitHub's web interface:
-
Navigate to the file in GitHub. For example, making-requests.md.
-
Click the pencil icon to Edit This File.
-
Make the edit.
-
Type a commit message.
-
Select Create a new branch for this commit and start a pull request.
-
Give the branch a descriptive name.
-
Click Propose file change.
-
Give the pull request a descriptive title.
-
Fill in the pull request description.
-
Click Create pull request.
That's it! You're done.
For more complex changes, fork and edit locally:
-
Fork
bigcommerce/dev-docs
. -
git clone
the fork to your local machine. -
Make edits on a new branch in your IDE of choice.
-
Commit and push changes to your remote repo.
-
Create a pull request to
bigcommerce:dev-docs/main
.
- Always include subject; include body when necessary.
- Use present tense ("Add feature" not "Added feature").
- Use imperative mood ("Fix broken link..." not "Fixes broken link...").
- Separate subject from body with a blank line.
- Limit the subject line to 50 characters.
- Capitalize the subject line.
- Do not end the subject line with a period.
- Use the body to explain what and why versus how.
There are many other public BigCommerce repositories accepting contributions. If you're interested in contributing to those projects, see the full list of public source repos. Also, consider joining the BigCommerce Developer Community.