Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a44cec288ce5610f

Jump to content

Talk:1 Line (Sound Transit)/GA1

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
(Redirected from Talk:Red Line (Sound Transit)/GA1)
Latest comment: 8 years ago by SounderBruce in topic GA Review

GA Review

[edit]

The 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.


Article (edit | visual edit | history) · Article talk (edit | history) · Watch

Reviewer: Kees08 (talk · contribs) 07:03, 14 February 2018 (UTC)Reply


Rate Attribute Review Comment
1. Well-written:
1a. the prose is clear, concise, and understandable to an appropriately broad audience; spelling and grammar are correct.

Should one of these be hyphenated when the other isn't?: 70-mile (110 km)

Should that space be there?: mid- 2010s.

Hyphens? - End to end

1b. it complies with the Manual of Style guidelines for lead sections, layout, words to watch, fiction, list incorporation, and table accessibility.

Shouldn't the reference come after the parenthesis? - dollars[8])

2. Verifiable with no original research:
2a. it contains a list of all references (sources of information), presented in accordance with the layout style guideline.

Talked a bit in IRC, I am happy here.

2b. reliable sources are cited inline. All content that could reasonably be challenged, except for plot summaries and that which summarizes cited content elsewhere in the article, must be cited no later than the end of the paragraph (or line if the content is not in prose).
2c. it contains no original research.
2d. it contains no copyright violations or plagiarism.

Earwig shows some matches, but they are road names, so it is fine.

3. Broad in its coverage:
3a. it addresses the main aspects of the topic.
3b. it stays focused on the topic without going into unnecessary detail (see summary style).
4. Neutral: it represents viewpoints fairly and without editorial bias, giving due weight to each.
5. Stable: it does not change significantly from day to day because of an ongoing edit war or content dispute. No edit warring
6. Illustrated, if possible, by media such as images, video, or audio:
6a. media are tagged with their copyright statuses, and valid non-free use rationales are provided for non-free content.

Images are tagged w/ their copyright status, no fair-use images are used. Tineye'ed the ones that were not by SounderBruce and Wikipedia is the first place the images were found.

6b. media are relevant to the topic, have suitable captions, and have alt text.

Some of the captions are complete sentences, which means they should end in a period. Captions that are not complete sentences should stay without a period. Otherwise the captions are well-written and informative.

OPTIONAL: Not required at any level of review, but add alts to the images for accessibility if you want.

7. Overall assessment.
@Kees08: Fixed the hyphens, spaces, inflation citations, captions, and alt text for images. The km conversion is generated by a template that cites MOS as its reason to drop the hyphen, so I would rather keep it. SounderBruce 07:04, 22 February 2018 (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.