Skip to content

Latest commit

 

History

History
72 lines (50 loc) · 5.5 KB

CONTRIBUTING.md

File metadata and controls

72 lines (50 loc) · 5.5 KB
Raw

##How to use this repository

This repository is for user guides on how to use CocoaPods. It replaces the multiple Wikis, guides section of the old docs.cocoapods.org site, and some of the more verbose documentation sections of the API docs.

###Where is the content?

You can find all of the guides source in /source. Each section is then broken down into its own content folder. So the guides for using CocoaPods can be found in /source/using. Also, if you view a page on guides, there is a link at the bottom of the footer to the source page in this repo.

###How do I make a change?

Just like any other repository, you should create a fork, make a change, commit, and then submit a pull request to master.

###How do I add a new guide?

All the guides content is written in Markdown. Each page has some special information at the top, defined by ---. This is used to generate the index pages, as well as the sitemap in the footer. Each page must include this information at the very top of this page.

Here is a sample file:

---
title: Getting Started
description: This is a guide that describes setting up CocoaPods and integrating with your first project.
---

## What are CocoaPods

CocoaPods manages library dependencies for your Xcode projects.

##Overall Guidelines

  • This repo is for content for guides.cocoapods.org only. If you are having an issue with CocoaPods, please ask on StackOverflow or our mailing-list.
  • This is high-level content only. If you have an issue with the API documentation for one of the gems that make up CocoaPods, please file that issue in its own repo; API documentation is generated from source files.
  • This is not the repository for per-Pod documentation. See CocoaDocs for documentation on individual Pods.
  • Please do not add images hosted on 3rd party sites. Image explanations are great, but we would like to keep this a self-contained site.
  • Take out any personally identifiable information. This applies to images, code snippets, or any other content. Please keep all information anonymous.
  • Do not add promotional material. This applies to both Guides content and linked resources.

##Style Guidelines

While we aren't terribly picky about writing style, there are a few things we'd like to make sure are standard across the content of the Guides site.

  • All content must be in well written English. Use proper spelling and punctuation.
  • All guides content is separated into 3 sections: Using, Making, and Contributing. For any new guides, please choose the appropriate section.
  • All content is written in Markdown.
  • These are not tutorials, but rather explanations of the inner workings of CocoaPods.
  • If you would like to see these in another language, please open an issue, or simply start translating. We'd love to see this content accessible to more users.
  • Our code blocks are parsed by Pygments, so please make sure your code additions are highlighted correctly. The best way to check this is to run your changes locally. Instructions can be found in the README.
  • We also enjoy the Oxford comma.

##Issue Submissions

We are always looking for the best way to present information about CocoaPods. If you would like to see something specific, or start a discussion, please follow these guidelines.

  • Double check there is no open issue for a potential topic. If it is related, but not quite the same, make sure to mention the issue in your post.
  • When opening a new issue, please reference the specific guide you would like to talk about. If it does not exist, make sure to say so.
  • While discussing issues, links to external sites are welcome, but this site is for original content. If you'd like to add a link to a blog post or article, see the External Resource Submission guidelines below.
  • There are some topics, e.g. whether or not to check in the Pods folder, that will be heavily debated. In these situations, we would like to present both sides and give the user the best information to make an informed decision. Please be courteous and resepectful to your fellow developers.
  • UX suggestions are not only welcome, but encouraged. We want to make sure this content is easy to browse and easy to read.

##External Resource Submissions

We love including content from the greater community. When adding a new resource, please follow the following guidelines.

  • External resources are to be placed at the bottom of the guide for reference.
  • These should serve to enhance the content available on the Guides site, not duplicate it.
  • Make sure to add a resource on the correct page. E.g. a blog post on creating a private cocoapod should not be on the Specs and Spec Repo guide.
  • Links should lead to articles or blog posts. Please do not add links to StackOverflow, GitHub Issues, Gists, or our mailing list.
  • Links should be active at the time of submission. Please do not link to a mirror site.
  • Any external resource links should lead directly to the resource. Links with paywalls, adwalls, etc will not be accepted.
  • External resources should not be promotions or trying to sell something. We are happy to link to technical posts on your company's blog, but posts solely for advertising purposes will not be accepted.
  • All external resources should be submitted via pull request.