[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [taler-www] branch stable updated (b73e2ef -> c78e327)
From: |
gnunet |
Subject: |
[GNUnet-SVN] [taler-www] branch stable updated (b73e2ef -> c78e327) |
Date: |
Wed, 24 Jul 2019 13:25:15 +0200 |
This is an automated email from the git hooks/post-receive script.
grothoff pushed a change to branch stable
in repository www.
from b73e2ef list WooCommerce team
add c78e327 fix floatings
No new revisions were added by this update.
Summary of changes:
principles.html.j2 | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/principles.html.j2 b/principles.html.j2
index 52164b7..854ebce 100644
--- a/principles.html.j2
+++ b/principles.html.j2
@@ -89,7 +89,7 @@ h2 {
<div class="row">
<div class="col-lg-12">
<h2>5. Only disclose the minimal amount of information necessary</h2>
- <img style="width:20vw;float:left;padding:15px"
src="../images/gdpr.medium.jpg" alt="Privacy by design, privacy by default,
General Data Protection Regulation (GDPR) compliant"></a>
+ <img style="width:20vw;float:right;padding:15px"
src="../images/gdpr.medium.jpg" alt="Privacy by design, privacy by default,
General Data Protection Regulation (GDPR) compliant"></a>
<p>
The reason behind this goal is similar to (2). The privacy of buyers
is given
priority, but other parties such as merchants still benefit from it,
for example,
@@ -100,7 +100,7 @@ h2 {
<div class="row">
<div class="col-lg-12">
<h2>6. Be usable</h2>
- <img style="width:20vw;float:right;padding:15px"
src="../images/buy.medium.jpg" alt="Buy with one click"></a>
+ <img style="width:20vw;float:left;padding:15px"
src="../images/buy.medium.jpg" alt="Buy with one click"></a>
<p>
Specifically it must be usable for non-expert customers. Usability also
applies to the integration with merchants, and informs choices about the
@@ -112,7 +112,7 @@ operations into an isolated component with a simple API.
<div class="row">
<div class="col-lg-12">
<h2>7. Be efficient</h2>
- <img style="width:20vw;float:left;padding:15px"
src="../images/efficient.png" alt="Energy efficiency"></a>
+ <img style="width:20vw;float:right;padding:15px"
src="../images/efficient.png" alt="Energy efficiency"></a>
<p>
Approaches such as proof-of-work are ruled out by this requirement.
Efficiency is necessary for GNU Taler to be used for micropayments.
</p>
@@ -121,7 +121,7 @@ operations into an isolated component with a simple API.
<div class="row">
<div class="col-lg-12">
<h2>8. Fault-tolerant design</a></h2>
- <img style="width:20vw;float:right;padding:15px"
src="../images/life-safer.medium.jpg" alt="Life Safers"></a>
+ <img style="width:20vw;float:left;padding:15px"
src="../images/life-safer.medium.jpg" alt="Life Safers"></a>
<p>
Taler should tolerate failure of individual components and systems,
including malicious operators compromising core secrets.
@@ -133,7 +133,7 @@ operations into an isolated component with a simple API.
<div class="row">
<div class="col-lg-12">
<h2>9. Foster competition</h2>
- <img style="width:20vw;float:left;padding:15px"
src="../images/market.medium.jpg" alt="A competitive market"></a>
+ <img style="width:20vw;float:right;padding:15px"
src="../images/market.medium.jpg" alt="A competitive market"></a>
<p>
It must be relatively easy for competitors to join the systems. While the
barriers for this in traditional financial systems are rather high, the
technical
--
To stop receiving notification emails like this one, please contact
address@hidden.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] [taler-www] branch stable updated (b73e2ef -> c78e327),
gnunet <=