Skip to content

Latest commit

 

History

History
174 lines (108 loc) · 7.07 KB

CONTRIBUTING.md

File metadata and controls

174 lines (108 loc) · 7.07 KB
Raw

Contributing to OpenSauced Guestbook

This Contributing Guide will walk you through how to contribute to this project for bug fixes and features. If you want to contribute to the guestbook, please refer to chapter five of the Intro to Open Source course.

Contributions are always welcome, no matter how large or small. Before you begin, please read our Code of Conduct and follow the directions below:

Recommended Communication Style

  1. Always leave screenshots for visual changes.
  2. Always leave a detailed description in the Pull Request. Leave nothing ambiguous for the reviewer(s).
  3. Always review your code first. Be sure to run the project locally and test it before asking for a review.
  4. Always communicate in the GitHub repository. Whether it is in the issue or the pull request, keeping the lines of communication open and visible to everyone on the team helps everyone around you.

Issues

If you wish to work on an open issue, please comment on the issue with .take and it will be assigned to you. If an issue is not assigned, it is assumed to be open for anyone to work on. Please assign yourself to an issue before beginning work on it to avoid conflicts.

If you are contributing to the project for the first time, please consider checking the bug or good first issue labels.

In case you get stuck, please feel free to ask for help in the Intro to Contributing discussion.

Setup the Project Locally

  1. Fork the guestbook repository you are working on to your own GitHub account.

  2. Clone the forked repository to your local machine.

    git clone https://github.com/<your-username>/guestbook.git

  3. Navigate to and open the project in your code editor.

    cd guestbook

Using Markdown for Documentation

Markdown is a lightweight and easy-to-use markup language that allows you to format text in a readable and visually appealing way. When contributing to the documentation in this repository, it's important to use Markdown to structure and format your content effectively.

Markdown Basics

Here are some common Markdown elements you can use:

1. Headings

Use the hash (#) symbol to create headings (titles and subtitles). There are six levels of section headings, and the number of symbols indicates the heading level.

# Heading 1

## Heading 2

2. Text Formatting

  • Make text bold by enclosing it with double asterisks (**).
  • Make text italic by enclosing it with single underscores (_).
  • Create inline code by wrapping text with backticks (`).
**This is a bold text.**

_This is an italic text._

This is an `inline code`.

3. Lists

  • Create ordered lists using numbers followed by a period (1., 2., etc.).
  • Create unordered lists using hyphens (-).
1.  Item 1
2.  Item 2

- Unordered Item 1
- Unordered Item 2

4. Links

Create links using square brackets ([]) for the link text and parentheses (()) for the URL.

[Intro to Open Source with OpenSauced](https://intro.opensauced.pizza/#/)

5. Images

Embed images using an exclamation mark (!), followed by square brackets ([]) for the alt text, and parentheses (()) for the image URL.

![OpenSauced Highlights](https://github.com/open-sauced/intro/blob/main/images/opensauced-highlights.png)

6. Blockquotes

Create blockquotes using the greater-than symbol (>).

> This is a blockquote.

7. Code Blocks

Create code blocks using triple backticks (```) for fenced code blocks and specify a language next to the backticks before the fenced code block to highlight the syntax.

```bash
git pull
```

Markdown Tips

  • Preview your Markdown locally to ensure proper formatting before submitting your contribution.
  • Keep your Markdown content organized, and use headings to structure the sections.
  • Use code blocks to highlight code snippets or configuration examples.
  • Check out the official Markdown Guide website for more information about using Markdown.

Adding Translations to Documentation

Adding translations to our project's documentation helps make it more accessible to a wider audience. If you're interested in contributing translations for our documentation, check out the below section.

Steps to Add Translations

1. Identify Target Languages:

  • Determine which languages you want to add translations for. Make sure these languages are relevant to the project's user base.

2. Create Translation Files:

  • Inside the documentation directory, create a new subdirectory for each language you plan to support. Use language codes (e.g., "en" for English, "fr" for French) as directory names.
- docs/
  - en/         (English)
  - fr/         (French)
  - es/         (Spanish)

3. Translate Content:

  • For each language directory, create translated versions of the documentation files. Typically, you will translate Markdown files, but consider other formats as needed.
  • Maintain the same file structure and filenames as in the original documentation, but with translated content.

4 Update Links:

  • In the translated files, ensure that any internal links (e.g., links to other sections or pages within the documentation) are updated to point to the corresponding translated content.

5. Add Language Selector:

  • Consider adding a language selector to the documentation, allowing users to switch between different language versions. You can do this by modifying the navigation or header of your documentation.

6. Testing and Validation:

  • Test the translated documentation to ensure accuracy and readability. Make sure that all links work correctly and that the content is culturally appropriate.

7. Submit Contributions:

  • If you haven't already, submit your translations as a pull request. Ensure that you provide clear information about the languages you've translated and any specific details related to your contributions.

8. Collaborate and Review:

  • Collaborate with other contributors and reviewers to ensure the quality of translations. Be open to feedback and suggestions for improvement.

Best Practices for Translations

  • Maintain consistency in terminology and style throughout the translated documentation.
  • Work with another contributor who speaks the language you're translating to.
  • It helps to mention specific tools so that developers who want to translate documentation can see how it's done.
  • Keep translations up to date with changes in the original documentation.