@@ -527,58 +527,6 @@ You may be able to work on separate figures from separate threads. However,
527527you must in that case use a *non-interactive backend * (typically Agg), because
528528most GUI backends *require * being run from the main thread as well.
529529
530- .. _howto-contribute :
531-
532- How-to: Contributing
533- ====================
534-
535- .. _how-to-contribute-docs :
536-
537- Contribute to Matplotlib documentation
538- --------------------------------------
539-
540- Matplotlib is a big library, which is used in many ways, and the
541- documentation has only scratched the surface of everything it can
542- do. So far, the place most people have learned all these features are
543- through studying the :ref: `examples-index `, which is a
544- recommended and great way to learn, but it would be nice to have more
545- official narrative documentation guiding people through all the dark
546- corners. This is where you come in.
547-
548- There is a good chance you know more about Matplotlib usage in some
549- areas, the stuff you do every day, than many of the core developers
550- who wrote most of the documentation. Just pulled your hair out
551- compiling Matplotlib for Windows? Write a FAQ or a section for the
552- :ref: `installing-faq ` page. Are you a digital signal processing wizard?
553- Write a tutorial on the signal analysis plotting functions like
554- :func: `~matplotlib.pyplot.xcorr `, :func: `~matplotlib.pyplot.psd ` and
555- :func: `~matplotlib.pyplot.specgram `. Do you use Matplotlib with
556- `django <https://www.djangoproject.com/ >`_ or other popular web
557- application servers? Write a FAQ or tutorial and we'll find a place
558- for it in the :ref: `users-guide-index `. And so on... I think you get the
559- idea.
560-
561- Matplotlib is documented using the `sphinx
562- <http://www.sphinx-doc.org/en/stable/> `_ extensions to restructured text
563- `(ReST) <http://docutils.sourceforge.net/rst.html >`_. sphinx is an
564- extensible python framework for documentation projects which generates
565- HTML and PDF, and is pretty easy to write; you can see the source for this
566- document or any page on this site by clicking on the *Show Source * link
567- at the end of the page in the sidebar.
568-
569- The sphinx website is a good resource for learning sphinx, but we have
570- put together a cheat-sheet at :ref: `documenting-matplotlib ` which
571- shows you how to get started, and outlines the Matplotlib conventions
572- and extensions, e.g., for including plots directly from external code in
573- your documents.
574-
575- Once your documentation contributions are working (and hopefully
576- tested by actually *building * the docs) you can submit them as a patch
577- against git. See :ref: `install-git ` and :ref: `pr-guidelines `.
578- Looking for something to do? Search for `TODO <../search.html?q=todo >`_
579- or look at the open issues on github.
580-
581-
582530.. _howto-webapp :
583531
584532How to use Matplotlib in a web application server
0 commit comments