├── LICENSE
└── README.md


/LICENSE:
--------------------------------------------------------------------------------
 1 | MIT License
 2 | 
 3 | Copyright (c) 2024 Angular Space
 4 | 
 5 | Permission is hereby granted, free of charge, to any person obtaining a copy
 6 | of this software and associated documentation files (the "Software"), to deal
 7 | in the Software without restriction, including without limitation the rights
 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 | 
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 | 
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 | 


--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
 1 | ![Screenshot 2024-10-30 at 17 24 08_upscayl_2x_realesrgan-x4plus](https://github.com/user-attachments/assets/68267755-3276-4074-9575-b6d067f8da4a)
 2 | 
 3 | # Angular Style Guide by Angular Space x Angular Space Mentors - powered by community :)
 4 | 
 5 | An **opinionated Angular Style Guide + Best Coding Practices**. Built collaboratively with Angular Space & Angular Space Mentors, this guide is created for the community by the community! Like our articles, this guide aims for high quality and remains open to community contributions and feedback. *(Work in Progress)*
 6 | 
 7 | Before launching this project, I reached out to the community on social media, and the response was overwhelmingly positive! This guide is going to be designed to help teams make thoughtful choices on Angular styles and practices, tailored to fit various projects, teams, and architectural preferences. We are going to rpovide the thought process needed to make informed decisons BUT we will have out strong recommendations and when they FIT.
 8 | 
 9 | ### In this guide, you'll find:
10 | - **Guidance on making informed style choices**, with explanations of recommended options, when they work best, and cases where they may not fit as well.
11 | - A focus on understanding the **thought process** behind style selection, making it adaptable rather than prescriptive.
12 | - **Regular alignment with official Angular updates**, while keeping flexibility at the core to support evolving best practices.
13 | 
14 | Thank you for your enthusiasm and feedback in making this happen – let's build a guide that grows with the Angular community!
15 | 


--------------------------------------------------------------------------------