Content deleted Content added
m Reverted 2 edits by 2A02:C7C:A638:8000:1477:FAFC:D5B7:FB33 (talk) to last revision by LizardJr8 |
Minilexikon (talk | contribs) m Group related sections under a parent section for better structure |
||
Line 26:
Server-side scripts are completely processed by the servers instead of clients. When clients request a page containing server-side scripts, the application server processes the scripts and returns an HTML page to the client.
==
=== Server-side rendering ===
In the beginning of the web, content was generated purely on the back end. After the big adoption of front end [[single-page application]]s, a new approach was introduced to generate the HTML using the client application, but on the back end. Examples of frameworks that use [[Server-side rendering|SSR]] are [[Next.js]], [[Nuxt.js]] and [[Nest.js]]. They use [[React.js]], [[Vue.js]], and [[Angular (web framework)|Angular]], respectively, to generate the content of the server.
=== Server-side generation ===
Another similar to SSR technique of generating content for a website is using Server-side generation. This technique use application that create static html pages and then those files are send to the server. File generation can happen on completely different computer for example using [[continuous delivery]]. Example of SSG tools are [[Jekyll (software)|Jekyll]], [[Gatsby (software)|Gatsby]] or [[Eleventy (software)|Eleventy]]. Those sites are often hosted on [[Netlify]] or [[GitHub]] pages. GitHub also supports Jekyll projects where it automatically build the site when changes are added to [[git]].
| |||