commit eea346162b9ba78c9f4b0f48b9c2b2bcda425ecd
parent 996140163d18824529c8f7aef6d3260a321e24b9
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
Date: Wed, 25 Nov 2020 12:21:39 -0500
convert from table @item to @cindex: ‘frontend’, ‘backend’
Diffstat:
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst
@@ -78,18 +78,18 @@ Architecture overview
The Taler software stack for a merchant consists of the following main
components:
-- frontend
+.. index:: frontend
- A frontend which interacts with the customer’s browser. The frontend
+- A frontend which interacts with the customer’s browser. The frontend
enables the customer to build a shopping cart and place an order.
Upon payment, it triggers the respective business logic to satisfy
the order. This component is not included with Taler, but rather
assumed to exist at the merchant. This tutorial describes how to
develop a Taler frontend.
-- backend
+.. index:: backend
- A Taler-specific payment backend which makes it easy for the frontend
+- A Taler-specific payment backend which makes it easy for the frontend
to process financial transactions with Taler. For this tutorial, you
will use a public sandbox backend. For production use, you must
either set up your own backend or ask another person to do so for
