Speaker Q & A

on YouTube ↗28m

" summary

Server rendering trades off direct DOM access, viewport-aware logic and extra infrastructure costs for faster first paint and SEO; use ng add @nguniversal/express-engine to add Universal and run prerendering at build time. Pre-render vs Scully: Universal runs in Node vs Scully in Chrome (Puppeteer) so Universal is faster and Scully is more forgiving; Scully supports Markdown. Template type checking should be enabled incrementally (basic → full → strict), run a strict build to surface errors, then fix by sprint. Use Lighthouse and axe for accessibility but rely on manual screen reader testing.

AI-written summary · about

" chapters (9)

1. 0:00Start
2. 4:09What Are the Downsides of Angular Universal
3. 7:36Are There any Standard Tools To Test Web Aria Accessibility in Web Applications
4. 12:22Media Queries
5. 12:57What Is the Best Strategy for Migrating Large Existing Angular Applications to Using Angular Universal Pre Rendering
6. 13:37What's the Easiest Way To Add It into a Giant Angular App
7. 23:42Is It Worth Investigating Angular Universal if the Contents of My App Are Completely User Role-Based
8. 24:29What Are the Differences between Universal Pre-Render and Scully
9. 25:18Universal Pre-Render Have Markdown Support

" related talks

• 09mScully like an alternative to SSRStepan Suvorov · AngularUP Experience 2020
• 22mDay 1 - Speaker panel 2: Let’s chat about Angular!Manfred Steyer, Stephen Fluin, Ana Cidre, Aaron Frost · ngVikings 2020
• 51mThe Jedi Path to Angular UniversalMichel Murabito · Angular Day 2018
• 26mServer Side Rendering with Angular UniversalNir Kaufman · AngularUP 2016
• 39mScully Like an Alternative to Angular UniversalStepan Suvorov · DevDays Europe 2022
• 19mA plethora of rendering ideasMateusz Do Duc · NG Poland 2022
• 20mSven van StraalenSven van Straalen · AngularNL 2019
• 28mServer-side rendering with Angular 2Wassim Chegham · NG Poland 2016