Front-end features link
Line 15: | Line 15: | ||
==Server side rendering== | ==Server side rendering== | ||
+ | Server side rendering is the standard way how traditional static web pages or web applications are served on the web, where the page's content is computed and composed server side, even based on user-related data, and then server client side as the page load. | ||
+ | By contrast, a single-page-application (which allows a greater interactivity) first loads on the client and then retrieve its state, that is data from a database and user-related data. | ||
+ | However, by doing so, the information on the page are not present on page load, and the feeling is indeed that you are not consulting a static piece of information, but something which has to be load every time. | ||
+ | In order to enjoy the advantages of both technologies (and considering that the feeling to not visit a static page translates in a poor access to search engines) server side rendering allows a single page application to be processed on the server, and then served on the client precisely as a static page, and then becoming fully interactive and navigable dynamically. | ||
+ | |||
+ | |||
<!-- | <!-- | ||
Thus the front-end is an interactive single-page-application (SPA) using the most modern technologies, | Thus the front-end is an interactive single-page-application (SPA) using the most modern technologies, |
Revision as of 06:12, 19 July 2020
The front-end side of this wiki (a streamlined single-page-application allowing an instantaneous access to set of pages) is automatically created and updated as you create, edit, move or delete pages on the back-end, and it includes the following features:
- Server side rendering
- Navigable table of contents
- Dynamic components
- Offline navigation
- Breadcrumbs and navigation between pages
- Hyphenation
- Filtering of contents in multiple languages
Server side rendering
Server side rendering is the standard way how traditional static web pages or web applications are served on the web, where the page's content is computed and composed server side, even based on user-related data, and then server client side as the page load. By contrast, a single-page-application (which allows a greater interactivity) first loads on the client and then retrieve its state, that is data from a database and user-related data. However, by doing so, the information on the page are not present on page load, and the feeling is indeed that you are not consulting a static piece of information, but something which has to be load every time. In order to enjoy the advantages of both technologies (and considering that the feeling to not visit a static page translates in a poor access to search engines) server side rendering allows a single page application to be processed on the server, and then served on the client precisely as a static page, and then becoming fully interactive and navigable dynamically.