Wikipedia:WikiProject Architecture/Peer review/Japanese castle
From Wikipedia, the free encyclopedia
[edit] Japanese castle
I have just finished a significant expansion and renovation of this article which I created in May 2005. I would really like to be able to hold this up as an example of my best work, since it is (a) largely my own work, with, for the most part only images and some minor stylistic/grammatical changes made by other editors, (b) a broad, important, and central topic, (c) one that is particularly non-esoteric and of general interest. Any suggestions anyone can make to improving this article would be most appreciated.
I've tried not to go overboard on detail, as it really doesn't need to describe every single important development in architecture, nor every military tactical/strategic/technological advancement - it's meant to be a thorough overview, and further details can be explained in separate articles (e.g. I may be creating at some point in the near future separate articles on different styles of Japanese roofing).
- Are there sentences that are awkward or hard to understand?
- Are there points that are superfluous or redundant?
- Points that are missing?
- How does the thing flow overall? - this is a problem I always have trouble with in my actual academic papers: paragraphs that don't flow nicely into one another thematically.
Thanks, all. LordAmeth 11:08, 12 February 2007 (UTC)
- Automatic review - some pointers for compliance with WP:MOS and other policies - I'll comment on the content later. --Mcginnly | Natter 11:13, 12 February 2007 (UTC)
The following suggestions were generated by a semi-automatic javascript program, and might not be applicable for the article in question.
- Consider adding more links to the article; per Wikipedia:Manual of Style (links) and Wikipedia:Build the web, create links to relevant articles.[?]
- Per Wikipedia:Context and Wikipedia:Manual of Style (dates), months and days of the week generally should not be linked. Years, decades, and centuries can be linked if they provide context for the article.[?]
- There may be an applicable infobox for this article. For example, see Template:Infobox Biography, Template:Infobox School, or Template:Infobox City.[?] (Note that there might not be an applicable infobox; remember that these suggestions are not generated manually)
- Per Wikipedia:Manual of Style (headings), headings generally should not repeat the title of the article. For example, if the article was Ferdinand Magellan, instead of using the heading ==Magellan's journey==, use ==Journey==.[?]
- Watch for redundancies that make the article too wordy instead of being crisp and concise. (You may wish to try Tony1's redundancy exercises.)
- Vague terms of size often are unnecessary and redundant - “some”, “a variety/number/majority of”, “several”, “a few”, “many”, “any”, and “all”. For example, “
Allpigs are pink, so we thought ofa number ofways to turn them green.”
- Vague terms of size often are unnecessary and redundant - “some”, “a variety/number/majority of”, “several”, “a few”, “many”, “any”, and “all”. For example, “
- As done in WP:FOOTNOTE, footnotes usually are located right after a punctuation mark (as recommended by the CMS, but not mandatory), such that there is no space in between. For example, the sun is larger than the moon [2]. is usually written as the sun is larger than the moon.[2][?]
- Please ensure that the article has gone through a thorough copyediting so that it exemplifies some of Wikipedia's best work. See also User:Tony1/How to satisfy Criterion 1a.[?]
You may wish to browse through User:AndyZ/Suggestions for further ideas. Thanks, Mcginnly | Natter 11:13, 12 February 2007 (UTC)
