Welcome to RSSR(React-JS Server Side Rendering). Being here is a sign of your professionalism.
RSSR is a SSR boilerplate for React js and contains:
- SSR (Server Side Rendering)
- User Authentication Structure
- SEO optimization utilities
- SCSS Style Namespace
- and more …
:: Base
- React 17.0.1 (react-dom 17.0.1)
- express 4.17.1
- webpack 4.43.0
- eslint 6.8.0
- axios 0.21.0
- history 4.10.1
:: Useful side
- node-sass 4.14.1 (support scss)
- rssr-seo-optimization 0.0.1 (improve SEO)
- dotenv 8.2.0 (support .env files)
- cookie-parser 1.4.5 (support cookie in server mode)
- express-rate-limit 5.1.3 (limit and filer requests in server)
- local-storage 2.0.0 (good structuer for local storage)
- trim-redux 2.3.0 (Redax simplification)
- rssr-namespace 1.0.1 (set name space for SCSS (style) files.)
:: utility (there is no force, You can simply delete)
- bootstrap 4.5.3
- jquery 3.5.1
See Documentation in github.
You can also watch videos of RSSR team at aparat and youtube, .
The core of RSSR is stable but needs some changes before it can be released publicly. You can fork, review and star it but DO NOT USE it for your enterprise projects until the final release!
For more information, follow us at : Telegram channel.
Server Side Rendering is a popular technique for rendering a normally client-side single page app (SPA) on the server and then sending a fully rendered page to the client. The client’s JavaScript bundle can then take over and the SPA can operate as normal. One major benefit of using SSR is in having an app that can be crawled for its content even for crawlers that don’t execute JavaScript code. This can help with SEO and with providing meta data to social media channels.
In programming, the term boilerplate code refers to blocks of code used over and over again.
Let’s assume your development stack consists of several libraries, such as React, Babel, Express, Jest, Webpack, etc. When you start a new project, you initialize all these libraries and configure them to work with each other.
With every new project that you start, you will be repeating yourself. You could also introduce inconsistencies in how these libraries are set up in each project. This can cause confusion when you switch between projects.
This is where boilerplates come in. A boilerplate is a template that you can clone and reuse for every project.
