Talk:Pixel 6/GA1
GA Review
editThe following discussion 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.
GA toolbox |
---|
Reviewing |
Article (edit | visual edit | history) · Article talk (edit | history) · Watch
Reviewer: Sammi Brie (talk · contribs) 05:39, 31 July 2022 (UTC)
GA review (see here for what the criteria are, and here for what they are not) |
---|
|
Overall: |
· · · |
@InfiniteNexus: Almost there. A handful of copy changes as well as some accessibility items with the table of color options. 7-day hold. Ping me when done. (Disclosure: I have a 6 Pro.) Sammi Brie (she/her • t • c) 06:11, 31 July 2022 (UTC)
- @Sammi Brie: Thanks for reviewing this article! I believe all your concerns have been addressed. InfiniteNexus (talk) 06:08, 1 August 2022 (UTC)
Copy changes
editLead
edit- Hyphenate "fifth-largest" (also in Commercial reception)
History
editin as early as 2016
— remove "in"
Specifications
edit- Add "an" before "extended warranty"
Marketing
edit- "as with" → "as well as"
- "As well as" doesn't sound quite right, but I've adjusted the wording. InfiniteNexus (talk) 05:53, 1 August 2022 (UTC)
Reception
edit- Does "Counterpoint Research" need to be italicized? It is not a publication but a company.
- I've un-italicized all mentions of Counterpoint Research. InfiniteNexus (talk) 05:53, 1 August 2022 (UTC)
Source spot checks
editI have randomly selected 10 citations for spot checks. All pass:
- 41 grammar correction as exclusive feature
- 42 digital car key
- 54 online commercials
- 56 major city billboards
- 59 (ABOUTSELF) NBA partnership
- 77 Tensor chip as anticipated
- 99 delays in 6 Pro shipments
- 111 380% growth
- 130 temporary disabling of phone features
- 133 Max Kellerman discovery of Dirty Pipe
Other
edit- Earwig catches almost entirely unavoidable formulations (including "Pixel 6 and Pixel 6 Pro"). Not a real concern.
- UPSD catches three sources: an ABOUTSELF tweet, an attributed reviewer on YT, and a Lifehacker article. The Lifehacker article can probably go. The other two are fine.
- References are archived.
- Outside the infobox, the images need alt text. There are no licensing issues with the images.
- The table of colors needs a caption (MOS:DTAB).
An observation, aside from GA review
editThis is one of the longest infoboxes I have seen in quite some time. Some of this is because of the listing of two sets of specs. However, I would like to recommend that someone consider what is truly needed in {{Infobox mobile phone}}, with these specific comments:
- There are many data fields but no headers to logically organize their contents.
- Slogan parameters have been removed from many infoboxes, e.g. Template talk:Infobox company/Archive 11#Slogans.
- There may be too many data fields in general. See MOS:INFOBOXPURPOSE.
I speak from experience with the 2020 redesign of Infobox radio station, Infobox television station, and Infobox television channel.
- To be honest, I'm not sure what can/should be removed here. I'm aware the infobox is rather long, and yes, it's probably because it includes the specifications for both phones. One way to shorten the length would be to use collapsible lists (see the Availability by region heading), but that would make it harder for readers to access the info. I would suggest elevating your concerns over at Template talk:Infobox mobile phone, though I don't know how many editors are active there. InfiniteNexus (talk) 06:08, 1 August 2022 (UTC)
- Yeah, this isn't a concern of "yikes this is against GA" but me speaking as someone with experience in infobox management. Turns out that it was missing from a few projects that it probably belonged with, too. Sammi Brie (she/her • t • c) 06:24, 1 August 2022 (UTC)