update all wagtail.io to wagtail.org

- also ensure that we link to stable not latest when using docs links consistently

bakerydemo/base/fixtures/bakerydemo.json

@@ -3512,7 +3512,7 @@
   "fields": {
     "introduction": "Things to know about this demo site",
     "image": 41,
-    "body": "[{\"type\": \"paragraph_block\", \"value\": \"<h2>Welcome to the Wagtail Demo Site!</h2><p>If you've gotten this far, congratulations - you're running an instance of a killer content management system written for and on top of Django, <i>the framework for perfectionists with deadlines.</i></p><p>What does Wagtail get you that Django alone does not?\\u00a0</p><p></p><ul><li>Focus on content creators/managers, rather than developers (but developer-friendly!)</li><li>\\\"Page-centric\\\" content modeling</li><li>Beautiful, modern, intuitive user interface optimized for content people</li><li>Super-powerful hierarchical content management (\\\"content trees\\\")</li><li>User- and group-based permissions system attached to content hierarchies</li><li>Flexible image resizing with a ton of image display helpers</li><li>Innovative \\\"<a href=\\\"https://torchbox.com/blog/rich-text-fields-and-faster-horses/\\\">StreamFields</a>\\\" as an alternative to traditional \\\"anything goes\\\" rich text fields</li><li>Intuitive choosers for embedded Pages, Images, Documents and other content</li><li>Native integration with ElasticSearch to help you build powerful search features</li><li>Template tags to help create image renditions, smart links, and to navigate content trees</li></ul><p>If you're new to Wagtail, there are two primary paths to learning:</p><p></p><ul><li>The source code that powers this demo site</li><li>The official <a href=\\\"https://docs.wagtail.io/en/stable/getting_started/index.html\\\">tutorial</a></li></ul><p></p><p></p>\"}]"
+    "body": "[{\"type\": \"paragraph_block\", \"value\": \"<h2>Welcome to the Wagtail Demo Site!</h2><p>If you've gotten this far, congratulations - you're running an instance of a killer content management system written for and on top of Django, <i>the framework for perfectionists with deadlines.</i></p><p>What does Wagtail get you that Django alone does not?\\u00a0</p><p></p><ul><li>Focus on content creators/managers, rather than developers (but developer-friendly!)</li><li>\\\"Page-centric\\\" content modeling</li><li>Beautiful, modern, intuitive user interface optimized for content people</li><li>Super-powerful hierarchical content management (\\\"content trees\\\")</li><li>User- and group-based permissions system attached to content hierarchies</li><li>Flexible image resizing with a ton of image display helpers</li><li>Innovative \\\"<a href=\\\"https://torchbox.com/blog/rich-text-fields-and-faster-horses/\\\">StreamFields</a>\\\" as an alternative to traditional \\\"anything goes\\\" rich text fields</li><li>Intuitive choosers for embedded Pages, Images, Documents and other content</li><li>Native integration with ElasticSearch to help you build powerful search features</li><li>Template tags to help create image renditions, smart links, and to navigate content trees</li></ul><p>If you're new to Wagtail, there are two primary paths to learning:</p><p></p><ul><li>The source code that powers this demo site</li><li>The official <a href=\\\"https://docs.wagtail.org/en/stable/getting_started/index.html\\\">tutorial</a></li></ul><p></p><p></p>\"}]"
   }
 }
 ]

bakerydemo/base/models.py

@@ -338,7 +338,7 @@ class FormField(AbstractFormField):
     to generate a general purpose data-collection form or contact form
     without having to write code. We use it on the site for a contact form. You
     can read more about Wagtail forms at:
-    https://docs.wagtail.io/en/latest/reference/contrib/forms/index.html
+    https://docs.wagtail.org/en/stable/reference/contrib/forms/index.html
     """
     page = ParentalKey('FormPage', related_name='form_fields', on_delete=models.CASCADE)
 

bakerydemo/blog/models.py

@@ -43,7 +43,7 @@ class BlogPageTag(TaggedItemBase):
     """
     This model allows us to create a many-to-many relationship between
     the BlogPage object and tags. There's a longer guide on using it at
-    https://docs.wagtail.io/en/latest/reference/pages/model_recipes.html#tagging
+    https://docs.wagtail.org/en/stable/reference/pages/model_recipes.html#tagging
     """
     content_object = ParentalKey('BlogPage', related_name='tagged_items', on_delete=models.CASCADE)
 
@@ -54,7 +54,7 @@ class BlogPage(Page):
 
     We access the People object with an inline panel that references the
     ParentalKey's related_name in BlogPeopleRelationship. More docs:
-    https://docs.wagtail.io/en/latest/topics/pages.html#inline-models
+    https://docs.wagtail.org/en/stable/topics/pages.html#inline-models
     """
     introduction = models.TextField(
         help_text='Text to describe the page',
@@ -166,7 +166,7 @@ class BlogIndexPage(RoutablePageMixin, Page):
 
     # Overrides the context to list all child items, that are live, by the
     # date that they were published
-    # https://docs.wagtail.io/en/latest/getting_started/tutorial.html#overriding-context
+    # https://docs.wagtail.org/en/stable/getting_started/tutorial.html#overriding-context
     def get_context(self, request):
         context = super(BlogIndexPage, self).get_context(request)
         context['posts'] = BlogPage.objects.descendant_of(
@@ -177,7 +177,7 @@ class BlogIndexPage(RoutablePageMixin, Page):
     # This defines a Custom view that utilizes Tags. This view will return all
     # related BlogPages for a given Tag or redirect back to the BlogIndexPage.
     # More information on RoutablePages is at
-    # https://docs.wagtail.io/en/latest/reference/contrib/routablepage.html
+    # https://docs.wagtail.org/en/stable/reference/contrib/routablepage.html
     @route(r'^tags/$', name='tag_archive')
     @route(r'^tags/([\w-]+)/$', name='tag_archive')
     def tag_archive(self, request, tag=None):

bakerydemo/breads/models.py

@@ -44,7 +44,7 @@ class BreadIngredient(models.Model):
     to the `@register_snippet` decorator. We use a new piece of functionality
     available to Wagtail called the ParentalManyToManyField on the BreadPage
     model to display this. The Wagtail Docs give a slightly more detailed example
-    https://docs.wagtail.io/en/latest/getting_started/tutorial.html#categories
+    https://docs.wagtail.org/en/stable/getting_started/tutorial.html#categories
     """
     name = models.CharField(max_length=255)
 

bakerydemo/locations/models.py

@@ -110,7 +110,7 @@ class LocationsIndexPage(Page):
 
     # Overrides the context to list all child
     # items, that are live, by the date that they were published
-    # https://docs.wagtail.io/en/latest/getting_started/tutorial.html#overriding-context
+    # https://docs.wagtail.org/en/stable/getting_started/tutorial.html#overriding-context
     def get_context(self, request):
         context = super(LocationsIndexPage, self).get_context(request)
         context['locations'] = LocationPage.objects.descendant_of(

bakerydemo/search/views.py

@@ -16,7 +16,7 @@ def search(request):
     if search_query:
         if 'elasticsearch' in settings.WAGTAILSEARCH_BACKENDS['default']['BACKEND']:
             # In production, use ElasticSearch and a simplified search query, per
-            # https://docs.wagtail.io/en/latest/topics/search/backends.html
+            # https://docs.wagtail.org/en/stable/topics/search/backends.html
             # like this:
             search_results = Page.objects.live().search(search_query)
         else:

bakerydemo/templates/includes/footer.html

@@ -21,7 +21,7 @@
                     </a>
                 </li>
                 <li>
-                    <a href="https://wagtail.io/" target="_blank">
+                    <a href="https://wagtail.org/" target="_blank">
                         <span class="fa-stack fa-lg">
                             <i class="fa fa-circle fa-stack-2x"></i>
                             <i class="fa fa-link fa-stack-1x fa-inverse"></i>

readme.md

@@ -184,7 +184,7 @@ environments typically work in the same manner.  In laymen's terms, this means t
 minimum of once per day, and on each application deployment. To mitigate this, you can host your media on S3.
 
 This documentation assumes that you have an AWS account, an IAM user, and a properly configured S3 bucket. These topics
-are outside of the scope of this documentation; the following [blog post](https://wagtail.io/blog/amazon-s3-for-media-files/)
+are outside of the scope of this documentation; the following [blog post](https://wagtail.org/blog/amazon-s3-for-media-files/)
 will walk you through those steps.
 
 This demo site comes preconfigured with a production settings file that will enable S3 for uploaded media storage if
@@ -205,8 +205,7 @@ time you might need to run it again.
 
 # Next steps
 
-Hopefully after you've experimented with the demo you'll want to create your own site. To do that you'll want to run the `wagtail start` command in your environment of choice. You can find more information in the [getting started Wagtail CMS docs](http://wagtail.readthedocs.io/en/latest/getting_started/index.html).
-
+Hopefully after you've experimented with the demo you'll want to create your own site. To do that you'll want to run the `wagtail start` command in your environment of choice. You can find more information in the [getting started Wagtail CMS docs](https://docs.wagtail.org/en/stable/getting_started/index.html).
 
 # Contributing
 
@@ -230,7 +229,7 @@ Because we can't (easily) use ElasticSearch for this demo, we use wagtail's nati
 However, native DB search can't search specific fields in our models on a generalized `Page` query.
 So for demo purposes ONLY, we hard-code the model names we want to search into `search.views`, which is
 not ideal. In production, use ElasticSearch and a simplified search query, per
-[https://docs.wagtail.io/en/latest/topics/search/searching.html](https://docs.wagtail.io/en/latest/topics/search/searching.html).
+[https://docs.wagtail.org/en/stable/topics/search/searching.html](https://docs.wagtail.org/en/stable/topics/search/searching.html).
 
 ### Sending email from the contact form