- [ ] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md

I am:

- [ ] Suggesting edits to an existing Topic page

- [ ] Curating a new Topic page

- [ ] Suggesting edits to an existing topic or collection

- [ ] Curating a new topic or collection

***********EDITING AN EXISTING TOPIC PAGE************

***********EDITING AN EXISTING TOPIC OR COLLECTION************

I'm suggesting these edits to an existing topic:

- [ ] Image (and my file is `*.png`, square, dimensions 288x288)

Please explain why these changes are necessary:

************CURATING A NEW TOPIC PAGE************

************CURATING A NEW TOPIC OR COLLECTION************

- [ ] I've formatted my changes as a new folder directory, named for the topic as it appears in the URL on GitHub (e.g. `https://github.com/topics/[NAME]`)

- [ ] My folder contains a `*.png` image (if applicable) and `index.md`

- [ ] All required fields in my `index.md` conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

Please explain why you think this Topic page should be curated:

Please explain why you think this topic or collection should be curated:

**Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.**

Hi there! We're excited you've got ideas for an existing or new topic page. Your help makes Explore valuable to others in your community.

Hi there! We're excited you've got ideas to improve topics and collections. Your helping the community discover valuable information.

This project adheres to the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.

There are a few ways you can contribute: improving an existing topic page, or curating a new topic page.

There are a few ways you can contribute:

- Improving an existing topic or collection

- Curating a new topic topic or collection

As you write content, check out the [Style Guide](./docs/styleguide.md) to learn what each field means, and how they should be formatted. Following the style guide will improve the chances of your contribution being accepted.

Note: updates won't immediately appear once we've merged your PR. We pull in these changes regularly to GitHub.

Note: Updates won't immediately appear once we've merged your PR. We pull in these changes regularly to GitHub.

If a topic page already exists, it will be listed in the [topics directory](https://github.com/github/explore/tree/master/topics). The topic name should match its URL, e.g. `https://github.com/topics/rails` corresponds to the [`rails` folder](https://github.com/github/explore/tree/master/topics/rails).

If a topic or collection already exists, it will be listed in its respective directory:

To improve an existing topic page, please **open a pull request** with your proposed changes:

- [Topics](https://github.com/github/explore/tree/master/topics)

- [Collections](https://github.com/github/explore/tree/master/collections)

* To update the image, replace the image inside the topic's folder

* To update the content, edit the `index.md` inside the topic's folder

The topic or collection name should match its URL, e.g. `https://github.com/topics/rails` corresponds to the [`topics/rails` directory](https://github.com/github/explore/tree/master/topics/rails).

**Please fill out the pull request template completely.** If you do not fill out the template, your PR will be closed.

To update the image, simply replace the image inside the topic or collection's directory

To update text and links, edit the `index.md` inside the topic or collection's directory. These files are formatted using a combination of [front matter](https://jekyllrb.com/docs/frontmatter/) and simple body content.

For **topics**, you'll notice that, in examples like "[algolia](https://raw.githubusercontent.com/github/explore/master/topics/algolia/index.md)," data like the topic's canonical URL, Wikipedia URL, or display name are called out in key-value pairs; while its detailed description is accounted for in the body of the document.

_/topics/algolia/index.md_:

Similarly, **collections** like "[music](https://raw.githubusercontent.com/github/explore/master/collections/music/index.md)" call out things like their author and display name in key-value pairs -- with a detailed description in the body of the document. Most importantly, though, collections identify their individual collection items in a comma-separated string value for the key "items."

_/collections/music/index.md_:

The [pull request template](./.github/PULL_REQUEST_TEMPLATE.md) also provides guidance on the information you need to include.

**Please fill out the pull request template completely.** If you do not fill out the template, your PR will be closed.

If a topic page is not yet curated, it will NOT be listed in the [topics directory](https://github.com/github/explore/tree/master/topics). The default layout on `https://github.com/topics/foo` looks like this:


If a topic or collection is not yet curated, it will NOT be listed in its respective directory.

We are likely to consider suggestions to curate a topic page that is valuable to GitHub's community. Valuable topics include those that are already [widely used by repositories](https://help.github.com/articles/classifying-your-repository-with-topics/), or a topic that currently lacks important information. When suggesting content for a topic page, please consider how to make your contribution broadly useful and relevant to others, rather than serving a specific use case.

We are likely to consider suggestions to curate a topic or collection that is valuable to GitHub's community. Valuable topics, for example, include those that are already [widely used by repositories](https://help.github.com/articles/classifying-your-repository-with-topics/), or a topic that currently lacks important information. When suggesting content, please consider how to make your contribution broadly useful and relevant to others, rather than serving a specific use case.

Please note that all suggestions must adhere to GitHub's [Community Guidelines](https://help.github.com/articles/github-community-guidelines/) and [Terms of Service](https://help.github.com/articles/github-terms-of-service/). Per our Terms of Service, [you are responsible](https://help.github.com/articles/github-terms-of-service/#d-user-generated-content) for the content you contribute, and you must have the rights to use it.

To propose a new topic page, please **open an pull request** with your proposed changes. The [API docs](./docs/API.md) and [style guide](./docs/styleguide.md) provide guidance on the information you need to include and how it should be formatted.

To propose a new topic or collection, please **open an pull request** with your proposed additions. The [API docs](./docs/API.md) and [style guide](./docs/styleguide.md) provide guidance on the information you need to include and how it should be formatted.

This repository includes [a list of the most-used GitHub topics that don't yet have extra context](topics-todo.md). If your pull request adds one of these topics, please update topics-todo.md so that the topic is checked (marked complete).

[](https://travis-ci.org/github/explore)

Topic pages, curated by the community.

[Topics](https://help.github.com/articles/about-topics/) help you explore repositories in a particular subject area, learn more about that subject, and find projects to contribute to.

[Topics](https://help.github.com/articles/about-topics/) help you explore repositories in a particular subject area, learn more about a subject area, and find projects to contribute to.

[Collections](http://github.com/collections) help you discover hand-picked repositories, developers, organizations, videos, and articles that share a common theme.

If you want to suggest edits to an existing topic page, or curate a new topic page, read our [contributing guide](CONTRIBUTING.md) to get started. You can [review a list of popular topics that need more context](topics-todo.md) to get an idea of where to start.

If you want to suggest edits to an existing topic page or collection, or curate a new one, read our [contributing guide](CONTRIBUTING.md) to get started. You can also [review a list of popular topics that need more context](topics-todo.md) to get an idea of where to start.

There are some lint tests in place to ensure each topic is formatted in the way we expect. Travis

CI will run the tests automatically. If you want to run the tests yourself locally, you will need

Ruby and Bundler installed.

There are some lint tests in place to ensure each topic is formatted in the way we expect. Travis CI will run the tests automatically. If you want to run the tests yourself locally, you will need Ruby and Bundler installed.

You can run the tests using:

If you're making edits to a topic page, the following fields are available for use. Not all fields are required.

(required) A longer description of the topic, which will appear on its topic page. Must be 1,000 characters or less. Should not be the same as `short_description`. Some Markdown is allowed, such as links. Emoji are allowed.

If you're making edits to a collection, the following fields are available for use. Not all fields are required.

A comma-separated string containing any of the following values:

- GitHub repository path (e.g. `defunkt/dotjs`)

- GitHub username (e.g. `defunkt`)

- GitHub organization (e.g. `github`)

- Any web URL (e.g. `https://product.hubspot.com/blog/git-and-github-tutorial-for-beginners`)

- Any YouTube video URL (e.g. `https://www.youtube.com/watch?v=0fKg7e37bQE`)

A complete `items` key-value pair might look like:

(if applicable) GitHub username of the person and/or organization that authored the collection.

(required) The collection name that will be displayed on its page (ex. `How to choose (and contribute to) your first open source project`). Should use proper noun capitalization. Emoji are not allowed.

(required) A longer description of the collection, which will appear on its page. Must be 1,000 characters or less. Some Markdown is allowed, such as links. Emoji are allowed.

Include and spell out the month. Include the day number without the "th" or "nd" at the end, for example: October 12.

Avoid exclamation points in topic pages.

Avoid exclamation points in topic pages and collections.

Always use correct capitalization when referring to "GitHub" or "Git". Never use "GitHub" or "Git" as a verb.