Server-Side Rendering for any JS Framework

Server-Side Rendering (SSR) can offer huge benefits to initial page load performance and SEO, but most SSR techniques require you to change the way you write your front-end web apps to accommodate the SSR. We've created a technique to use Node.js to SSR your app without changing your source code and it works with any framework: React, Angular, Backbone, even legacy jQuery apps. Learn how it all works and start SSR'ing your SPAs and PWAs today!

Transcript

1. SERVER-SIDE RENDERING for any JS Framework
2. WHAT IS SSR? Server-Side Rendering
3. 3 THINGS TODAY • Talk about what SSR is and how it works • Talk about our project
 (SSR any SPA and incremental rendering) • Talk you out of using it… (no really)
4. WHY SSR?
5. IS THIS A SOLVED PROBLEM?
6. VOLUNTEERS?
7. SINGLE PAGE APPS
8. VOLUNTEERS?
9. SERVER-SIDE RENDERING
10. SERVER-SIDE RENDERING HTTP2
11. VOLUNTEERS?
12. INCREMENTAL RENDERING
14. VELOCIRENDER
17. HOW’S IT WORK?
18. HOW’S IT WORK? JSDOM
19. EASY HTTP2 PUSH
20. STAND ALONE HTTP(S) MODULE EXPRESS
21. BUT, DON’T USE IT…?
22. NO SEO
23. NO SEO
24. IT SOLVES A VERY
 PARTICULAR PROBLEM
25. DON’T SSR AT ALL…?
26. ARE THERE BETTER OPTIONS?
27. HTTP2
 &
 SERVICE WORKERS
28. HTTP2
29. SERVICE WORKERS
30. SERVICE WORKERS
31. WHY SSR AT ALL…?
32. WHEN YOU CAN JAM?
33. Did you just make this up?
34. &
35. QUICK RECAP • We talked about SSR, the benefits and how it works • We talked about Velocirender, the easiest way to add SSR and incremental rendering to your SPA • We talked about why you most likely shouldn’t be SSR’ing at all!
36. QUESTIONS? SERVER-SIDE RENDERING For any JavaScript Framework @adamlbarrett BigAB