===============
SEO fields for objects of any model registered in admin.
Maintained by `Basil Shubin <https://github.com/bashu>`_, and some great
`contributors <https://github.com/bashu/django-easy-seo/contributors>`_.
.. image:: https://img.shields.io/pypi/v/django-easy-seo.svg
:target: https://pypi.python.org/pypi/django-easy-seo/
.. image:: https://img.shields.io/pypi/dm/django-easy-seo.svg
:target: https://pypi.python.org/pypi/django-easy-seo/
.. image:: https://img.shields.io/github/license/bashu/django-easy-seo.svg
:target: https://pypi.python.org/pypi/django-easy-seo/
.. raw:: html
<p align="center">
<img src="https://raw.githubusercontent.com/bashu/django-easy-seo/develop/logo/sizes%20500x300/color.png" alt="django-easy-seo">
</p>
Setup
-----
Either clone this repository into your project, or install with ``pip install django-easy-seo``
You'll need to add ``seo`` as a **LAST** item to ``INSTALLED_APPS`` in your project's ``settings.py`` file :
.. code-block:: python
INSTALLED_APPS = (
...
'seo', # must be last in a list
)
Then run ``./manage.py syncdb`` to create the required database tables
Configuration
-------------
There is only one mandatory configuration option you need to set in your ``settings.py`` :
.. code-block:: python
# Override / extend ModelAdmin classes for a given Models
SEO_FOR_MODELS = [
'<app_name>.models.<ModelName>',
]
Usage
-----
First of all, load the ``seo_tags`` in every template where you want to use it :
.. code-block:: html+django
{% load seo_tags %}
Use :
.. code-block:: html+django
{% seo '<title|keywords|description>' for object %}
or :
.. code-block:: html+django
{% seo '<title|keywords|description>' for object as variable %}
{{ variable }}
Please see ``example`` application. This application is used to manually test the functionalities of this package. This also serves as a good example.
You need only Django 1.4 or above to run that. It might run on older versions but that is not tested.
Metadata
Release files for django-easy-seo 0.4.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django-easy-seo-0.4.8.tar.gz | 20.4 kB | Without provenance | Details for django-easy-seo-0.4.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_easy_seo-0.4.8-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for django_easy_seo-0.4.8-py2.py3-none-any.whl |
Total release size: 48.4 kB
Release files / django-easy-seo-0.4.8.tar.gz
| Download URL | django-easy-seo-0.4.8.tar.gz |
|---|---|
| Size | 20.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2a4bcaeabfb24d27861547848f51b8f8f9f80d8bee9e53a1da2e857c217b3134
|
|
BLAKE2b-256 checksum How to use checksums |
bf35b2b91c5ed1e9690bfb710191cf9de084421abfa06b063be83a0b84c760a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.7
|
Release files / django_easy_seo-0.4.8-py2.py3-none-any.whl
| Download URL | django_easy_seo-0.4.8-py2.py3-none-any.whl |
|---|---|
| Size | 28.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
a2e358974aaf5ba34cf998515ee160d7807e4419e3c17cccf16ee15ca5649230
|
|
BLAKE2b-256 checksum How to use checksums |
c3c8c017ca0637e8b158b3d82be078e3c6a1f292220e533ad36e505ee91e681d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.7
|
Security for django-easy-seo 0.4.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.