mirror of
https://github.com/readthedocs/sphinx_rtd_theme.git
synced 2025-02-25 18:55:21 -06:00
Demodocs: move the rest of the example from the index page
This commit is contained in:
@@ -1,7 +1,46 @@
|
||||
|
||||
*********************
|
||||
:mod:`test_py_module`
|
||||
=====================
|
||||
*********************
|
||||
|
||||
.. automodule:: test_py_module.test
|
||||
:members:
|
||||
:private-members:
|
||||
:special-members:
|
||||
|
||||
|
||||
Optional parameter args
|
||||
=======================
|
||||
|
||||
At this point optional parameters `cannot be generated from code`_.
|
||||
However, some projects will manually do it, like so:
|
||||
|
||||
This example comes from `django-payments module docs`_.
|
||||
|
||||
.. class:: payments.dotpay.DotpayProvider(seller_id, pin[, channel=0[, lock=False], lang='pl'])
|
||||
|
||||
This backend implements payments using a popular Polish gateway, `Dotpay.pl <http://www.dotpay.pl>`_.
|
||||
|
||||
Due to API limitations there is no support for transferring purchased items.
|
||||
|
||||
|
||||
:param seller_id: Seller ID assigned by Dotpay
|
||||
:param pin: PIN assigned by Dotpay
|
||||
:param channel: Default payment channel (consult reference guide)
|
||||
:param lang: UI language
|
||||
:param lock: Whether to disable channels other than the default selected above
|
||||
|
||||
.. _cannot be generated from code: https://groups.google.com/forum/#!topic/sphinx-users/_qfsVT5Vxpw
|
||||
.. _django-payments module docs: http://django-payments.readthedocs.org/en/latest/modules.html#payments.authorizenet.AuthorizeNetProvide
|
||||
|
||||
|
||||
Data
|
||||
====
|
||||
|
||||
.. data:: Data_item_1
|
||||
Data_item_2
|
||||
Data_item_3
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Fusce congue elit eu hendrerit mattis.
|
||||
|
||||
Some data link :data:`Data_item_1`.
|
||||
|
||||
@@ -27,6 +27,10 @@ Character-level inline markup is also possible (although exceedingly ugly!)
|
||||
in *re*\ ``Structured``\ *Text*. Problems are indicated by |problematic| text
|
||||
(generated by processing errors; this one is intentional).
|
||||
|
||||
Also with ``sphinx.ext.autodoc``, which I use in the demo,
|
||||
I can link to :class:`test_py_module.test.Foo`.
|
||||
It will link you right my code documentation for it.
|
||||
|
||||
The default role for interpreted text is `Title Reference`. Here are
|
||||
some explicit interpreted text roles: a PEP reference (:PEP:`287`); an
|
||||
RFC reference (:RFC:`2822`); a :sub:`subscript`; a :sup:`superscript`;
|
||||
|
||||
@@ -26,60 +26,3 @@ Contents
|
||||
long
|
||||
|
||||
You can also read the :ref:`genindex`
|
||||
|
||||
Optional parameter args
|
||||
=======================
|
||||
|
||||
At this point optional parameters `cannot be generated from code`_.
|
||||
However, some projects will manually do it, like so:
|
||||
|
||||
This example comes from `django-payments module docs`_.
|
||||
|
||||
.. class:: payments.dotpay.DotpayProvider(seller_id, pin[, channel=0[, lock=False], lang='pl'])
|
||||
|
||||
This backend implements payments using a popular Polish gateway, `Dotpay.pl <http://www.dotpay.pl>`_.
|
||||
|
||||
Due to API limitations there is no support for transferring purchased items.
|
||||
|
||||
|
||||
:param seller_id: Seller ID assigned by Dotpay
|
||||
:param pin: PIN assigned by Dotpay
|
||||
:param channel: Default payment channel (consult reference guide)
|
||||
:param lang: UI language
|
||||
:param lock: Whether to disable channels other than the default selected above
|
||||
|
||||
.. _cannot be generated from code: https://groups.google.com/forum/#!topic/sphinx-users/_qfsVT5Vxpw
|
||||
.. _django-payments module docs: http://django-payments.readthedocs.org/en/latest/modules.html#payments.authorizenet.AuthorizeNetProvider
|
||||
|
||||
|
||||
Inline code and references
|
||||
==========================
|
||||
|
||||
`reStructuredText`_ is a markup language. It can use roles and
|
||||
declarations to turn reST into HTML.
|
||||
|
||||
In reST, ``*hello world*`` becomes ``<em>hello world</em>``. This is
|
||||
because a library called `Docutils`_ was able to parse the reST and use a
|
||||
``Writer`` to output it that way.
|
||||
|
||||
If I type ````an inline literal```` it will wrap it in ``<tt>``. You can
|
||||
see more details on the `Inline Markup`_ on the Docutils homepage.
|
||||
|
||||
Also with ``sphinx.ext.autodoc``, which I use in the demo, I can link to
|
||||
:class:`test_py_module.test.Foo`. It will link you right my code
|
||||
documentation for it.
|
||||
|
||||
.. _reStructuredText: http://docutils.sourceforge.net/rst.html
|
||||
.. _Docutils: http://docutils.sourceforge.net/
|
||||
.. _Inline Markup: http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#inline-markup
|
||||
|
||||
Data
|
||||
====
|
||||
|
||||
.. data:: Data_item_1
|
||||
Data_item_2
|
||||
Data_item_3
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Fusce congue elit eu hendrerit mattis.
|
||||
|
||||
Some data link :data:`Data_item_1`.
|
||||
|
||||
Reference in New Issue
Block a user