mirror of
https://github.com/django/django.git
synced 2025-08-04 02:48:35 +00:00
Fixed #25755 -- Unified spelling of "website".
This commit is contained in:
parent
53326e2c8a
commit
1f8dad6915
33 changed files with 55 additions and 55 deletions
|
@ -2702,7 +2702,7 @@ Multiple admin sites in the same URLconf
|
|||
----------------------------------------
|
||||
|
||||
It's easy to create multiple instances of the admin site on the same
|
||||
Django-powered Web site. Just create multiple instances of ``AdminSite`` and
|
||||
Django-powered website. Just create multiple instances of ``AdminSite`` and
|
||||
root each one at a different URL.
|
||||
|
||||
In this example, the URLs ``/basic-admin/`` and ``/advanced-admin/`` feature
|
||||
|
|
|
@ -153,7 +153,7 @@ Widget classes
|
|||
``template_name`` is ``gis/openlayers.html``.
|
||||
|
||||
``OpenLayersWidget`` and :class:`OSMWidget` use the ``openlayers.js`` file
|
||||
hosted on the ``openlayers.org`` Web site. This works for basic usage
|
||||
hosted on the ``openlayers.org`` website. This works for basic usage
|
||||
during development, but isn't appropriate for a production deployment as
|
||||
``openlayers.org/api/`` has no guaranteed uptime and runs on a slow server.
|
||||
You are therefore advised to subclass these widgets in order to specify
|
||||
|
|
|
@ -104,7 +104,7 @@ internal geometry representation used by GeoDjango (it's behind the "lazy"
|
|||
geometries). Specifically, the C API library is called (e.g., ``libgeos_c.so``)
|
||||
directly from Python using ctypes.
|
||||
|
||||
First, download GEOS 3.4.2 from the GEOS Web site and untar the source
|
||||
First, download GEOS 3.4.2 from the GEOS website and untar the source
|
||||
archive::
|
||||
|
||||
$ wget http://download.osgeo.org/geos/geos-3.4.2.tar.bz2
|
||||
|
|
|
@ -381,7 +381,7 @@ GeoDjango on Windows.
|
|||
Python
|
||||
^^^^^^
|
||||
|
||||
First, download the latest `Python 2.7 installer`__ from the Python Web site.
|
||||
First, download the latest `Python 2.7 installer`__ from the Python website.
|
||||
Next, run the installer and keep the defaults -- for example, keep
|
||||
'Install for all users' checked and the installation path set as
|
||||
``C:\Python27``.
|
||||
|
@ -398,7 +398,7 @@ PostgreSQL
|
|||
^^^^^^^^^^
|
||||
|
||||
First, download the latest `PostgreSQL 9.x installer`__ from the
|
||||
`EnterpriseDB`__ Web site. After downloading, simply run the installer,
|
||||
`EnterpriseDB`__ website. After downloading, simply run the installer,
|
||||
follow the on-screen directions, and keep the default options unless
|
||||
you know the consequences of changing them.
|
||||
|
||||
|
|
|
@ -147,7 +147,7 @@ Additional Resources:
|
|||
|
||||
* `spatialreference.org`__: A Django-powered database of spatial reference
|
||||
systems.
|
||||
* `The State Plane Coordinate System`__: A Web site covering the various
|
||||
* `The State Plane Coordinate System`__: A website covering the various
|
||||
projection systems used in the United States. Much of the U.S. spatial
|
||||
data encountered will be in one of these coordinate systems rather than
|
||||
in a geographic coordinate system such as WGS84.
|
||||
|
|
|
@ -116,7 +116,7 @@ See the :doc:`sessions documentation </topics/http/sessions>`.
|
|||
sites
|
||||
=====
|
||||
|
||||
A light framework that lets you operate multiple Web sites off of the same
|
||||
A light framework that lets you operate multiple websites off of the same
|
||||
database and Django installation. It gives you hooks for associating objects to
|
||||
one or more sites.
|
||||
|
||||
|
|
|
@ -13,7 +13,7 @@ creating sitemap_ XML files easy.
|
|||
Overview
|
||||
========
|
||||
|
||||
A sitemap is an XML file on your Web site that tells search-engine indexers how
|
||||
A sitemap is an XML file on your website that tells search-engine indexers how
|
||||
frequently your pages change and how "important" certain pages are in relation
|
||||
to other pages on your site. This information helps search engines index your
|
||||
site.
|
||||
|
|
|
@ -3,11 +3,11 @@ The "sites" framework
|
|||
=====================
|
||||
|
||||
.. module:: django.contrib.sites
|
||||
:synopsis: Lets you operate multiple Web sites from the same database and
|
||||
:synopsis: Lets you operate multiple websites from the same database and
|
||||
Django project
|
||||
|
||||
Django comes with an optional "sites" framework. It's a hook for associating
|
||||
objects and functionality to particular Web sites, and it's a holding place for
|
||||
objects and functionality to particular websites, and it's a holding place for
|
||||
the domain names and "verbose" names of your Django-powered sites.
|
||||
|
||||
Use it if your single Django installation powers more than one site and you
|
||||
|
@ -17,11 +17,11 @@ The sites framework is mainly based on a simple model:
|
|||
|
||||
.. class:: models.Site
|
||||
|
||||
A model for storing the ``domain`` and ``name`` attributes of a Web site.
|
||||
A model for storing the ``domain`` and ``name`` attributes of a website.
|
||||
|
||||
.. attribute:: domain
|
||||
|
||||
The fully qualified domain name associated with the Web site.
|
||||
The fully qualified domain name associated with the website.
|
||||
For example, ``www.example.com``.
|
||||
|
||||
.. versionchanged:: 1.9
|
||||
|
@ -31,7 +31,7 @@ The sites framework is mainly based on a simple model:
|
|||
|
||||
.. attribute:: name
|
||||
|
||||
A human-readable "verbose" name for the Web site.
|
||||
A human-readable "verbose" name for the website.
|
||||
|
||||
The :setting:`SITE_ID` setting specifies the database ID of the
|
||||
:class:`~django.contrib.sites.models.Site` object associated with that
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue