From d669d242f863becc3d4be8771d5747b08047c3d4 Mon Sep 17 00:00:00 2001
From: "J. Degand" <70610011+jdegand@users.noreply.github.com>
Date: Sun, 1 Sep 2024 07:43:43 -0400
Subject: [PATCH] docs(angular): add creating libraries content (#6894)

---
 .../creating-libraries@A1mYMg7cbcj6p_VkDf-Tz.md        | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/src/data/roadmaps/angular/content/creating-libraries@A1mYMg7cbcj6p_VkDf-Tz.md b/src/data/roadmaps/angular/content/creating-libraries@A1mYMg7cbcj6p_VkDf-Tz.md
index a4c6d8e3c..30e0670b1 100644
--- a/src/data/roadmaps/angular/content/creating-libraries@A1mYMg7cbcj6p_VkDf-Tz.md
+++ b/src/data/roadmaps/angular/content/creating-libraries@A1mYMg7cbcj6p_VkDf-Tz.md
@@ -1 +1,9 @@
-# Creating Libraries
\ No newline at end of file
+# Creating Libraries
+
+If you have developed features that are suitable for reuse, you can create your own libraries. These libraries can be used locally in your workspace, or you can publish them as npm packages to share with other projects or other Angular developers. Putting code into a separate library is more complex than simply putting everything in one application. It requires more of an investment in time and thought for managing, maintaining, and updating the library. This complexity can pay off when the library is being used in multiple applications.
+
+Visit the following resources to learn more:
+
+- [@official@Angular Official Docs - Creating Libraries](https://angular.dev/tools/libraries/creating-libraries)
+- [@official@Angular Official Docs - File Structure: Library project files](https://angular.dev/reference/configs/file-structure#library-project-files)
+- [@opensource@NG Packagr](https://github.com/ng-packagr/ng-packagr)
\ No newline at end of file