Mercurial > libervia-backend

comparison doc/overview.rst @ 3627:7fe1028acab2

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
doc (overview): comment mentions of web app (not relevant anymore, for now) + web frontend name change
author Goffi <goffi@goffi.org>
date Fri, 27 Aug 2021 14:46:56 +0200
parents 267e4987b58b
children
comparison
equal deleted inserted replaced
3626:82e616b70a2a 3627:7fe1028acab2
76 Libervia Web 76 Libervia Web
77 ------------ 77 ------------
78 78
79 The Web frontend is the second main interface for most users. This frontend has the 79 The Web frontend is the second main interface for most users. This frontend has the
80 particularity to be in 2 parts: a server which serves HTTP content, and a client which 80 particularity to be in 2 parts: a server which serves HTTP content, and a client which
81 runs in the browser. So you have Libervia server which connect to Libervia backend which itself 81 runs in the browser. So you have Libervia Web server which connect to Libervia backend which itself
82 connect to the XMPP server, and your browser will connect to Libervia server. 82 connect to the XMPP server, and your browser will connect to Libervia Web server.
83 83
84 In the browser, you can access the server in two ways: either directly with what we call 84 ..
85 **Libervia pages**, or with a JavaScript code in `single-page application`_ which is the 85 # NOTE: currently not relevant as there is no Web APP anymore, may come back in the
86 **Libervia client** (or **Libervia web app**) that we have mentioned above. 86 future though
87 87 In the browser, you can access the server in two ways: either directly with what we call
88 The **Libervia pages** are web pages managing a single feature. They can work without 88 **Libervia pages**, or with a JavaScript code in `single-page application`_ which is the
89 **Libervia client** (or **Libervia web app**) that we have mentioned above.
90
91 The **Libervia Web Pages** are web pages managing a single feature. They can work without
89 JavaScript when it's possible (it's not the case for instant messaging or similar highly 92 JavaScript when it's possible (it's not the case for instant messaging or similar highly
90 dynamic contents). They aims to be simple and straightforward to use. 93 dynamic contents). They aims to be simple and straightforward to use. That what you're
91 94 accessing when you're using Libervia Web.
92 The **Libervia client** is a highly dynamic web application, used to access more features. 95
93 It's more complete and may be well adapted if you want to let Libervia running in a browser tab 96 ..
94 for an extended period. 97 #Note: as above, not relevant anymore but may come back in the future
95 98 The **Libervia Web Client** is a highly dynamic web application, used to access more features.
96 Last but not least, Libervia is also the central part of the new **web framework** of 99 It's more complete and may be well adapted if you want to let Libervia running in a browser tab
97 Libervia. Indeed, in addition of being a frontend to Libervia features (which is built with 100 for an extended period.
98 this framework), you can create totally different websites which are integrated in Libervia 101
99 (and so XMPP) ecosystem. This framework uses Libervia template engine (based on `Jinja2`_) and 102 Libervia Web is also the central part of the **Web Framework**. Indeed, in addition of
100 makes the creation of decentralised and federated websites simple. Thanks to this framework, 103 being a frontend to Libervia features (which is built with this framework), you can create
101 it's easy to experiment new ideas/features, or to change completely the look and feel of 104 totally different websites which are integrated in Libervia (and so XMPP) ecosystem. This
102 the Libervia frontend. 105 framework uses Libervia template engine (based on `Jinja2`_) and makes the creation of
106 decentralised and federated websites simple. Thanks to this framework, it's easy to
107 experiment new ideas/features, or to change completely the look and feel of the Libervia
108 frontend.
103 109
104 The `official Libervia website`_ is made with Libervia web framework. 110 The `official Libervia website`_ is made with Libervia web framework.
105 111
106 .. _single-page application: https://en.wikipedia.org/wiki/Single-page_application 112 .. _single-page application: https://en.wikipedia.org/wiki/Single-page_application
107 .. _Jinja2: http://jinja.pocoo.org/ 113 .. _Jinja2: http://jinja.pocoo.org/