pandas-dev · datapythonista · Nov 13, 2019 · Nov 13, 2019 · Nov 14, 2019 · Nov 14, 2019
diff --git a/doc/source/development/extending.rst b/doc/source/development/extending.rst
@@ -59,7 +59,7 @@ Now users can access your methods using the ``geo`` namespace:
 
 This can be a convenient way to extend pandas objects without subclassing them.
 If you write a custom accessor, make a pull request adding it to our
-:ref:`ecosystem` page.
+`Ecosystem </community/ecosystem.html>`__ page.
 
 We highly recommend validating the data in your accessor's `__init__`.
 In our ``GeoAccessor``, we validate that the data contains the expected columns,
@@ -91,7 +91,7 @@ objects). Many methods like :func:`pandas.isna` will dispatch to the extension
 type's implementation.
 
 If you're building a library that implements the interface, please publicize it
-on :ref:`ecosystem.extensions`.
+on `Extension data types </community/ecosystem.html#extension-data-types>`__.
 
 The interface consists of two classes.
 

diff --git a/doc/source/development/index.rst b/doc/source/development/index.rst
@@ -17,4 +17,3 @@ Development
     extending
     developer
     policies
-    roadmap
diff --git a/doc/source/development/roadmap.rst b/doc/source/development/roadmap.rst