[taler-docs] branch master updated: fix index

[gnunet]

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new d45af5c  fix index
d45af5c is described below

commit d45af5cacdf719c368af806619405f2dd1d2275b
Author: Florian Dold <address@hidden>
AuthorDate: Thu Apr 23 16:47:27 2020 +0530

    fix index
---
 genindex.rst                    |  2 ++
 index.rst                       |  1 +
 taler-merchant-api-tutorial.rst | 18 +++++++++++-------
 3 files changed, 14 insertions(+), 7 deletions(-)

diff --git a/genindex.rst b/genindex.rst
new file mode 100644
index 0000000..98f0d6e
--- /dev/null
+++ b/genindex.rst
@@ -0,0 +1,2 @@
+Complete Index
+==============
diff --git a/index.rst b/index.rst
index 2ead8f2..1a4d56c 100644
--- a/index.rst
+++ b/index.rst
@@ -66,6 +66,7 @@ Documentation Overview
   libeufin/index
   global-licensing
   manindex
+  genindex
 
 .. toctree::
   :hidden:
diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst
index 438c1cd..34064a0 100644
--- a/taler-merchant-api-tutorial.rst
+++ b/taler-merchant-api-tutorial.rst
@@ -80,11 +80,12 @@ Some functionality of the backend (the “public interface“) 
is also
 exposed to the customer’s browser directly. In the HTTP API, all public
 endpoints are prefixed with ``/public/``.
 
+
+.. index:: sandbox, authorization
+
 Public Sandbox Backend and Authentication
 -----------------------------------------
 
-:keywords: sandbox
-:keywords: authorization
 How the frontend authenticates to the Taler backend depends on the
 configuration. See Taler Merchant Operating Manual.
 
@@ -107,10 +108,11 @@ The sandbox backend https://backend.demo.taler.net/ uses 
``KUDOS`` as an
 imaginary currency. Coins denominated in ``KUDOS`` can be withdrawn from
 https://bank.demo.taler.net/.
 
+.. index:: instance
+
 Merchant Instances
 ------------------
 
-:keywords: instance
 The same Taler merchant backend server can be used by multiple separate
 merchants that are separate business entities. Each of these separate
 business entities is called a *merchant instance*, and is identified by
@@ -136,10 +138,11 @@ not affiliated with or officially approved by the 
respective projects.
 Accepting a Simple Payment
 ==========================
 
+.. index:: order
+
 Creating an Order for a Payment
 -------------------------------
 
-:keywords: order
 Payments in Taler revolve around an *order*, which is a machine-readable
 description of the business transaction for which the payment is to be
 made. Before accepting a Taler payment as a merchant you must create
@@ -225,11 +228,11 @@ usually needs to trigger the business logic for the 
merchant to fulfill
 the merchant’s obligations under the contract.
 
 .. _Giving-Refunds:
+.. index:: refunds
 
 Giving Refunds
 ==============
 
-:keywords: refunds
 A refund in GNU Taler is a way to “undo” a payment. It needs to be
 authorized by the merchant. Refunds can be for any fraction of the
 original amount paid, but they cannot exceed the original payment.
@@ -275,10 +278,11 @@ This code snipped illustrates giving a refund:
    <Response [200]>
 
 
+.. index:: repurchase
+
 Repurchase detection and fulfillment URLs
 =========================================
 
-:keywords: repurchase
 A possible problem for merchants selling access to digital articles
 is that a customer may have paid for an article on one device, but
 may then want to read it on a different device, possibly one that
@@ -317,11 +321,11 @@ unique.
 
 
 .. _Giving-Customers-Tips:
+.. index:: tips
 
 Giving Customers Tips
 =====================
 
-:keywords: tips
 GNU Taler allows Web sites to grant small amounts directly to the
 visitor. The idea is that some sites may want incentivize actions such
 as filling out a survey or trying a new feature. It is important to note

-- 
To stop receiving notification emails like this one, please contact
address@hidden.