erebion/libervia-backend
Watch
1
0
Fork
You've already forked libervia-backend
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

doc (overview): comment mentions of web app (not relevant anymore, for now) + web frontend name change

Browse source
This commit is contained in:
Goffi 2021-08-27 14:46:56 +02:00
commit 29dd678af9
1 changed files with 25 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

40
doc/overview.rst
View file

@ -78,28 +78,34 @@ Libervia Web
The Web frontend is the second main interface for most users. This frontend has the
particularity to be in 2 parts: a server which serves HTTP content, and a client which
runs in the browser. So you have Libervia server which connect to Libervia backend which itself
connect to the XMPP server, and your browser will connect to Libervia server.
runs in the browser. So you have Libervia Web server which connect to Libervia backend which itself
connect to the XMPP server, and your browser will connect to Libervia Web server.
In the browser, you can access the server in two ways: either directly with what we call
**Libervia pages**, or with a JavaScript code in `single-page application`_ which is the
**Libervia client** (or **Libervia web app**) that we have mentioned above.
..
# NOTE: currently not relevant as there is no Web APP anymore, may come back in the
future though
In the browser, you can access the server in two ways: either directly with what we call
**Libervia pages**, or with a JavaScript code in `single-page application`_ which is the
**Libervia client** (or **Libervia web app**) that we have mentioned above.
The **Libervia pages** are web pages managing a single feature. They can work without
The **Libervia Web Pages** are web pages managing a single feature. They can work without
JavaScript when it's possible (it's not the case for instant messaging or similar highly
dynamic contents). They aims to be simple and straightforward to use.
dynamic contents). They aims to be simple and straightforward to use. That what you're
accessing when you're using Libervia Web.
The **Libervia client** is a highly dynamic web application, used to access more features.
It's more complete and may be well adapted if you want to let Libervia running in a browser tab
for an extended period.
..
#Note: as above, not relevant anymore but may come back in the future
The **Libervia Web Client** is a highly dynamic web application, used to access more features.
It's more complete and may be well adapted if you want to let Libervia running in a browser tab
for an extended period.
Last but not least, Libervia is also the central part of the new **web framework** of
Libervia. Indeed, in addition of being a frontend to Libervia features (which is built with
this framework), you can create totally different websites which are integrated in Libervia
(and so XMPP) ecosystem. This framework uses Libervia template engine (based on `Jinja2`_) and
makes the creation of decentralised and federated websites simple. Thanks to this framework,
it's easy to experiment new ideas/features, or to change completely the look and feel of
the Libervia frontend.
Libervia Web is also the central part of the **Web Framework**. Indeed, in addition of
being a frontend to Libervia features (which is built with this framework), you can create
totally different websites which are integrated in Libervia (and so XMPP) ecosystem. This
framework uses Libervia template engine (based on `Jinja2`_) and makes the creation of
decentralised and federated websites simple. Thanks to this framework, it's easy to
experiment new ideas/features, or to change completely the look and feel of the Libervia
frontend.
The `official Libervia website`_ is made with Libervia web framework.