@@ -17,19 +17,19 @@ a few KBs, as opposed to the hundreds/thousands of KBs require to download your
17
17
18
18
Your app appears INSTANTLY on any device (including mobile 3G).
19
19
20
- Once the fully-rendered HTML arrives/appears on the user's view, your Angular app will them load and bootstrap ontop of
20
+ Once the fully-rendered HTML arrives/appears on the user's view, your Angular app will then load and bootstrap on top of
21
21
the existing view. This means that Scully gives you the best of both worlds:
22
22
23
23
1 . The ability to pre-render your entire app to the most base form of HTML & CSS.
24
24
2 . The ability to still have a full powered SPA written in Angular.
25
25
26
26
When your app is pre-rendered, users no longer wait until all the JavaScript has downloaded, parsed and executed before
27
27
they can see and interact with your website. They can immediately begin to see and interact with the page. When your page
28
- is IMMEDIATELY available, you will have less abandoned sessions and a much higher conversion rate on our website.
28
+ is IMMEDIATELY available, you will have less abandoned sessions and a much higher conversion rate on your website.
29
29
30
- This also means that may not need to ship your backend to production. Because the view is pre-rendered and the
30
+ This also means that you may not need to ship your backend to production. Because the view is pre-rendered and the
31
31
data is fetched at build time, all views that can run without the backend in prod CAN run without the backend in prod.
32
- The security an cost implications to that fact can be mind blowing when you think about them.
32
+ The security and cost implications to that fact can be mind blowing when you think about them.
33
33
34
34
For those wanting to know more about this process, please read the [ Getting Started] ( docs/getting-started.md ) guide. For
35
35
those who want to know more about the theory behind pre-rendering JavaScript SPAs, our friends at [ Netlify] ( https://netlify.com )
0 commit comments