- The following discussion is an archived debate of the proposed deletion of the article below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.
The result was redirect. The current article consists mainly of a bulleted list of features and advantages, and is hardly an article. Some participants have advocated outright deletion, but the option to redirect to a related article also appears acceptable. Two articles have been proposed as the redirect target. At my editorial discretion, I am redirecting to AngularJS#Angular_Material since there already is a "Angular Material" heading there, although redirecting to Angular (web framework) is also arguable. (The choice of redirect target does not require admin attention.) Sjakkalle (Check!) 11:45, 30 August 2019 (UTC)[reply]
- Angular Material (edit | talk | history | protect | delete | links | watch | logs | views) – (View log · Stats)
- (Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)
No evidence of notability. WP does not need a stub for every software project or component Imaginatorium (talk) 06:13, 21 August 2019 (UTC)[reply]
- Note: This discussion has been included in the list of Software-related deletion discussions. CAPTAIN RAJU(T) 06:49, 21 August 2019 (UTC)[reply]
- Note: This discussion has been included in the list of Internet-related deletion discussions. CAPTAIN RAJU(T) 06:49, 21 August 2019 (UTC)[reply]
- Note: This discussion has been included in the list of Computing-related deletion discussions. CAPTAIN RAJU(T) 06:49, 21 August 2019 (UTC)[reply]
- Does it even need a redirect? If discussed in AngularJS, a search will find that article, which is what the reader needs. If someone enters "Angular material", what is the probability they are looking for AngularJS versus just any sort of angular material? Imaginatorium (talk) 09:58, 21 August 2019 (UTC)[reply]
Delete. There's some ambiguity between AngularJS and Angular (web framework), and it's unclear which one this article should redirect to. The subject of this article is only associated with the former, but there is another library named Angular Material that only works with the latter. If there were a clear redirect target, I would insist on a redirect because this library does meet WP:GNG with the article's cited sources, and there is no other topic on Wikipedia with the name angular material. — Newslinger talk 10:15, 21 August 2019 (UTC)[reply]
Merge into AngularJS. Angular Material is a library that implements Material Design for AngularJS. All 3 of the subjects (Angular Material, Material Design, and AngularJS) are developed by Google, and there is considerable overlap between Angular Material and AngularJS. The Angular Material article in its current state is highly promotional and its content relies almost entirely on primary sources, even though there are secondary sources cited. A merge of the citations and the lead sentence should be sufficient. Since there are two different Angular Material libraries, one targeting AngularJS and one targeting Angular (web framework), and it is unclear which article Angular Material should redirect to, the Angular Material page should either be deleted or converted into a disambiguation page after the merge. — Newslinger talk 22:49, 21 August 2019 (UTC)[reply]
- OMG. lack of understanding.:) refer github to understand which library is it. that is a separate library. AngularJS is a JavaScript library, we can merge AngularJS to Javascript too: it does not work like that. Angular Material is a Meterial design library. Seperate article is needed. You can find many books about Angular Material. There is no overlap: only lack of understanding of the subject. Thanks.
- I am fully aware that AngularJS and Angular Material are in two separate Git repositories, and I still don't think Angular Material deserves a separate article. Angular Material is only used within AngularJS projects, and both Angular Material and AngularJS are developed by Google. This shows significant overlap and warrants a merge. There is nothing wrong with writing about Angular Material on Wikipedia, but it should be done in the AngularJS article because Angular Material is essentially a subtopic of AngularJS, despite being in a separate repository. All of the books you listed only refer to using Angular Material within AngularJS (or Angular (web framework), but that's a different Angular Material repository than the one described in the article). We don't have separate articles for Vue Router (repository) or Ember Data (repository) for the same reasons: they are closely associated with and are not used outside of their parent frameworks (Vue.js and Ember.js). Wikipedia is not a directory or a package registry, and articles don't need to have a one-to-one correspondence with Git repositories. In general, we would prefer to have one very comprehensive article on AngularJS and its associated libraries than to have separate articles that are less comprehensive. — Newslinger talk 02:18, 22 August 2019 (UTC)[reply]
- I understand your logic. The issue here is people might query angular material as a phrase. There are books about it separately. Material design is a different topic which is different from general web design. With regarding future expansion, it will be important to have a seperate article for angular material which is effectively a sub-set of material design than AngularJS. (e.g. we are not going to include all the JavaScript frameworks under the article JavaScript, for, the same reason). In design viewpoint, it should be under material design not AngularJS as the usage is different. Thanks.Shevonsilva (talk) 15:56, 22 August 2019 (UTC)[reply]
- Redirect to AngularJS § Angular Material. I've merged in the sentence and the secondary book sources. If this article is redirected, I will add a
{{redirect}} hatnote from this section to Angular (web framework) to eliminate any confusion between the two frameworks. — Newslinger talk 01:02, 30 August 2019 (UTC)[reply]
- As originator of this AfD, thanks for your effort - and redirect now seems the obvious choice. But the sentence you added (the entire "content" of this "article") is uncontroversial, and does not need five references. Please reduce to (about) two. Imaginatorium (talk) 06:10, 30 August 2019 (UTC)[reply]
- No problem. I've condensed the citations with
{{refn}}, which makes them take up less space in the article text. The book sources are included to help interested editors to expand the section. If the editors who expand the section decide that some of the sources are not necessary, they can remove them. — Newslinger talk 06:30, 30 August 2019 (UTC)[reply]
- Strongly Keep: I got really a problem here. Angular Material is used in many places in software development as a dependency and it is really a popular library. There is no issue in notability (refer references). This is really disturbing my contribution. These articles should be reviewed through experienced and IT expertise people. I find it really disturbing placing deletion tags' without even understating the content. Do not redirect as usage of AngularJS and Angular Material is different as Angular material is a part of material design. Angular Material is probably one of top 10 material design framework.[1][2] There are books mainly targeting Angular material (https://books.google.co.uk/books?id=3gvpDAAAQBAJ). There are many tutorials about Angular Materials[3] (Note: Articles should be reviewed by experienced people. If you cannot understand the content, please place a message in my talk page or here, I will answer as I have time for that.) Thanks. — Preceding unsigned comment added by Shevonsilva (talk • contribs) 10:46, 21 August 2019 (UTC)[reply]
- — Note to closing admin: Shevonsilva (talk • contribs) is the creator of the page that is the subject of this XfD.
- Sorry, I have included many books about the subject
Kotaru, V. Keerti (2016-08-25). Material Design Implementation with AngularJS: UI Component Framework. Apress. p. 4. ISBN 9781484221907.
Noring, Christoffer; Deeleman, Pablo (2017-12-08). Learning Angular: A no-nonsense guide to building real-world apps with Angular 5. Packt Publishing Ltd. p. 315. ISBN 9781787125940.
Hajian, Majid (2019-05-22). Progressive Web Apps with Angular: Create Responsive, Fast and Reliable PWAs Using Angular. Apress. p. 30. ISBN 9781484244487.
Kasagoni, Shravan Kumar (2017-05-29). Building Modern Web Applications Using Angular. Packt Publishing Ltd. p. 173. ISBN 9781785880032.
Clow, Mark (2018-02-20). Angular 5 Projects: Learn to Build Single Page Web Applications Using 70+ Projects. Apress. p. 245. ISBN 9781484232798.
- Material Design is a seperate implementation and is not a part of AngularJS. Shevonsilva (talk) 23:14, 21 August 2019 (UTC)[reply]
- Maven dependency for AngularJS is
<dependency>
<groupId>org.webjars</groupId>
<artifactId>angularjs</artifactId>
<version>2.0.0-alpha.22</version>
</dependency>
Maven dependency for Angular Material is
<dependency>
<groupId>org.webjars</groupId>
<artifactId>angular-material</artifactId>
<version>0.7.1</version>
</dependency>
Two different artifacts means two different projects. Keep the article as this is a separate artifact. Shevonsilva (talk) 00:09, 22 August 2019 (UTC)[reply]
- Comment on merge proposal: Problem is, what would you merge? The "content" of the article consists of two bulleted lists: the "Features" appear to be just marketing fluff; the "Advantages" are largely inscrutable. @Shevonsilva: can you explain what "DI" means, for example? If it is CS slang, it should be explained or linked. Imaginatorium (talk) 03:20, 23 August 2019 (UTC)[reply]
- Again, I am repeating: these articles should be reviewed by experienced writers and IT experts. :) DI is a really really popular and common short form (in IT) for Dependency Injection. Thanks. Shevonsilva (talk) 12:11, 23 August 2019 (UTC)[reply]
- (And you are an "experienced writer", are you?) If DI is CS slang, it should be explained. In any case, it is not a coherent "Advantage". Imaginatorium (talk) 15:20, 23 August 2019 (UTC)[reply]
- "experienced writer" -> about myself doesn't matter :) ; DI is not a CS slang :) ; coherent "Advantage" -> these articles should be reviewed by experienced writers and IT experts. :) Thanks. Shevonsilva (talk) 00:43, 24 August 2019 (UTC)[reply]
- Redirect to Angular (web framework) where it is mentioned as a component of that framework 5 times - the five books referenced in the Angular Material article are all about using Angular (web framework) and using Angular Material as part of Angular projects, so it is not notable outside of that context - If the article can only be understood by experienced writers and IT experts, then it falls under "Wikipedia is not a manual, guidebook, textbook, or scientific journal" WP:NOTMANUAL. Writing better articles says that articles should be "accessible and understandable for as many readers as possible" and "Aim for a balance between comprehensibility and detail so that readers can gain information from the article" and should "make sense if the reader gets to it as a random page" and "if we cannot explain to readers why something is important, then it is not important" - I can't see any way that this is important as a stand-alone article, therefore, redirect to main article - Epinoia (talk) 00:18, 28 August 2019 (UTC)[reply]
- The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.