Add page for Angular

[RonakLakhotia]

Fixes #70

[damithc]

@RonakLakhotia The structure looks fine. Can proceed to get peer reviews. Remember to credit original source when reusing assets from elsewhere.

[RonakLakhotia]

@jacoblipech can review this PR?

[jacoblipech]

LGTM! It is quite well-documented, just certain comments to consider. It will be good if you can read through one more time to check for line spacing, missing comma and minor grammar errors.

[jacoblipech]

Sorry for the delay! LGTM! minor spacing problem which you can settle or not.

[damithc]

Added a few quick comments to the top portion. Take another critical look at the rest yourself and fix things that I'm likely to object to, based on my current comments. For example, don't make expansive claims as if you are selling Angular. Give an independent unbiased view.

[damithc]

If you want to use marketing claims in the article e.g., effortless, trivial, etc., simply quote the claim from a credible source, even Angular website themselves, and cite the source. That way, you are not the one making the claim.

[damithc]

Also, wanted to clarify, if for instance I am using a term like MVC in my article. Is it fine to provide a link to another resource or should I explain MVC in the article?

Ideal, avoid using the term.
Next best, provide a simple explanation e.g., as a tooltip or a popover
Failing the above, provide a link to a good concise explanation elsewhere. It is not good if the reader has to read another big article before proceeding with yours though.

[damithc]

A preliminary review of the top portion. Revise the whole article to match the quality indicated by the review comments. Writing is hard.; buckle down for a long ride :-p

[damithc]

@jacoblipech can do another review as the content has changed since your last review? Refer my review comments and calibrate your review to that depth. The deeper your review is, the better the final outcome will be.

[damithc]

Use Fixes #... in the PR description so that GitHub can auto-close the issue when the PR is merged.

[tanhengyeow]

Good effort in the writeup! Refer to the suggestions made 😄

[jacoblipech]

LGTM! Despite using Angular in Teammates, I still learnt some new knowledge from reading it! Minor nits. Also, the "Given below..." phrasings feel quite weird to me but it may be just me, so up to you!

[RonakLakhotia]

@jacoblipech appreciate your review and inputs in this page!

[RonakLakhotia]

@tanhengyeow sorry for the nagging, but still waiting on your final approval. :P

[tanhengyeow]

Looks much better now, great job! Just some nits.

Also, in your first section What is Angular?, you mentioned about Templates, Components, and Dependency Injection. I feel it might nice to put clear sub-headings for them so that it is easier to follow.

[RonakLakhotia]

@tanhengyeow thanks for the suggestions. Added clear headers for templates components and DI.
Can you take another look

[RonakLakhotia]

@tanhengyeow could you look at it again, just a bit worried about the time constraints :P

[tanhengyeow]

LGTM! Just some final nits, thanks for the effort put into this chapter!

[RonakLakhotia]

@jacoblipech @tanhengyeow appreciate your reviews and thank you for the effort put into this!
@damithc your final call?

[damithc]

Looking good now. As we spent so much time on this, why not make it near perfect so that it can serve a a model for future authors? here are few more things to consider.

[RonakLakhotia]

@damithc thanks for suggestions 👍 Updated the changes

[damithc]

More nits

[damithc]

Merged and deployed. Good work @RonakLakhotia
Thanks to the reviewers too.