当 Django 增加新特性，以及 Django API 或者其行为发生改变时，会补充相关内容到文档 中。 Django 文档和其代码使用同一份版本控制进行管理。它位于我们 Git 仓库的 docs 目录下。在 Git 仓库中，每一份在线文档都是独立的文本文件。 您可以通过多种方式阅读 Django 文档，根据优先级顺序排列如下： 文档是如何更新的 哪里可以获取文档 在线获取 接下来如何学习？ （tarball）的 docs/ 的目录下。 如果您正在使用开发版本的 Django (又名”trunk 版本”)，请注意 docs/ 目录包含了所有的 文档。您可以通过 git checkout 来获取最新更新。 一个稍微有点技术含量的查看文档的方法是通过 Unix 系统的 grep 命令来查找关键字搜索文 档。例如，这将会展示 Django 文档中每一处提及” docs/_build/html 中。 正如前面提及的那样，我们 Git 仓库中的文档包含了许多“最新最好”的改变。这些改变通常包括了 Django 开发版本新增的一些特性。因此出于以上理由，有必要说明我们在处理不同 Django 版本 文档时所遵循的准则。 我们遵循着如下准则： 在 djangoproject.com 呈现的内容始终是 Git 仓库最新文档的 HTML 版本。这些文档总 是对应 Django

get it Differences between versions Writing your first patch for Django Introduction Installing Git Getting a copy of Django’s development version Rolling back to a previous revision of Django Running documentation is kept in the same source control system as its code. It lives in the docs directory of our Git repository. Each document online is a separate text file in the repository. Where to get it You can (aka “trunk”), note that the docs/ directory contains all of the documentation. You can update your Git checkout to get the latest changes. One low-tech way of taking advantage of the text documentation

Differences between versions Writing your first patch for Django Introduction Code of Conduct Installing Git Getting a copy of Django’s development version Rolling back to a previous revision of Django Running documentation is kept in the same source control system as its code. It lives in the docs directory of our Git repository. Each document online is a separate text file in the repository. Where to get it You can (aka “trunk”), note that the docs/ directory contains all of the documentation. You can update your Git checkout to get the latest changes. One low-tech way of taking advantage of the text documentation

Differences between versions Writing your first patch for Django Introduction Code of Conduct Installing Git Getting a copy of Django’s development version Rolling back to a previous revision of Django Running documentation is kept in the same source control system as its code. It lives in the docs directory of our Git repository. Each document online is a separate text file in the repository. Where to get it You can (aka “trunk”), note that the docs/ directory contains all of the documentation. You can update your Git checkout to get the latest changes. One low-tech way of taking advantage of the text documentation

Differences between versions Writing your first patch for Django Introduction Code of Conduct Installing Git Getting a copy of Django’s development version Rolling back to a previous revision of Django Running documentation is kept in the same source control system as its code. It lives in the docs directory of our Git repository. Each document online is a separate text file in the repository. Where to get it You can (aka “trunk”), note that the docs/ directory contains all of the documentation. You can update your Git checkout to get the latest changes. One low-tech way of taking advantage of the text documentation

documentation is kept in the same source control system as its code. It lives in the docs directory of our Git repository. Each document online is a separate text file in the repository. 2.11.4 Where to get it (aka “trunk”), note that the docs/ directory contains all of the documentation. You can update your Git checkout to get the latest changes. One low-tech way of taking advantage of the text documentation documentation in our Git repository contains the “latest and greatest” changes and additions. These changes often include documentation of new features added in the Django development version – the Git (“trunk”)

documentation is kept in the same source control system as its code. It lives in the docs directory of our Git repository. Each document online is a separate text file in the repository. 2.11.4 Where to get it (aka “trunk”), note that the docs/ directory contains all of the documentation. You can update your Git checkout to get the latest changes. One low-tech way of taking advantage of the text documentation documentation in our Git repository contains the “latest and greatest” changes and additions. These changes often include documentation of new features added in the Django development version – the Git (“trunk”)

documentation is kept in the same source control system as its code. It lives in the docs directory of our Git repository. Each document online is a separate text file in the repository. 2.10.4 Where to get it (aka “trunk”), note that the docs/ directory contains all of the documentation. You can update your Git checkout to get the latest changes. One low-tech way of taking advantage of the text documentation documentation in our Git repository contains the “latest and greatest” changes and additions. These changes often include documentation of new features added in the Django development version – the Git (“trunk”)

Install the application from its GitHub repository using pip: pip install git+http://git@github.com/divio/django-polls.git#egg=polls Let’s add this application to our project. Add 'polls' to the end also places it in your virtualenv’s src directory as a cloned Git repository: pip install -e git+http://git@github.com/divio/django- polls.git#egg=polls You should end up with a folder structure similar GitHub repository to your own GitHub account 2. Clone your fork locally: git clone git@github.com:YOUR_USERNAME/django-cms.git 3. Create a virtualenv: virtualenv cms-develop source cms-develop/bin/activate

documentation is kept in the same source control system as its code. It lives in the docs directory of our Git repository. Each document online is a separate text file in the repository. 2.11.4 Where to get it (aka “trunk”), note that the docs/ directory contains all of the documentation. You can update your Git checkout to get the latest changes. One low-tech way of taking advantage of the text documentation documentation in our Git repository contains the “latest and greatest” changes and additions. These changes often include documentation of new features added in the Django development version – the Git (“trunk”)