Applications or websites build with Angular Universal

samvloeberghs profile image Sam Vloeberghs Updated on ・1 min read

Angular Universal Advanced Techniques (5 Part Series)

1) Better sharing on social media platforms with Angular Universal 2) Outputting JSON-LD with Angular Universal 3) Applications or websites build with Angular Universal 4) Creating a simple memory cache for your Angular Universal website or application 5) Angular v9 & Universal: SSR and prerendering out of the box!

I've been using Angular Universal for my blog and personal website since I first learned about the technology in October 2016!

What websites have you built using Angular and more specifically Universal? What challenges did you face? How do you like it so far?

For those who haven't heard about it yet, Angular Universal is a specific technology allowing Angular applications to be rendered on the server. This gives you some major benefits, like

  • better performance and load times
  • better SEO and support for crawlers
  • and many more..

Read more about it here and here. Fire away if you have specific questions!


This is where we write about all things Angular. It's meant to be a place for Angular community and people interested in Angular and the Angular ecosystem.


markdown guide

Hi Sam,
I have one question. If you build with Angular Universal, is it the whole application will be server rendered?
Or just render during the time bootstrap, and javascript will take place after fully load.


It's not mandatory to render the complete page of the application on the server, nor is it required to render the complete list of pages on the server.

Some things don't necessary require a server side render. For example: if you are server side rendering for SEO purposes it's only necessary to render the publicly available pages, or the publicly available parts of your pages.

Google will, for example, not login on your authentication functionality when it's crawling your page. Therefor, in respect to that specific requirement, it has no added value to server side render personalized content that you would only show when authenticated


So we can choose which page to use server side render?
It that is the case, do we need two deployments? one for static hosting, another for server side rendering

Correct, you can! Only one deployment is needed. In your server side logic it's perfectly possible to choose which pages can and should be prerended and which not.

I can put together an example if you'd like, but that will require me some time :)

That's great. I was planning to opt in SSR for my website. Thanks for the answer. If you have the time luxury I would love to have an example 😁

Hi there. I've devoted some extra time in my new blogpost to your specific question.

You can find it here: samvloeberghs.be/posts/creating-a-...

The answer to your question is in the second-last section of the page: "Server-side render only specific pages". I will cross post this asap to dev.to Crossposted here: dev.to/angular/creating-a-simple-m...

This is awesome! thanks a lot


Hey Sam. Do you have any examples of how you use angular for your blog? What is your process for storing/rendering your MD, rendering your list page vs post page? I would love to see a post about how you are doing this.


I can write about those specific questions, but it will require time.

Meanwhile please check the repo: github.com/samvloeberghs/kwerri-os...

I don't use MD myself, I prefer full HTML as you can see here: github.com/samvloeberghs/kwerri-os...

How I load my posts and generate them can be found in the posts components, here: github.com/samvloeberghs/kwerri-os...

Hope this can help you out somehow :)