gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[www] branch master updated: remove duplicate report from news, add diff


From: gnunet
Subject: [www] branch master updated: remove duplicate report from news, add diff to report
Date: Sun, 01 Dec 2019 15:21:49 +0100

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

ng0 pushed a commit to branch master
in repository www.

The following commit(s) were added to refs/heads/master by this push:
     new 8fc995f  remove duplicate report from news, add diff to report
8fc995f is described below

commit 8fc995fcbdc65bc1a56afd10ad3c9b12eb1979d3
Author: ng0 <address@hidden>
AuthorDate: Sun Dec 1 14:18:36 2019 +0000

    remove duplicate report from news, add diff to report
---
 news/2018-08.html.j2                    | 40 ------------------
 template/gsoc-2018-gnunet-webui.html.j2 | 74 ++++++++++++++++-----------------
 www.yml                                 |  5 ---
 3 files changed, 37 insertions(+), 82 deletions(-)

diff --git a/news/2018-08.html.j2 b/news/2018-08.html.j2
deleted file mode 100644
index 3555c0f..0000000
--- a/news/2018-08.html.j2
+++ /dev/null
@@ -1,40 +0,0 @@
-{% extends "common/news.j2" %}
-{% block body_content %}
-  <h1>GSoC 2018 - GNUnet Web-based User Interface</h1>
-<p>
-  Tue, 08/14/2018 - 07:55 - Phil Buschmann 
-</p>
-<h4>What was done?</h4>
-<p>
-  In the context of Google Summer of Code 2018, my mentor (Martin 
Schanzenbach) and I have worked on creating and extending the REST API of 
GNUnet. Currently, we mirrored the functionality of following commands:
-</p>
-<ul>
-  <li>gnunet-identity
-  <li>gnunet-namestore
-  <li>gnunet-gns
-  <li>gnunet-peerinfo
-</ul>
-<p>
-  Additionally, we developed a website with the Javascript framework Angular 6 
and the design framework iotaCSS to use the new REST API. The REST API of 
GNUnet is now documented with Sphinx.
-</p>
-<h4>Why did we create a REST API?</h4>
-<p>
-  ... when you can use the command line tools?  We need to keep in mind, that 
everyone has the right to stay secure and private but not everyone feels 
comfortable using a terminal. The further developed REST access to GNUnet APIs 
in addition to the new web application allows new users to interact with GNUnet 
over a well known tool: their browsers. This addition to the C API and the 
command line tools may attract new users and developers.
-</p>
-<h4>How can we use it?</h4>
-<ol>
-  <li>The REST API developed in GNUnet<br>The REST API is already merged into 
the gnunet.git repository (GNUnet Main Git).  To use the new features, clone 
the repository and follow the Installation on gnunet.org. Then, start the rest 
service with "gnunet-arm -i rest".</li>
-  <li>The Web Application<br>The web application is available under the 
gnunet-webui.git repository (GNUnet WebUI Git).  You need to install the newest 
version of 'node' and 'yarn'. Dependent on your system, you may need to 
download newer versions and install them manually and not over your packet 
manager. After the installation succeeded, you need to clone the repository. 
Then, you need to run "yarn install" and "yarn start" for testing purposes. To 
deploy the website (keep in mind, tha [...]
-  <li>The Documentation<br>The documentation is available under the 
gnunet-rest-api.git repository (GNUnet REST API Docmentation Git). Clone the 
repository and "make html". Then open the 'index.html' under 'build/html/'.</li>
-</ol>
-<p>
-  Please, give it a try and contact me, if you find any bugs or unintentional 
features. ;)
-</p>
-<h4>What can be improved?</h4>
-<p>
-  Right now, the build process of the web application may be a little too 
complex for a casual user. We may be able to solve this by using docker.  
Additionally, the web application does not prevent wrong inputs but responds 
with error messages. Adding GNUnet Records is currently only usable for people, 
who know how a GNS Record looks like. This can be adapted to each record type.  
Last but not least, additional features, design changes, etc...
-</p>
-<p>
-  Thanks for reading.
-</p>
-{% endblock body_content %}
diff --git a/template/gsoc-2018-gnunet-webui.html.j2 
b/template/gsoc-2018-gnunet-webui.html.j2
index ada000f..ec65ee5 100644
--- a/template/gsoc-2018-gnunet-webui.html.j2
+++ b/template/gsoc-2018-gnunet-webui.html.j2
@@ -4,7 +4,7 @@
     <div class="container">
       <div class="text-center">
         <header>
-          <h1>{{ _("GSoC 2018: GNUnet WebUI") }}</h1>
+          <h1>{{ _("GSoC 2018: GNUnet WebUI (GNUnet Web-based User 
Interface)") }}</h1>
         </header>
         <br />
         <p>
@@ -13,21 +13,21 @@
           {% endtrans %}
         </p>
       </div>
+      <h4>What was done?</h4>
       <p>
         {% trans %}
-          <strong>What was done?</strong><br />
           In the context of Google Summer of Code 2018, my mentor
           (Martin Schanzenbach) and I have worked on creating and
           extending the REST API of GNUnet. Currently, we mirrored
           the functionality of following commands:
         {% endtrans %}
       </p>
-      <p>
-        gnunet-identity<br />
-        gnunet-namestore<br />
-        gnunet-gns<br />
-        gnunet-peerinfo
-      </p>
+      <ul>
+        <li>gnunet-identity</li>
+        <li>gnunet-namestore</li>
+        <li>gnunet-gns</li>
+        <li>gnunet-peerinfo</li>
+      </ul>
       <p>
         {% trans %}
           Additionally, we developed a website with the Javascript
@@ -36,32 +36,33 @@
           with Sphinx.
         {% endtrans %}
       </p>
+      <h4>Why did we create a REST API?</h4>
       <p>
         {% trans %}
-          <strong>Why did we create a REST API?</strong><br />
-          ... when you can use the command line tools?<br />
-          We need to keep in mind, that everyone has the right to stay secure
-          and private but not everyone feels comfortable using a terminal. The
-          further developed REST access to GNUnet APIs in addition to the new
-          web application allows new users to interact with GNUnet over a well
-          known tool: their browsers. This addition to the C API and the 
command
-          line tools may attract new users and developers.
+          ... when you can use the command line tools?  We need to
+          keep in mind, that everyone has the right to stay secure and
+          private but not everyone feels comfortable using a
+          terminal. The further developed REST access to GNUnet APIs
+          in addition to the new web application allows new users to
+          interact with GNUnet over a well known tool: their
+          browsers. This addition to the C API and the command line
+          tools may attract new users and developers.
         {% endtrans %}
       </p>
-      <p>
-        {% trans %}
-          <strong>How can we use it?</strong><br />
-          1. The REST API developed in GNUnet<br /> The REST API is
-          already merged into the gnunet.git repository
-          (<a href="https://gnunet.org/git/gnunet.git/";>GNUnet Main 
Git</a>).<br />
-          To use the new features, clone the repository
-          and follow the <a 
href="https://gnunet.org/en/install.html";>Installation</a>
-          on gnunet.org. Then, start the rest service with "gnunet-arm -i 
rest".
-        {% endtrans %}
-      </p>
-      <p>
+      <h4>How can we use it?</h4>
+      <ol>
         {% trans %}
-          2. The Web Application<br />
+          <li>
+            The REST API developed in GNUnet<br> The REST API is
+            already merged into the gnunet.git repository
+            (<a href="https://gnunet.org/git/gnunet.git/";>GNUnet Main 
Git</a>).<br />
+            To use the new features, clone the repository and follow
+            the <a href="https://gnunet.org/en/install.html";>Installation</a>
+            on gnunet.org. Then, start the rest service with
+            "gnunet-arm -i rest".
+          </li>
+        <li>
+          The Web Application<br>
           The web application is available under the gnunet-webui.git
           repository
           (<a href="https://gnunet.org/git/gnunet-webui.git/";>GNUnet WebUI 
Git</a>).<br />
@@ -74,28 +75,27 @@
           in mind, that this website communicates with another localhost
           instance) use "yarn build" for building the web application
           and use the output in the 'dist' directory.
-        {% endtrans %}
-      </p>
-      <p>
-        {% trans %}
-          3. The Documentation<br />
+        </li>
+        <li>
+          The Documentation<br />
           The documentation is available under the gnunet-rest-api.git
           repository
           (<a href="https://gnunet.org/git/gnunet-rest-api.git/";>GNUnet REST 
API Docmentation Git</a>).<br />
           Clone the repository
           and "make html". Then open the 'index.html' under
           'build/html/'.
-        {% endtrans %}
-      </p>
+        </li>
+      {% endtrans %}
+      </ol>
       <p>
         {% trans %}
           Please, give it a try and contact me, if you find any
           bugs or unintentional features. ;)
         {% endtrans %}
       </p>
+      <h4>What can be improved?</h4>
       <p>
         {% trans %}
-          <strong>What can be improved?</strong><br />
           Right now, the build process of the web application may be a
           little too complex for a casual user. We may be able to solve
           this by using docker.<br />  Additionally, the web application
diff --git a/www.yml b/www.yml
index 03f654a..2b61768 100644
--- a/www.yml
+++ b/www.yml
@@ -136,11 +136,6 @@ newsposts:
     title: Google Summer of Code 2019
     abstract:
     content:
-  - page: 2018-08.html
-    date: 2018-08-14
-    title: GSoC 2018 - GNUnet Web-based User Interface
-    abstract:
-    content:
   - page: 2018-07.html
     date: 2018-07-01
     title: Second GNUnet Hacker Meeting 2018

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]