Wikipedia:Miscellany for deletion/Portal:Android (operating system)
- The following discussion is an archived debate of the proposed deletion of the miscellaneous page below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the page's talk page or in a deletion review). No further edits should be made to this page.
The result of the discussion was: delete. — JJMC89 (T·C) 03:43, 3 July 2019 (UTC)
Created 2016 and already out of date. One bio, one selected article. The selected article refers to "Android Pay," which has since been renamed "Google Pay." Mark Schierbecker (talk) 04:29, 25 June 2019 (UTC)
- Delete - One common method for the design of portals, in use at least since 2005, has involved sometimes large numbers of subpages of the portal, one for each selected article and picture, and sometimes for news items and Do You Know (DYK) items. Often the subpages for selected articles consist of a copy of the original article, or a copy of the first part of the original article. The subpages for In The News (ITN) and DYK items may also be copies of the lead paragraph or a portion of the article page. This approach to design of portals is sufficiently commonly used that it can be considered standard. However, it is an honorable experiment that has failed, and should be abandoned. In numerous cases, it has been found that portals have displayed outdated and incorrect information to the reader. These discrepancies have been especially common with, but not limited to, political leadership. These discrepancies are a serious problem because they cannot be readily corrected. Wikipedia is the encyclopedia that anyone can edit, meaning that any reasonably computer-literate person can edit an article; but editing the displayed information in a portal requires specialized technical knowledge of how portals are implemented, which is presumably why errors persist, sometimes for years. An editor who has Twinkle installed can tag articles in need of editing if they do not have the time or knowledge to fix them; but tagging via Twinkle is not available for portals. Experience has shown that the use of portal subpages that copy portions of articles results in outdated information being displayed, sometimes for years, because it is difficult to correct. This design technique, partial article copies, has been an honorable experiment over the course of more than a decade, but the experiment should be assessed to have been a failure. Some other design approach for portals should be used in the future.
- This portal has 39 daily pageviews, as opposed to 8144 daily pageviews for the head article. The ability to attract a large number of readers is not useful if they are being attracted to a portal that is out-of-date. This portal should be deleted, without prejudice to a new portal with a design that does not rely on partial copies of articles. Robert McClenon (talk) 06:11, 26 June 2019 (UTC)
- Delete. Yet another abandoned portal. Special:PrefixIndex/Portal:Android (operating system) confirms the nominator's observation about lack of content.
- WP:POG requires that portals should be about "broad subject areas, which are likely to attract large numbers of interested readers and portal maintainers". A theoretical argument could be made that Android is a broad topic. I disagree with that theoretical argument (it's currently a v popular operating system, but that makes it a sub-sub-field of computing), but we don't need to rely on theory because we have empirical evidence that in practice this portal does not pass that test: it has not attracted maintainers, and it has not attracted readers.
- Per WP:PORTAL, "Portals serve as enhanced 'Main Pages' for specific broad subjects". But this is massively less useful in every respect than the head article Android (operating system) and its poor navboxes Template:Android (operating system).
- Two newish features of the Wikimedia software means that the article and navboxes offers all the functionality which portals like this set out to offer. Both features are available only to ordinary readers who are not logged in, but you can test them without logging out by right-clicking on a link, and the select "open in private window" (in Firefox) or "open in incognito window" (Chrome).
- mouseover: on any link, mouseover shows you the picture and the start of the lead. So the preview-selected page-function of portals is redundant: something almost as good is available automatically on any navbox or other set of links. Try it by right-clicking on this link to Template:Android (operating system), open in a private/incognito tab, and mouseover any link.
- automatic imagery galleries: clicking on an image brings up an image gallery of all the images on that page. It's full-screen, so it's actually much better than a click-for-next image gallery on a portal. Try it by right-clicking on this link to the article Android (operating system), open in a private/incognito tab, and click on any image to start the slideshow
- Similar features have been available since 2015 to users of Wikipedia's Android app.
- Those new technologies set a high bar for any portal which actually tries to add value for the reader. But this portal fails the basic requirements even of the guidelines written before the new technologies changed the game. The generic problems of the content-forked-subpage model of portal are multiplied in a fast-developing field such as this, where content forks become outdated even more rapidly than elsewhere. This model of portal should be deprecated generally, but it is a disaster for a fast-moving topic such as this unless a huge amount of work is applied to keep it up-to-date ... and that's not happening here. --BrownHairedGirl (talk) • (contribs) 01:12, 3 July 2019 (UTC)
- The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the page's talk page or in a deletion review). No further edits should be made to this page.