Normalized the default application template.

Removed the default test that 1 + 1 = 2, because it's been committed
way too many times, in too many projects.

Added an import of `render` for views, because the first view will
often be:

def home(request):
    return render(request, "mysite/home.html")
Moved code comments about WSGI to docs, and rewrote said docs.
Used a significant example for URLconf includes.
Added links to the settings documentation.
Removed admindocs from default project template.
Enabled the admin by default.

Everyone uses the admin.
Added a default admin.py to the application template.

Thanks Ryan D Hiebert for the suggestion.
Disabled the sites framework by default.

RequestSite does the job for single-domain websites.
Removed settings related to email reporting.

While handy for small scale projects, it isn't exactly a best practice.
Removed STATICFILES/TEMPLATES_DIRS from default settings file.

The current best practice is to put static files and templates in
applications, for easier testing and deployment.
Removed STATICFILES_FINDERS/TEMPLATE_LOADERS from default settings file.

Only developers with special needs ever need to change these settings.
Avoided misleading TEMPLATE_DEBUG = DEBUG.

According to the docs TEMPLATE_DEBUG works only when DEBUG = True.
Reorganized settings in logical sections, and trimmed comments.
Enabled clickjacking protection by default.
Enabled the locale middleware by default.

USE_I18N is True by default, and doesn't work well without
LocaleMiddleware.
Moved logging config for email notifications of 500 error in the docs.
Removed MEDIA_ROOT/URL from default settings template.

Many sites will never deal with user-uploaded files, and MEDIA_ROOT is
complicated to explain.

Thanks Carl Meyer for the suggestion.
Removed STATIC_ROOT from the default settings template.

It isn't necessary in development, and it confuses beginners to no end.

Thanks Carl Meyer for the suggestion.
Used an absolute path for the SQLite database.

This ensures the settings file works regardless of which directory
django-admin.py / manage.py is invoked from.

ROOT_DIR got a +1 from the BDFL and another core dev. It doesn't involve
the concept of a "Django project"; it's just a convenient way to express
relative paths within the source code repository for non-Python files.

Thanks Jacob Kaplan-Moss for the suggestion.
Added security warnings for the most sensitive settings.