From f939af74dc5cf49056cce1e1fbf829ed0d2d9fe0 Mon Sep 17 00:00:00 2001 From: Matt Westcott Date: Thu, 10 Jul 2014 13:33:20 +0100 Subject: [PATCH] Fix more doc syntax errors --- docs/index.rst | 1 + docs/releases/0.4.rst | 4 ++-- docs/releases/index.rst | 7 +++++++ docs/search/backends.rst | 2 +- docs/search/editors_picks.rst | 2 +- docs/search/for_python_developers.rst | 2 +- 6 files changed, 13 insertions(+), 5 deletions(-) create mode 100644 docs/releases/index.rst diff --git a/docs/index.rst b/docs/index.rst index a040fe767c..2ab429eb62 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -28,3 +28,4 @@ It supports Django 1.6.2+ on Python 2.6, 2.7, 3.2, 3.3 and 3.4. Django 1.7 suppo support roadmap editor_manual/index + releases/index diff --git a/docs/releases/0.4.rst b/docs/releases/0.4.rst index a53ca5463c..3aa6306036 100644 --- a/docs/releases/0.4.rst +++ b/docs/releases/0.4.rst @@ -32,7 +32,7 @@ A new management command has been added (:ref:`publish_scheduled_pages`) to publ Search on QuerySet with Elasticsearch ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Its now possible to perform searches with Elasticsearch on ``PageQuerySet``s: +Its now possible to perform searches with Elasticsearch on ``PageQuerySet`` objects: >>> from wagtail.wagtailcore.models import Page >>> Page.objects.live().descendant_of(events_index).search("Hello") @@ -174,7 +174,7 @@ Previously, the ``route`` method called ``serve`` and returned a ``HttpResponse` Wagtailadmins ``hooks`` module has moved to wagtailcore -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If you use any ``wagtail_hooks.py`` files in your project, you may have an import like: ``from wagtail.wagtailadmin import hooks`` diff --git a/docs/releases/index.rst b/docs/releases/index.rst new file mode 100644 index 0000000000..07bc8e888e --- /dev/null +++ b/docs/releases/index.rst @@ -0,0 +1,7 @@ +Release notes +============= + +.. toctree:: + :maxdepth: 1 + + 0.4 \ No newline at end of file diff --git a/docs/search/backends.rst b/docs/search/backends.rst index eba6d8a1a8..f03f063581 100644 --- a/docs/search/backends.rst +++ b/docs/search/backends.rst @@ -14,7 +14,7 @@ Wagtail can degrade to a database-backed text search, but we strongly recommend .. _wagtailsearch_backends_database: Database Backend -=============== +================ The default DB search backend uses Django's ``__icontains`` filter. diff --git a/docs/search/editors_picks.rst b/docs/search/editors_picks.rst index f899302b41..9ed41f3c54 100644 --- a/docs/search/editors_picks.rst +++ b/docs/search/editors_picks.rst @@ -1,5 +1,5 @@ -.. _wagtailsearch_editors_picks: +.. _editors-picks: Editors picks diff --git a/docs/search/for_python_developers.rst b/docs/search/for_python_developers.rst index c73799a7ab..7ff9a18dc4 100644 --- a/docs/search/for_python_developers.rst +++ b/docs/search/for_python_developers.rst @@ -35,7 +35,7 @@ Fields need to be explicitly added to the search configuration in order for you You can add new fields to the search index by overriding the ``search_fields`` property and appending a list of extra ``SearchField``/``FilterField`` objects to it. -``Page`` sets a default value to ``search_fields`` indexing the ``title`` field as a ``SearchField`` and some other generally useful fields as ``FilterField``s. +The default value of ``search_fields`` (as set in ``Page``) indexes the ``title`` field as a ``SearchField`` and some other generally useful fields as ``FilterField`` rules. Quick example