Docs: testing for file tree diff

.readthedocs.yml

@@ -6,7 +6,7 @@ formats:
 
 sphinx:
   configuration: docs/conf.py
-  fail_on_warning: true
+  fail_on_warning: false
 
 python:
   install:

docs/user/added.rst

@@ -0,0 +1,4 @@
+Title
+=====
+
+This file was added.

docs/user/guides/deprecating-content.rst

@@ -11,10 +11,6 @@ and you don't necessary want to make the content inaccessible.
 Here you'll find some tips on how to use Read the Docs to deprecate your content
 progressively and in non harmful ways.
 
-.. seealso::
-
-   :doc:`/guides/best-practice/links`
-     More information about handling URL structures, renaming and removing content.
 
 Deprecating versions
 --------------------

docs/user/guides/index.rst

@@ -15,5 +15,4 @@ and how to write successful documentation.
    Content, themes and SEO </guides/content/index>
    Security and access </guides/access/index>
    Account management </guides/management/index>
-   Best practice </guides/best-practice/index>
    Troubleshooting problems </guides/troubleshooting/index>

docs/user/guides/redirects.rst

@@ -9,10 +9,6 @@ which means that the reader is automatically redirected to a *new URL*.
 
 .. seealso::
 
-   :doc:`/guides/best-practice/links`
-     The need for a redirect often comes from external links to your documentation.
-     Read more about handling links in this explanation of best practices.
-
    :doc:`/user-defined-redirects`
      If you want to know more about our implementation of redirects,
      you can look up more examples in our reference before continuing with the how-to.

docs/user/guides/technical-docs-seo-guide.rst

@@ -198,10 +198,6 @@ Read the Docs supports a few different kinds of :doc:`user defined redirects </u
 that should cover all the different cases such as redirecting a certain page for all project versions,
 or redirecting one version to another.
 
-.. seealso:
-
-   :doc:`/guides/best-practice/links`
-      Following best practices to avoid broken links is great for search engine ranking.
 
 Canonical URLs ✅️
 ~~~~~~~~~~~~~~~~~~

docs/user/index.rst

@@ -6,6 +6,7 @@ Read the Docs: documentation simplified
    :hidden:
    :caption: Getting started
 
+   /added
    /tutorial/index
    /intro/doctools
    /intro/mkdocs
@@ -77,7 +78,6 @@ Read the Docs: documentation simplified
    /security-log
    /badges
    /explanation/documentation-structure
-   /guides/best-practice/links
    /security-implications
 
 .. toctree::
@@ -103,7 +103,6 @@ Read the Docs: documentation simplified
    Content, themes and SEO </guides/content/index>
    Security and access </guides/access/index>
    Account management </guides/management/index>
-   Best practice </guides/best-practice/index>
    Troubleshooting problems </guides/troubleshooting/index>
 
 .. toctree::
@@ -126,6 +125,8 @@ Read the Docs: documentation simplified
 
    <a style="display: none;" rel="me" href="https://fosstodon.org/@readthedocs">Mastodon</a>
 
+I'm changing this file.
+
 Read the Docs simplifies managing software documentation
 by building and hosting your docs automatically,
 using the Git workflow you already use for code.

docs/user/user-defined-redirects.rst

@@ -19,8 +19,6 @@ the bad user experience of a 404 page is usually best to avoid.
 
    :doc:`/guides/redirects`
      This guide shows you how to add redirects with practical examples.
-   :doc:`/guides/best-practice/links`
-     Information and tips about creating and handling external references.
    :doc:`/guides/deprecating-content`
      A guide to deprecating features and other topics in a documentation.
 
@@ -29,7 +27,6 @@ Built-in redirects
 
 This section explains the redirects that are automatically active for all projects and how they are useful.
 Built-in redirects are especially useful for creating and sharing incoming links,
-which is discussed in depth in :doc:`/guides/best-practice/links`.
 
 .. _page_redirects: