From 14508c6df2fda6f623df7d2cc775d1185ce7237f Mon Sep 17 00:00:00 2001 From: erdemcaygor Date: Fri, 10 Oct 2025 15:28:02 +0300 Subject: [PATCH] update --- .../post.md | 7 ------- .../post.md | 6 ++++++ 2 files changed, 6 insertions(+), 7 deletions(-) delete mode 100644 docs/en/Community-Articles/2025-08-10-Using-Transfer-State-with-Angular-SSR/post.md create mode 100644 docs/en/Community-Articles/2025-10-10-Using-Transfer-State-with-Angular-SSR/post.md diff --git a/docs/en/Community-Articles/2025-08-10-Using-Transfer-State-with-Angular-SSR/post.md b/docs/en/Community-Articles/2025-08-10-Using-Transfer-State-with-Angular-SSR/post.md deleted file mode 100644 index 5c7567c3aa..0000000000 --- a/docs/en/Community-Articles/2025-08-10-Using-Transfer-State-with-Angular-SSR/post.md +++ /dev/null @@ -1,7 +0,0 @@ -# From Server to Browser — the Elegant Way: Angular TransferState Explained - -## Introduction - -When building Angular applications with Server-Side Rendering (SSR), one of the most common performance pitfalls is duplicated data fetching. Your server fetches data to render the initial HTML, and then — as soon as the browser bootstraps Angular — it fetches the same data all over again. That’s wasteful, especially for APIs that don’t change often. - -Enter TransferState, Angular’s elegant solution to bridge the data gap between the server and the browser. It allows you to transfer pre-fetched data from the server-rendered page to the client seamlessly — no redundant HTTP calls, no flickering spinners, and no extra waiting time. \ No newline at end of file diff --git a/docs/en/Community-Articles/2025-10-10-Using-Transfer-State-with-Angular-SSR/post.md b/docs/en/Community-Articles/2025-10-10-Using-Transfer-State-with-Angular-SSR/post.md new file mode 100644 index 0000000000..67526d2813 --- /dev/null +++ b/docs/en/Community-Articles/2025-10-10-Using-Transfer-State-with-Angular-SSR/post.md @@ -0,0 +1,6 @@ +# From Server to Browser — the Elegant Way: Angular TransferState Explained + +## Introduction + +When building Angular applications with Server-Side Rendering (SSR), one of the most common performance pitfalls is duplicated data fetching. Server fetch data while generating initial HTML, and then browser bootstraps Angular and it fetches the same data all over again. That’s wasteful, especially for APIs that don’t change often. +To solve this problem, Angular provide **TransferState**. It allows to transfer data from application on server to application on browser, in this way you can avoid redundant unnecessary operations. \ No newline at end of file