Fix the install button that Google broke

See https://developer.chrome.com/extensions/inline_faq

8 files changed, 1128 insertions, 27 deletions

diff --git a/locale/de/LC_MESSAGES/messages.po b/locale/de/LC_MESSAGES/messages.po
index cd3a28b..4d7b47f 100644
--- a/locale/de/LC_MESSAGES/messages.po
+++ b/locale/de/LC_MESSAGES/messages.po
@@ -2,7 +2,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2018-06-12 22:03+0200\n"
+"POT-Creation-Date: 2019-01-16 23:15+0100\n"
 "PO-Revision-Date: 2017-06-02 09:46+0100\n"
 "Last-Translator: Stefan Kügel <skuegel@web.de>\n"
 "Language-Team: de <LL@li.org, de@taler.net>\n"
@@ -1720,6 +1720,157 @@ msgstr ""
 "Wechselstuben an Geschäftsbanken sowie die Einkünfte der Wechselstuben aus "
 "Transaktionsgebühren"
 
+#: gsoc-codeless.html.j2:5
+msgid "GSoC 2018: Codeless Payment"
+msgstr ""
+
+#: gsoc-codeless.html.j2:6
+msgid ""
+"Implemented by Shivam Kohli as part of GSoC 2018 under the mentoring and "
+"guidance of Florian Dold."
+msgstr ""
+
+#: gsoc-codeless.html.j2:12
+#, fuzzy
+#| msgid "Taler system overview"
+msgid "Overview"
+msgstr "Das Taler-System im Überblick"
+
+#: gsoc-codeless.html.j2:14
+msgid ""
+"Codeless payment is a component that sits between the seller's frontend and "
+"the GNU Taler merchant backend. This component has a web interface, where "
+"payment buttons are configured. Registered merchants can manage their "
+"inventory and simultaneously create a 'Buy Now' button for a specific "
+"product. This code can be directly copy pasted on the seller's frontend and "
+"can be used for 'Pay with Taler'."
+msgstr ""
+
+#: gsoc-codeless.html.j2:23
+msgid "Use Cases"
+msgstr ""
+
+#: gsoc-codeless.html.j2:24
+msgid "The various use cases and features of codeless payment are:"
+msgstr ""
+
+#: gsoc-codeless.html.j2:28
+msgid ""
+"The primary use case is the registration of the merchant. The codeless "
+"payment backend provides a secure django authenticated login to the "
+"merchant. The registered merchant can add inventory (both digital as well as "
+"physical) in their stocks. They can manage inventory and simultaneously "
+"create a 'Buy Now' button for the product. The merchant also monitors the "
+"orders placed and updates the status of the order which helps in shipment "
+"tracking."
+msgstr ""
+
+#: gsoc-codeless.html.j2:33
+msgid ""
+"Merchant has the flexibility to add two types of inventory as follows: <ul> "
+"<li>The merchant can upload digital inventory (like a PDF or HTML page) via "
+"the codeless payments frontend and the user can then purchase it and view "
+"the version hosted by the codeless payment frontend.</li> <li>The merchant "
+"can add any physical inventory available in his stocks. While adding these "
+"inventory, the seller is prompted to add minimum quantity of product that is "
+"required to be maintained in the stock. Whenever the stocks run below this "
+"limit the seller would be notified (currently this feature has not been "
+"added but soon email notification would be added).</li> </ul>"
+msgstr ""
+
+#: gsoc-codeless.html.j2:42
+msgid ""
+"The buyers will access the seller's frontend where the code for the 'Buy "
+"Now' button is present. When this button is triggered, they are redirected "
+"to codeless payment backend and eventually redirected to the payment page. "
+"After successful payment, the buyer can also track their shipment for "
+"physical products or view the digital version hosted by the codeless payment "
+"frontend."
+msgstr ""
+
+#: gsoc-codeless.html.j2:47
+msgid ""
+"The other use case of the codeless payment backend is to handle the event "
+"when the 'Buy Now' button is triggered on the seller's frontend. To perform "
+"the payment the backend communicates with merchant backend api. After "
+"successful payment, the users are redirected to the fulfilment page."
+msgstr ""
+
+#: gsoc-codeless.html.j2:53
+msgid "Dynamic Merchant Instance"
+msgstr ""
+
+#: gsoc-codeless.html.j2:57
+msgid "Use Case Diagram"
+msgstr ""
+
+#: gsoc-codeless.html.j2:63
+msgid "Link to the contributions made"
+msgstr ""
+
+#: gsoc-codeless.html.j2:66
+msgid "Codeless Payment Backend"
+msgstr ""
+
+#: gsoc-codeless.html.j2:68
+msgid "Documentation to dynamically manage Merchant Instances"
+msgstr ""
+
+#: gsoc-codeless.html.j2:77
+msgid "Future Work"
+msgstr ""
+
+#: gsoc-codeless.html.j2:79
+msgid ""
+"The backend of codeless payment is very robust and can be easily extended as "
+"per the requirements. It is adaptive to add new features to this framework. "
+"But as per the discussion and the scope of this project, there are various "
+"features that will be soon added in the Codeless Merchant Backend. The list "
+"of future work is as follows:"
+msgstr ""
+
+#: gsoc-codeless.html.j2:84
+msgid ""
+"To send email notification to the merchant when the stocks run below a "
+"certain limit. The minimum quantity required to be maintained in the stocks "
+"is currently taken from the merchant(specific to each product) but no such "
+"notification system is designed."
+msgstr ""
+
+#: gsoc-codeless.html.j2:90
+msgid ""
+"To add API access to the merchant backend via the codeless payment service. "
+"Basically, it would be used as a hosting platform for multiple merchants. "
+"There would be an additional user interface part in the codeless payment "
+"service where a logged-in merchant can generate an API key. This API key can "
+"be used to access the functionality of the merchant backend in a controlled "
+"way. After requesting an API key, the page would display the generated key "
+"and a base URL for the API to use by the seller, which is handled by the "
+"codeless payments service."
+msgstr ""
+
+#: gsoc-codeless.html.j2:96
+msgid ""
+"Mapping every seller account to a separate merchant backend instance. This "
+"is not required for a simple version of codeless payments, but as soon as "
+"API access for sellers, this is a useful feature. The codeless payment "
+"service then can also double as a hosting service for merchants."
+msgstr ""
+
+#: gsoc-codeless.html.j2:102
+msgid ""
+"To add various analytics for the merchant. Various analysis could be "
+"performed on the orders placed for the respective merchant. Some of the "
+"analysis that can be performed are displaying the most frequently purchased "
+"product, some insights about the shipment tracking, analysis of products "
+"based on delivery location, etc. For this part, dicussions and some more "
+"research have to be done before proceeding to the implementation."
+msgstr ""
+
+#: gsoc-codeless.html.j2:114
+msgid "Screenshots"
+msgstr ""
+
 #: index.html.j2:6
 #, fuzzy
 #| msgid "GNU Taler"
@@ -2373,7 +2524,7 @@ msgstr ""
 "die Überweisungen an Girokonten der Geschäftsbanken mit den genauen "
 "Bedingungen jedes Kaufvertrags und nach Geschäftsvorfällen geordnet anzeigen."
 
-#: news.html.j2.inc:11
+#: news.html.j2.inc:9
 msgid "More news"
 msgstr ""
 
@@ -2391,6 +2542,10 @@ msgstr ""
 msgid "GNU Taler in the Press"
 msgstr "Taler in den Medien"
 
+#: schemafuzz.html.j2:6
+msgid "SchemaFuzz"
+msgstr ""
+
 #: common/base.j2:5
 msgid "GNU Taler"
 msgstr "Das Taler-Bezahlsystem"
@@ -2475,6 +2630,10 @@ msgstr "Entwickler"
 msgid "Copyright for Contributors"
 msgstr ""
 
+#: common/navigation.j2.inc:17
+msgid "Gsoc 2018: Codeless Payments"
+msgstr ""
+
 #~ msgid "Performance Analysis"
 #~ msgstr "Performanceanalyse"
 
diff --git a/locale/en/LC_MESSAGES/messages.po b/locale/en/LC_MESSAGES/messages.po
index 44ddeaf..462f643 100644
--- a/locale/en/LC_MESSAGES/messages.po
+++ b/locale/en/LC_MESSAGES/messages.po
@@ -2,7 +2,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2018-06-12 22:03+0200\n"
+"POT-Creation-Date: 2019-01-16 23:15+0100\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: en <LL@li.org>\n"
@@ -1046,6 +1046,155 @@ msgid ""
 "fees."
 msgstr ""
 
+#: gsoc-codeless.html.j2:5
+msgid "GSoC 2018: Codeless Payment"
+msgstr ""
+
+#: gsoc-codeless.html.j2:6
+msgid ""
+"Implemented by Shivam Kohli as part of GSoC 2018 under the mentoring and "
+"guidance of Florian Dold."
+msgstr ""
+
+#: gsoc-codeless.html.j2:12
+msgid "Overview"
+msgstr ""
+
+#: gsoc-codeless.html.j2:14
+msgid ""
+"Codeless payment is a component that sits between the seller's frontend and "
+"the GNU Taler merchant backend. This component has a web interface, where "
+"payment buttons are configured. Registered merchants can manage their "
+"inventory and simultaneously create a 'Buy Now' button for a specific "
+"product. This code can be directly copy pasted on the seller's frontend and "
+"can be used for 'Pay with Taler'."
+msgstr ""
+
+#: gsoc-codeless.html.j2:23
+msgid "Use Cases"
+msgstr ""
+
+#: gsoc-codeless.html.j2:24
+msgid "The various use cases and features of codeless payment are:"
+msgstr ""
+
+#: gsoc-codeless.html.j2:28
+msgid ""
+"The primary use case is the registration of the merchant. The codeless "
+"payment backend provides a secure django authenticated login to the "
+"merchant. The registered merchant can add inventory (both digital as well as "
+"physical) in their stocks. They can manage inventory and simultaneously "
+"create a 'Buy Now' button for the product. The merchant also monitors the "
+"orders placed and updates the status of the order which helps in shipment "
+"tracking."
+msgstr ""
+
+#: gsoc-codeless.html.j2:33
+msgid ""
+"Merchant has the flexibility to add two types of inventory as follows: <ul> "
+"<li>The merchant can upload digital inventory (like a PDF or HTML page) via "
+"the codeless payments frontend and the user can then purchase it and view "
+"the version hosted by the codeless payment frontend.</li> <li>The merchant "
+"can add any physical inventory available in his stocks. While adding these "
+"inventory, the seller is prompted to add minimum quantity of product that is "
+"required to be maintained in the stock. Whenever the stocks run below this "
+"limit the seller would be notified (currently this feature has not been "
+"added but soon email notification would be added).</li> </ul>"
+msgstr ""
+
+#: gsoc-codeless.html.j2:42
+msgid ""
+"The buyers will access the seller's frontend where the code for the 'Buy "
+"Now' button is present. When this button is triggered, they are redirected "
+"to codeless payment backend and eventually redirected to the payment page. "
+"After successful payment, the buyer can also track their shipment for "
+"physical products or view the digital version hosted by the codeless payment "
+"frontend."
+msgstr ""
+
+#: gsoc-codeless.html.j2:47
+msgid ""
+"The other use case of the codeless payment backend is to handle the event "
+"when the 'Buy Now' button is triggered on the seller's frontend. To perform "
+"the payment the backend communicates with merchant backend api. After "
+"successful payment, the users are redirected to the fulfilment page."
+msgstr ""
+
+#: gsoc-codeless.html.j2:53
+msgid "Dynamic Merchant Instance"
+msgstr ""
+
+#: gsoc-codeless.html.j2:57
+msgid "Use Case Diagram"
+msgstr ""
+
+#: gsoc-codeless.html.j2:63
+msgid "Link to the contributions made"
+msgstr ""
+
+#: gsoc-codeless.html.j2:66
+msgid "Codeless Payment Backend"
+msgstr ""
+
+#: gsoc-codeless.html.j2:68
+msgid "Documentation to dynamically manage Merchant Instances"
+msgstr ""
+
+#: gsoc-codeless.html.j2:77
+msgid "Future Work"
+msgstr ""
+
+#: gsoc-codeless.html.j2:79
+msgid ""
+"The backend of codeless payment is very robust and can be easily extended as "
+"per the requirements. It is adaptive to add new features to this framework. "
+"But as per the discussion and the scope of this project, there are various "
+"features that will be soon added in the Codeless Merchant Backend. The list "
+"of future work is as follows:"
+msgstr ""
+
+#: gsoc-codeless.html.j2:84
+msgid ""
+"To send email notification to the merchant when the stocks run below a "
+"certain limit. The minimum quantity required to be maintained in the stocks "
+"is currently taken from the merchant(specific to each product) but no such "
+"notification system is designed."
+msgstr ""
+
+#: gsoc-codeless.html.j2:90
+msgid ""
+"To add API access to the merchant backend via the codeless payment service. "
+"Basically, it would be used as a hosting platform for multiple merchants. "
+"There would be an additional user interface part in the codeless payment "
+"service where a logged-in merchant can generate an API key. This API key can "
+"be used to access the functionality of the merchant backend in a controlled "
+"way. After requesting an API key, the page would display the generated key "
+"and a base URL for the API to use by the seller, which is handled by the "
+"codeless payments service."
+msgstr ""
+
+#: gsoc-codeless.html.j2:96
+msgid ""
+"Mapping every seller account to a separate merchant backend instance. This "
+"is not required for a simple version of codeless payments, but as soon as "
+"API access for sellers, this is a useful feature. The codeless payment "
+"service then can also double as a hosting service for merchants."
+msgstr ""
+
+#: gsoc-codeless.html.j2:102
+msgid ""
+"To add various analytics for the merchant. Various analysis could be "
+"performed on the orders placed for the respective merchant. Some of the "
+"analysis that can be performed are displaying the most frequently purchased "
+"product, some insights about the shipment tracking, analysis of products "
+"based on delivery location, etc. For this part, dicussions and some more "
+"research have to be done before proceeding to the implementation."
+msgstr ""
+
+#: gsoc-codeless.html.j2:114
+msgid "Screenshots"
+msgstr ""
+
 #: index.html.j2:6
 msgid "GNU Taler logo"
 msgstr ""
@@ -1382,7 +1531,7 @@ msgid ""
 "each contract."
 msgstr ""
 
-#: news.html.j2.inc:11
+#: news.html.j2.inc:9
 msgid "More news"
 msgstr ""
 
@@ -1398,6 +1547,10 @@ msgstr ""
 msgid "GNU Taler in the Press"
 msgstr ""
 
+#: schemafuzz.html.j2:6
+msgid "SchemaFuzz"
+msgstr ""
+
 #: common/base.j2:5
 msgid "GNU Taler"
 msgstr ""
@@ -1467,3 +1620,7 @@ msgstr ""
 #: common/navigation.j2.inc:15
 msgid "Copyright for Contributors"
 msgstr ""
+
+#: common/navigation.j2.inc:17
+msgid "Gsoc 2018: Codeless Payments"
+msgstr ""
diff --git a/locale/es/LC_MESSAGES/messages.po b/locale/es/LC_MESSAGES/messages.po
index 87a1c18..a5ee6ec 100644
--- a/locale/es/LC_MESSAGES/messages.po
+++ b/locale/es/LC_MESSAGES/messages.po
@@ -2,7 +2,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2018-06-12 22:03+0200\n"
+"POT-Creation-Date: 2019-01-16 23:15+0100\n"
 "PO-Revision-Date: 2017-08-10 06:24+0200\n"
 "Last-Translator: \n"
 "Language-Team: es <LL@li.org>\n"
@@ -1398,6 +1398,157 @@ msgstr ""
 "detalles de las operaciones de depósito realizadas por los comerciantes con "
 "la plataforma de intercambio."
 
+#: gsoc-codeless.html.j2:5
+msgid "GSoC 2018: Codeless Payment"
+msgstr ""
+
+#: gsoc-codeless.html.j2:6
+msgid ""
+"Implemented by Shivam Kohli as part of GSoC 2018 under the mentoring and "
+"guidance of Florian Dold."
+msgstr ""
+
+#: gsoc-codeless.html.j2:12
+#, fuzzy
+#| msgid "system overview"
+msgid "Overview"
+msgstr "Diagrama general del sistema"
+
+#: gsoc-codeless.html.j2:14
+msgid ""
+"Codeless payment is a component that sits between the seller's frontend and "
+"the GNU Taler merchant backend. This component has a web interface, where "
+"payment buttons are configured. Registered merchants can manage their "
+"inventory and simultaneously create a 'Buy Now' button for a specific "
+"product. This code can be directly copy pasted on the seller's frontend and "
+"can be used for 'Pay with Taler'."
+msgstr ""
+
+#: gsoc-codeless.html.j2:23
+msgid "Use Cases"
+msgstr ""
+
+#: gsoc-codeless.html.j2:24
+msgid "The various use cases and features of codeless payment are:"
+msgstr ""
+
+#: gsoc-codeless.html.j2:28
+msgid ""
+"The primary use case is the registration of the merchant. The codeless "
+"payment backend provides a secure django authenticated login to the "
+"merchant. The registered merchant can add inventory (both digital as well as "
+"physical) in their stocks. They can manage inventory and simultaneously "
+"create a 'Buy Now' button for the product. The merchant also monitors the "
+"orders placed and updates the status of the order which helps in shipment "
+"tracking."
+msgstr ""
+
+#: gsoc-codeless.html.j2:33
+msgid ""
+"Merchant has the flexibility to add two types of inventory as follows: <ul> "
+"<li>The merchant can upload digital inventory (like a PDF or HTML page) via "
+"the codeless payments frontend and the user can then purchase it and view "
+"the version hosted by the codeless payment frontend.</li> <li>The merchant "
+"can add any physical inventory available in his stocks. While adding these "
+"inventory, the seller is prompted to add minimum quantity of product that is "
+"required to be maintained in the stock. Whenever the stocks run below this "
+"limit the seller would be notified (currently this feature has not been "
+"added but soon email notification would be added).</li> </ul>"
+msgstr ""
+
+#: gsoc-codeless.html.j2:42
+msgid ""
+"The buyers will access the seller's frontend where the code for the 'Buy "
+"Now' button is present. When this button is triggered, they are redirected "
+"to codeless payment backend and eventually redirected to the payment page. "
+"After successful payment, the buyer can also track their shipment for "
+"physical products or view the digital version hosted by the codeless payment "
+"frontend."
+msgstr ""
+
+#: gsoc-codeless.html.j2:47
+msgid ""
+"The other use case of the codeless payment backend is to handle the event "
+"when the 'Buy Now' button is triggered on the seller's frontend. To perform "
+"the payment the backend communicates with merchant backend api. After "
+"successful payment, the users are redirected to the fulfilment page."
+msgstr ""
+
+#: gsoc-codeless.html.j2:53
+msgid "Dynamic Merchant Instance"
+msgstr ""
+
+#: gsoc-codeless.html.j2:57
+msgid "Use Case Diagram"
+msgstr ""
+
+#: gsoc-codeless.html.j2:63
+msgid "Link to the contributions made"
+msgstr ""
+
+#: gsoc-codeless.html.j2:66
+msgid "Codeless Payment Backend"
+msgstr ""
+
+#: gsoc-codeless.html.j2:68
+msgid "Documentation to dynamically manage Merchant Instances"
+msgstr ""
+
+#: gsoc-codeless.html.j2:77
+msgid "Future Work"
+msgstr ""
+
+#: gsoc-codeless.html.j2:79
+msgid ""
+"The backend of codeless payment is very robust and can be easily extended as "
+"per the requirements. It is adaptive to add new features to this framework. "
+"But as per the discussion and the scope of this project, there are various "
+"features that will be soon added in the Codeless Merchant Backend. The list "
+"of future work is as follows:"
+msgstr ""
+
+#: gsoc-codeless.html.j2:84
+msgid ""
+"To send email notification to the merchant when the stocks run below a "
+"certain limit. The minimum quantity required to be maintained in the stocks "
+"is currently taken from the merchant(specific to each product) but no such "
+"notification system is designed."
+msgstr ""
+
+#: gsoc-codeless.html.j2:90
+msgid ""
+"To add API access to the merchant backend via the codeless payment service. "
+"Basically, it would be used as a hosting platform for multiple merchants. "
+"There would be an additional user interface part in the codeless payment "
+"service where a logged-in merchant can generate an API key. This API key can "
+"be used to access the functionality of the merchant backend in a controlled "
+"way. After requesting an API key, the page would display the generated key "
+"and a base URL for the API to use by the seller, which is handled by the "
+"codeless payments service."
+msgstr ""
+
+#: gsoc-codeless.html.j2:96
+msgid ""
+"Mapping every seller account to a separate merchant backend instance. This "
+"is not required for a simple version of codeless payments, but as soon as "
+"API access for sellers, this is a useful feature. The codeless payment "
+"service then can also double as a hosting service for merchants."
+msgstr ""
+
+#: gsoc-codeless.html.j2:102
+msgid ""
+"To add various analytics for the merchant. Various analysis could be "
+"performed on the orders placed for the respective merchant. Some of the "
+"analysis that can be performed are displaying the most frequently purchased "
+"product, some insights about the shipment tracking, analysis of products "
+"based on delivery location, etc. For this part, dicussions and some more "
+"research have to be done before proceeding to the implementation."
+msgstr ""
+
+#: gsoc-codeless.html.j2:114
+msgid "Screenshots"
+msgstr ""
+
 #: index.html.j2:6
 msgid "GNU Taler logo"
 msgstr "Logotipo de GNU Taler"
@@ -1878,7 +2029,7 @@ msgstr ""
 "<b>relacionar</b> las transferencias bancarias con los pagos electrónicos "
 "correspondientes, incluyendo los términos exactos de cada contrato."
 
-#: news.html.j2.inc:11
+#: news.html.j2.inc:9
 msgid "More news"
 msgstr ""
 
@@ -1896,6 +2047,10 @@ msgstr ""
 msgid "GNU Taler in the Press"
 msgstr "GNU Taler en la Prensa"
 
+#: schemafuzz.html.j2:6
+msgid "SchemaFuzz"
+msgstr ""
+
 #: common/base.j2:5
 msgid "GNU Taler"
 msgstr "GNU Taler"
@@ -1968,6 +2123,10 @@ msgstr "Introducción para desarrolladores"
 msgid "Copyright for Contributors"
 msgstr "Copyright para contribuidores"
 
+#: common/navigation.j2.inc:17
+msgid "Gsoc 2018: Codeless Payments"
+msgstr ""
+
 #~ msgid "Performance Analysis"
 #~ msgstr "Performance"
 
diff --git a/locale/fr/LC_MESSAGES/messages.po b/locale/fr/LC_MESSAGES/messages.po
index 1b37abb..bae8c98 100644
--- a/locale/fr/LC_MESSAGES/messages.po
+++ b/locale/fr/LC_MESSAGES/messages.po
@@ -2,7 +2,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2018-06-12 22:03+0200\n"
+"POT-Creation-Date: 2019-01-16 23:15+0100\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: fr <LL@li.org>\n"
@@ -1070,6 +1070,157 @@ msgid ""
 "fees."
 msgstr ""
 
+#: gsoc-codeless.html.j2:5
+msgid "GSoC 2018: Codeless Payment"
+msgstr ""
+
+#: gsoc-codeless.html.j2:6
+msgid ""
+"Implemented by Shivam Kohli as part of GSoC 2018 under the mentoring and "
+"guidance of Florian Dold."
+msgstr ""
+
+#: gsoc-codeless.html.j2:12
+#, fuzzy
+#| msgid "Taler system overview"
+msgid "Overview"
+msgstr "Vue d'ensemble de Taler"
+
+#: gsoc-codeless.html.j2:14
+msgid ""
+"Codeless payment is a component that sits between the seller's frontend and "
+"the GNU Taler merchant backend. This component has a web interface, where "
+"payment buttons are configured. Registered merchants can manage their "
+"inventory and simultaneously create a 'Buy Now' button for a specific "
+"product. This code can be directly copy pasted on the seller's frontend and "
+"can be used for 'Pay with Taler'."
+msgstr ""
+
+#: gsoc-codeless.html.j2:23
+msgid "Use Cases"
+msgstr ""
+
+#: gsoc-codeless.html.j2:24
+msgid "The various use cases and features of codeless payment are:"
+msgstr ""
+
+#: gsoc-codeless.html.j2:28
+msgid ""
+"The primary use case is the registration of the merchant. The codeless "
+"payment backend provides a secure django authenticated login to the "
+"merchant. The registered merchant can add inventory (both digital as well as "
+"physical) in their stocks. They can manage inventory and simultaneously "
+"create a 'Buy Now' button for the product. The merchant also monitors the "
+"orders placed and updates the status of the order which helps in shipment "
+"tracking."
+msgstr ""
+
+#: gsoc-codeless.html.j2:33
+msgid ""
+"Merchant has the flexibility to add two types of inventory as follows: <ul> "
+"<li>The merchant can upload digital inventory (like a PDF or HTML page) via "
+"the codeless payments frontend and the user can then purchase it and view "
+"the version hosted by the codeless payment frontend.</li> <li>The merchant "
+"can add any physical inventory available in his stocks. While adding these "
+"inventory, the seller is prompted to add minimum quantity of product that is "
+"required to be maintained in the stock. Whenever the stocks run below this "
+"limit the seller would be notified (currently this feature has not been "
+"added but soon email notification would be added).</li> </ul>"
+msgstr ""
+
+#: gsoc-codeless.html.j2:42
+msgid ""
+"The buyers will access the seller's frontend where the code for the 'Buy "
+"Now' button is present. When this button is triggered, they are redirected "
+"to codeless payment backend and eventually redirected to the payment page. "
+"After successful payment, the buyer can also track their shipment for "
+"physical products or view the digital version hosted by the codeless payment "
+"frontend."
+msgstr ""
+
+#: gsoc-codeless.html.j2:47
+msgid ""
+"The other use case of the codeless payment backend is to handle the event "
+"when the 'Buy Now' button is triggered on the seller's frontend. To perform "
+"the payment the backend communicates with merchant backend api. After "
+"successful payment, the users are redirected to the fulfilment page."
+msgstr ""
+
+#: gsoc-codeless.html.j2:53
+msgid "Dynamic Merchant Instance"
+msgstr ""
+
+#: gsoc-codeless.html.j2:57
+msgid "Use Case Diagram"
+msgstr ""
+
+#: gsoc-codeless.html.j2:63
+msgid "Link to the contributions made"
+msgstr ""
+
+#: gsoc-codeless.html.j2:66
+msgid "Codeless Payment Backend"
+msgstr ""
+
+#: gsoc-codeless.html.j2:68
+msgid "Documentation to dynamically manage Merchant Instances"
+msgstr ""
+
+#: gsoc-codeless.html.j2:77
+msgid "Future Work"
+msgstr ""
+
+#: gsoc-codeless.html.j2:79
+msgid ""
+"The backend of codeless payment is very robust and can be easily extended as "
+"per the requirements. It is adaptive to add new features to this framework. "
+"But as per the discussion and the scope of this project, there are various "
+"features that will be soon added in the Codeless Merchant Backend. The list "
+"of future work is as follows:"
+msgstr ""
+
+#: gsoc-codeless.html.j2:84
+msgid ""
+"To send email notification to the merchant when the stocks run below a "
+"certain limit. The minimum quantity required to be maintained in the stocks "
+"is currently taken from the merchant(specific to each product) but no such "
+"notification system is designed."
+msgstr ""
+
+#: gsoc-codeless.html.j2:90
+msgid ""
+"To add API access to the merchant backend via the codeless payment service. "
+"Basically, it would be used as a hosting platform for multiple merchants. "
+"There would be an additional user interface part in the codeless payment "
+"service where a logged-in merchant can generate an API key. This API key can "
+"be used to access the functionality of the merchant backend in a controlled "
+"way. After requesting an API key, the page would display the generated key "
+"and a base URL for the API to use by the seller, which is handled by the "
+"codeless payments service."
+msgstr ""
+
+#: gsoc-codeless.html.j2:96
+msgid ""
+"Mapping every seller account to a separate merchant backend instance. This "
+"is not required for a simple version of codeless payments, but as soon as "
+"API access for sellers, this is a useful feature. The codeless payment "
+"service then can also double as a hosting service for merchants."
+msgstr ""
+
+#: gsoc-codeless.html.j2:102
+msgid ""
+"To add various analytics for the merchant. Various analysis could be "
+"performed on the orders placed for the respective merchant. Some of the "
+"analysis that can be performed are displaying the most frequently purchased "
+"product, some insights about the shipment tracking, analysis of products "
+"based on delivery location, etc. For this part, dicussions and some more "
+"research have to be done before proceeding to the implementation."
+msgstr ""
+
+#: gsoc-codeless.html.j2:114
+msgid "Screenshots"
+msgstr ""
+
 #: index.html.j2:6
 msgid "GNU Taler logo"
 msgstr ""
@@ -1410,7 +1561,7 @@ msgid ""
 "each contract."
 msgstr ""
 
-#: news.html.j2.inc:11
+#: news.html.j2.inc:9
 msgid "More news"
 msgstr ""
 
@@ -1426,6 +1577,10 @@ msgstr ""
 msgid "GNU Taler in the Press"
 msgstr ""
 
+#: schemafuzz.html.j2:6
+msgid "SchemaFuzz"
+msgstr ""
+
 #: common/base.j2:5
 msgid "GNU Taler"
 msgstr ""
@@ -1497,6 +1652,10 @@ msgstr ""
 msgid "Copyright for Contributors"
 msgstr ""
 
+#: common/navigation.j2.inc:17
+msgid "Gsoc 2018: Codeless Payments"
+msgstr ""
+
 #~ msgid "Performance Analysis"
 #~ msgstr "Analyse de performances"
 
diff --git a/locale/it/LC_MESSAGES/messages.po b/locale/it/LC_MESSAGES/messages.po
index fe32483..6d9c6bb 100644
--- a/locale/it/LC_MESSAGES/messages.po
+++ b/locale/it/LC_MESSAGES/messages.po
@@ -2,7 +2,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2018-06-12 22:03+0200\n"
+"POT-Creation-Date: 2019-01-16 23:15+0100\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: it <LL@li.org>\n"
@@ -1406,6 +1406,157 @@ msgstr ""
 "operazioni di deposito effettuate dai commercianti con il cambio, e il "
 "profitto del cambio dalle spese di transazione. "
 
+#: gsoc-codeless.html.j2:5
+msgid "GSoC 2018: Codeless Payment"
+msgstr ""
+
+#: gsoc-codeless.html.j2:6
+msgid ""
+"Implemented by Shivam Kohli as part of GSoC 2018 under the mentoring and "
+"guidance of Florian Dold."
+msgstr ""
+
+#: gsoc-codeless.html.j2:12
+#, fuzzy
+#| msgid "Taler system overview"
+msgid "Overview"
+msgstr "Panoramica del sistema"
+
+#: gsoc-codeless.html.j2:14
+msgid ""
+"Codeless payment is a component that sits between the seller's frontend and "
+"the GNU Taler merchant backend. This component has a web interface, where "
+"payment buttons are configured. Registered merchants can manage their "
+"inventory and simultaneously create a 'Buy Now' button for a specific "
+"product. This code can be directly copy pasted on the seller's frontend and "
+"can be used for 'Pay with Taler'."
+msgstr ""
+
+#: gsoc-codeless.html.j2:23
+msgid "Use Cases"
+msgstr ""
+
+#: gsoc-codeless.html.j2:24
+msgid "The various use cases and features of codeless payment are:"
+msgstr ""
+
+#: gsoc-codeless.html.j2:28
+msgid ""
+"The primary use case is the registration of the merchant. The codeless "
+"payment backend provides a secure django authenticated login to the "
+"merchant. The registered merchant can add inventory (both digital as well as "
+"physical) in their stocks. They can manage inventory and simultaneously "
+"create a 'Buy Now' button for the product. The merchant also monitors the "
+"orders placed and updates the status of the order which helps in shipment "
+"tracking."
+msgstr ""
+
+#: gsoc-codeless.html.j2:33
+msgid ""
+"Merchant has the flexibility to add two types of inventory as follows: <ul> "
+"<li>The merchant can upload digital inventory (like a PDF or HTML page) via "
+"the codeless payments frontend and the user can then purchase it and view "
+"the version hosted by the codeless payment frontend.</li> <li>The merchant "
+"can add any physical inventory available in his stocks. While adding these "
+"inventory, the seller is prompted to add minimum quantity of product that is "
+"required to be maintained in the stock. Whenever the stocks run below this "
+"limit the seller would be notified (currently this feature has not been "
+"added but soon email notification would be added).</li> </ul>"
+msgstr ""
+
+#: gsoc-codeless.html.j2:42
+msgid ""
+"The buyers will access the seller's frontend where the code for the 'Buy "
+"Now' button is present. When this button is triggered, they are redirected "
+"to codeless payment backend and eventually redirected to the payment page. "
+"After successful payment, the buyer can also track their shipment for "
+"physical products or view the digital version hosted by the codeless payment "
+"frontend."
+msgstr ""
+
+#: gsoc-codeless.html.j2:47
+msgid ""
+"The other use case of the codeless payment backend is to handle the event "
+"when the 'Buy Now' button is triggered on the seller's frontend. To perform "
+"the payment the backend communicates with merchant backend api. After "
+"successful payment, the users are redirected to the fulfilment page."
+msgstr ""
+
+#: gsoc-codeless.html.j2:53
+msgid "Dynamic Merchant Instance"
+msgstr ""
+
+#: gsoc-codeless.html.j2:57
+msgid "Use Case Diagram"
+msgstr ""
+
+#: gsoc-codeless.html.j2:63
+msgid "Link to the contributions made"
+msgstr ""
+
+#: gsoc-codeless.html.j2:66
+msgid "Codeless Payment Backend"
+msgstr ""
+
+#: gsoc-codeless.html.j2:68
+msgid "Documentation to dynamically manage Merchant Instances"
+msgstr ""
+
+#: gsoc-codeless.html.j2:77
+msgid "Future Work"
+msgstr ""
+
+#: gsoc-codeless.html.j2:79
+msgid ""
+"The backend of codeless payment is very robust and can be easily extended as "
+"per the requirements. It is adaptive to add new features to this framework. "
+"But as per the discussion and the scope of this project, there are various "
+"features that will be soon added in the Codeless Merchant Backend. The list "
+"of future work is as follows:"
+msgstr ""
+
+#: gsoc-codeless.html.j2:84
+msgid ""
+"To send email notification to the merchant when the stocks run below a "
+"certain limit. The minimum quantity required to be maintained in the stocks "
+"is currently taken from the merchant(specific to each product) but no such "
+"notification system is designed."
+msgstr ""
+
+#: gsoc-codeless.html.j2:90
+msgid ""
+"To add API access to the merchant backend via the codeless payment service. "
+"Basically, it would be used as a hosting platform for multiple merchants. "
+"There would be an additional user interface part in the codeless payment "
+"service where a logged-in merchant can generate an API key. This API key can "
+"be used to access the functionality of the merchant backend in a controlled "
+"way. After requesting an API key, the page would display the generated key "
+"and a base URL for the API to use by the seller, which is handled by the "
+"codeless payments service."
+msgstr ""
+
+#: gsoc-codeless.html.j2:96
+msgid ""
+"Mapping every seller account to a separate merchant backend instance. This "
+"is not required for a simple version of codeless payments, but as soon as "
+"API access for sellers, this is a useful feature. The codeless payment "
+"service then can also double as a hosting service for merchants."
+msgstr ""
+
+#: gsoc-codeless.html.j2:102
+msgid ""
+"To add various analytics for the merchant. Various analysis could be "
+"performed on the orders placed for the respective merchant. Some of the "
+"analysis that can be performed are displaying the most frequently purchased "
+"product, some insights about the shipment tracking, analysis of products "
+"based on delivery location, etc. For this part, dicussions and some more "
+"research have to be done before proceeding to the implementation."
+msgstr ""
+
+#: gsoc-codeless.html.j2:114
+msgid "Screenshots"
+msgstr ""
+
 #: index.html.j2:6
 #, fuzzy
 #| msgid "GNU Taler Bibliography"
@@ -1891,7 +2042,7 @@ msgstr ""
 "bonifici a set di transazioni commerciali, includendo i termini esatti di "
 "ogni contratto. "
 
-#: news.html.j2.inc:11
+#: news.html.j2.inc:9
 msgid "More news"
 msgstr "Altre notizie"
 
@@ -1907,6 +2058,10 @@ msgstr "Questa pagina documenta la storia di GNU Taler. "
 msgid "GNU Taler in the Press"
 msgstr "GNU Taler nella Stampa"
 
+#: schemafuzz.html.j2:6
+msgid "SchemaFuzz"
+msgstr ""
+
 #: common/base.j2:5
 msgid "GNU Taler"
 msgstr "GNU Taler"
@@ -1984,6 +2139,10 @@ msgstr "Introduzione per i programmatori"
 msgid "Copyright for Contributors"
 msgstr "Diritti d'autore per i collaboratori"
 
+#: common/navigation.j2.inc:17
+msgid "Gsoc 2018: Codeless Payments"
+msgstr ""
+
 #~ msgid "Performance Analysis"
 #~ msgstr "Analisi delle prestazioni"
 
diff --git a/locale/pt/LC_MESSAGES/messages.po b/locale/pt/LC_MESSAGES/messages.po
index acad0f8..e740846 100644
--- a/locale/pt/LC_MESSAGES/messages.po
+++ b/locale/pt/LC_MESSAGES/messages.po
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: GNU taler master\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2018-06-12 22:03+0200\n"
+"POT-Creation-Date: 2019-01-16 23:15+0100\n"
 "PO-Revision-Date: 2018-01-28 15:27-0200\n"
 "Last-Translator: Rafael Fontenelle <rafaelff@gnome.org>\n"
 "Language-Team: Brazilian Portuguese\n"
@@ -1365,6 +1365,157 @@ msgstr ""
 "depósito realizadas pelos comerciantes com o câmbio e a renda do câmbio de "
 "taxas de transação."
 
+#: gsoc-codeless.html.j2:5
+msgid "GSoC 2018: Codeless Payment"
+msgstr ""
+
+#: gsoc-codeless.html.j2:6
+msgid ""
+"Implemented by Shivam Kohli as part of GSoC 2018 under the mentoring and "
+"guidance of Florian Dold."
+msgstr ""
+
+#: gsoc-codeless.html.j2:12
+#, fuzzy
+#| msgid "system overview"
+msgid "Overview"
+msgstr "visão geral do sistema"
+
+#: gsoc-codeless.html.j2:14
+msgid ""
+"Codeless payment is a component that sits between the seller's frontend and "
+"the GNU Taler merchant backend. This component has a web interface, where "
+"payment buttons are configured. Registered merchants can manage their "
+"inventory and simultaneously create a 'Buy Now' button for a specific "
+"product. This code can be directly copy pasted on the seller's frontend and "
+"can be used for 'Pay with Taler'."
+msgstr ""
+
+#: gsoc-codeless.html.j2:23
+msgid "Use Cases"
+msgstr ""
+
+#: gsoc-codeless.html.j2:24
+msgid "The various use cases and features of codeless payment are:"
+msgstr ""
+
+#: gsoc-codeless.html.j2:28
+msgid ""
+"The primary use case is the registration of the merchant. The codeless "
+"payment backend provides a secure django authenticated login to the "
+"merchant. The registered merchant can add inventory (both digital as well as "
+"physical) in their stocks. They can manage inventory and simultaneously "
+"create a 'Buy Now' button for the product. The merchant also monitors the "
+"orders placed and updates the status of the order which helps in shipment "
+"tracking."
+msgstr ""
+
+#: gsoc-codeless.html.j2:33
+msgid ""
+"Merchant has the flexibility to add two types of inventory as follows: <ul> "
+"<li>The merchant can upload digital inventory (like a PDF or HTML page) via "
+"the codeless payments frontend and the user can then purchase it and view "
+"the version hosted by the codeless payment frontend.</li> <li>The merchant "
+"can add any physical inventory available in his stocks. While adding these "
+"inventory, the seller is prompted to add minimum quantity of product that is "
+"required to be maintained in the stock. Whenever the stocks run below this "
+"limit the seller would be notified (currently this feature has not been "
+"added but soon email notification would be added).</li> </ul>"
+msgstr ""
+
+#: gsoc-codeless.html.j2:42
+msgid ""
+"The buyers will access the seller's frontend where the code for the 'Buy "
+"Now' button is present. When this button is triggered, they are redirected "
+"to codeless payment backend and eventually redirected to the payment page. "
+"After successful payment, the buyer can also track their shipment for "
+"physical products or view the digital version hosted by the codeless payment "
+"frontend."
+msgstr ""
+
+#: gsoc-codeless.html.j2:47
+msgid ""
+"The other use case of the codeless payment backend is to handle the event "
+"when the 'Buy Now' button is triggered on the seller's frontend. To perform "
+"the payment the backend communicates with merchant backend api. After "
+"successful payment, the users are redirected to the fulfilment page."
+msgstr ""
+
+#: gsoc-codeless.html.j2:53
+msgid "Dynamic Merchant Instance"
+msgstr ""
+
+#: gsoc-codeless.html.j2:57
+msgid "Use Case Diagram"
+msgstr ""
+
+#: gsoc-codeless.html.j2:63
+msgid "Link to the contributions made"
+msgstr ""
+
+#: gsoc-codeless.html.j2:66
+msgid "Codeless Payment Backend"
+msgstr ""
+
+#: gsoc-codeless.html.j2:68
+msgid "Documentation to dynamically manage Merchant Instances"
+msgstr ""
+
+#: gsoc-codeless.html.j2:77
+msgid "Future Work"
+msgstr ""
+
+#: gsoc-codeless.html.j2:79
+msgid ""
+"The backend of codeless payment is very robust and can be easily extended as "
+"per the requirements. It is adaptive to add new features to this framework. "
+"But as per the discussion and the scope of this project, there are various "
+"features that will be soon added in the Codeless Merchant Backend. The list "
+"of future work is as follows:"
+msgstr ""
+
+#: gsoc-codeless.html.j2:84
+msgid ""
+"To send email notification to the merchant when the stocks run below a "
+"certain limit. The minimum quantity required to be maintained in the stocks "
+"is currently taken from the merchant(specific to each product) but no such "
+"notification system is designed."
+msgstr ""
+
+#: gsoc-codeless.html.j2:90
+msgid ""
+"To add API access to the merchant backend via the codeless payment service. "
+"Basically, it would be used as a hosting platform for multiple merchants. "
+"There would be an additional user interface part in the codeless payment "
+"service where a logged-in merchant can generate an API key. This API key can "
+"be used to access the functionality of the merchant backend in a controlled "
+"way. After requesting an API key, the page would display the generated key "
+"and a base URL for the API to use by the seller, which is handled by the "
+"codeless payments service."
+msgstr ""
+
+#: gsoc-codeless.html.j2:96
+msgid ""
+"Mapping every seller account to a separate merchant backend instance. This "
+"is not required for a simple version of codeless payments, but as soon as "
+"API access for sellers, this is a useful feature. The codeless payment "
+"service then can also double as a hosting service for merchants."
+msgstr ""
+
+#: gsoc-codeless.html.j2:102
+msgid ""
+"To add various analytics for the merchant. Various analysis could be "
+"performed on the orders placed for the respective merchant. Some of the "
+"analysis that can be performed are displaying the most frequently purchased "
+"product, some insights about the shipment tracking, analysis of products "
+"based on delivery location, etc. For this part, dicussions and some more "
+"research have to be done before proceeding to the implementation."
+msgstr ""
+
+#: gsoc-codeless.html.j2:114
+msgid "Screenshots"
+msgstr ""
+
 #: index.html.j2:6
 msgid "GNU Taler logo"
 msgstr "Logo do GNU Taler"
@@ -1825,7 +1976,7 @@ msgstr ""
 "transferências eletrônicas para conjuntos de transações comerciais, "
 "incluindo os termos exatos de cada contrato."
 
-#: news.html.j2.inc:11
+#: news.html.j2.inc:9
 msgid "More news"
 msgstr "Mais notícias"
 
@@ -1841,6 +1992,10 @@ msgstr "Essa página documenta o histórico do GNU Taler."
 msgid "GNU Taler in the Press"
 msgstr "GNU Taler na imprensa"
 
+#: schemafuzz.html.j2:6
+msgid "SchemaFuzz"
+msgstr ""
+
 #: common/base.j2:5
 msgid "GNU Taler"
 msgstr "GNU Taler"
@@ -1913,6 +2068,10 @@ msgstr "Introdução para desenvolvedores"
 msgid "Copyright for Contributors"
 msgstr "Direitos autorais para contribuidores"
 
+#: common/navigation.j2.inc:17
+msgid "Gsoc 2018: Codeless Payments"
+msgstr ""
+
 #~ msgid "Performance Analysis"
 #~ msgstr "Análise de desempenho"
 
diff --git a/locale/ru/LC_MESSAGES/messages.po b/locale/ru/LC_MESSAGES/messages.po
index 13bd530..82dea62 100644
--- a/locale/ru/LC_MESSAGES/messages.po
+++ b/locale/ru/LC_MESSAGES/messages.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2018-06-12 22:03+0200\n"
+"POT-Creation-Date: 2019-01-16 23:15+0100\n"
 "PO-Revision-Date: 2017-12-29 11:14+0100\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: ru <LL@li.org>\n"
@@ -1052,6 +1052,155 @@ msgid ""
 "fees."
 msgstr ""
 
+#: gsoc-codeless.html.j2:5
+msgid "GSoC 2018: Codeless Payment"
+msgstr ""
+
+#: gsoc-codeless.html.j2:6
+msgid ""
+"Implemented by Shivam Kohli as part of GSoC 2018 under the mentoring and "
+"guidance of Florian Dold."
+msgstr ""
+
+#: gsoc-codeless.html.j2:12
+msgid "Overview"
+msgstr ""
+
+#: gsoc-codeless.html.j2:14
+msgid ""
+"Codeless payment is a component that sits between the seller's frontend and "
+"the GNU Taler merchant backend. This component has a web interface, where "
+"payment buttons are configured. Registered merchants can manage their "
+"inventory and simultaneously create a 'Buy Now' button for a specific "
+"product. This code can be directly copy pasted on the seller's frontend and "
+"can be used for 'Pay with Taler'."
+msgstr ""
+
+#: gsoc-codeless.html.j2:23
+msgid "Use Cases"
+msgstr ""
+
+#: gsoc-codeless.html.j2:24
+msgid "The various use cases and features of codeless payment are:"
+msgstr ""
+
+#: gsoc-codeless.html.j2:28
+msgid ""
+"The primary use case is the registration of the merchant. The codeless "
+"payment backend provides a secure django authenticated login to the "
+"merchant. The registered merchant can add inventory (both digital as well as "
+"physical) in their stocks. They can manage inventory and simultaneously "
+"create a 'Buy Now' button for the product. The merchant also monitors the "
+"orders placed and updates the status of the order which helps in shipment "
+"tracking."
+msgstr ""
+
+#: gsoc-codeless.html.j2:33
+msgid ""
+"Merchant has the flexibility to add two types of inventory as follows: <ul> "
+"<li>The merchant can upload digital inventory (like a PDF or HTML page) via "
+"the codeless payments frontend and the user can then purchase it and view "
+"the version hosted by the codeless payment frontend.</li> <li>The merchant "
+"can add any physical inventory available in his stocks. While adding these "
+"inventory, the seller is prompted to add minimum quantity of product that is "
+"required to be maintained in the stock. Whenever the stocks run below this "
+"limit the seller would be notified (currently this feature has not been "
+"added but soon email notification would be added).</li> </ul>"
+msgstr ""
+
+#: gsoc-codeless.html.j2:42
+msgid ""
+"The buyers will access the seller's frontend where the code for the 'Buy "
+"Now' button is present. When this button is triggered, they are redirected "
+"to codeless payment backend and eventually redirected to the payment page. "
+"After successful payment, the buyer can also track their shipment for "
+"physical products or view the digital version hosted by the codeless payment "
+"frontend."
+msgstr ""
+
+#: gsoc-codeless.html.j2:47
+msgid ""
+"The other use case of the codeless payment backend is to handle the event "
+"when the 'Buy Now' button is triggered on the seller's frontend. To perform "
+"the payment the backend communicates with merchant backend api. After "
+"successful payment, the users are redirected to the fulfilment page."
+msgstr ""
+
+#: gsoc-codeless.html.j2:53
+msgid "Dynamic Merchant Instance"
+msgstr ""
+
+#: gsoc-codeless.html.j2:57
+msgid "Use Case Diagram"
+msgstr ""
+
+#: gsoc-codeless.html.j2:63
+msgid "Link to the contributions made"
+msgstr ""
+
+#: gsoc-codeless.html.j2:66
+msgid "Codeless Payment Backend"
+msgstr ""
+
+#: gsoc-codeless.html.j2:68
+msgid "Documentation to dynamically manage Merchant Instances"
+msgstr ""
+
+#: gsoc-codeless.html.j2:77
+msgid "Future Work"
+msgstr ""
+
+#: gsoc-codeless.html.j2:79
+msgid ""
+"The backend of codeless payment is very robust and can be easily extended as "
+"per the requirements. It is adaptive to add new features to this framework. "
+"But as per the discussion and the scope of this project, there are various "
+"features that will be soon added in the Codeless Merchant Backend. The list "
+"of future work is as follows:"
+msgstr ""
+
+#: gsoc-codeless.html.j2:84
+msgid ""
+"To send email notification to the merchant when the stocks run below a "
+"certain limit. The minimum quantity required to be maintained in the stocks "
+"is currently taken from the merchant(specific to each product) but no such "
+"notification system is designed."
+msgstr ""
+
+#: gsoc-codeless.html.j2:90
+msgid ""
+"To add API access to the merchant backend via the codeless payment service. "
+"Basically, it would be used as a hosting platform for multiple merchants. "
+"There would be an additional user interface part in the codeless payment "
+"service where a logged-in merchant can generate an API key. This API key can "
+"be used to access the functionality of the merchant backend in a controlled "
+"way. After requesting an API key, the page would display the generated key "
+"and a base URL for the API to use by the seller, which is handled by the "
+"codeless payments service."
+msgstr ""
+
+#: gsoc-codeless.html.j2:96
+msgid ""
+"Mapping every seller account to a separate merchant backend instance. This "
+"is not required for a simple version of codeless payments, but as soon as "
+"API access for sellers, this is a useful feature. The codeless payment "
+"service then can also double as a hosting service for merchants."
+msgstr ""
+
+#: gsoc-codeless.html.j2:102
+msgid ""
+"To add various analytics for the merchant. Various analysis could be "
+"performed on the orders placed for the respective merchant. Some of the "
+"analysis that can be performed are displaying the most frequently purchased "
+"product, some insights about the shipment tracking, analysis of products "
+"based on delivery location, etc. For this part, dicussions and some more "
+"research have to be done before proceeding to the implementation."
+msgstr ""
+
+#: gsoc-codeless.html.j2:114
+msgid "Screenshots"
+msgstr ""
+
 #: index.html.j2:6
 msgid "GNU Taler logo"
 msgstr ""
@@ -1388,7 +1537,7 @@ msgid ""
 "each contract."
 msgstr ""
 
-#: news.html.j2.inc:11
+#: news.html.j2.inc:9
 msgid "More news"
 msgstr ""
 
@@ -1404,6 +1553,10 @@ msgstr ""
 msgid "GNU Taler in the Press"
 msgstr ""
 
+#: schemafuzz.html.j2:6
+msgid "SchemaFuzz"
+msgstr ""
+
 #: common/base.j2:5
 msgid "GNU Taler"
 msgstr ""
@@ -1473,3 +1626,7 @@ msgstr ""
 #: common/navigation.j2.inc:15
 msgid "Copyright for Contributors"
 msgstr ""
+
+#: common/navigation.j2.inc:17
+msgid "Gsoc 2018: Codeless Payments"
+msgstr ""
diff --git a/wallet.html.j2 b/wallet.html.j2
index 8f75397..c18fc4e 100644
--- a/wallet.html.j2
+++ b/wallet.html.j2
@@ -31,16 +31,6 @@
 
 var chrome_min_version = '51';
 
-function onSuccess() {
-    console.log("installation successful");
-    document.getElementById("install-result").appendChild(document.createTextNode("Installation was successful."));
-}
-
-function onFailure(detail) {
-    console.error("installation failed:", detail);
-    document.getElementById("install-result").appendChild(document.createTextNode("Installation failed: " + detail));
-}
-
 function installWallet() {
     if (window.chrome) {
         chrome.webstore.install("https://chrome.google.com/webstore/detail/millncjiddlpgdmkklmhfadpacifaonc", onSuccess, onFailure);
@@ -143,9 +133,11 @@ document.addEventListener('DOMContentLoaded', onLoad);
           <a href="https://www.google.com/chrome">Google Chrome</a> or <a href="https://www.chromium.org/">Chromium</a>
           version <span id="chrome-min-version"></span> or newer is required, but it appears you have an older version.</p>
         <div id="inline-install-chrome">
-          <button onclick="installWallet()" id="install-button">
-            Install wallet
-          </button>
+          <form target="_blank" action="https://chrome.google.com/webstore/detail/gnu-taler-wallet/millncjiddlpgdmkklmhfadpacifaonc">
+            <button action="submit">
+              Install wallet
+            </button>
+          </form>
           <noscript>
             <em style="color:darkred;">JavaScript is disabled, installation won't work.</em>
           </noscript>