Search results
Results from the WOW.Com Content Network
[[Category:Non-free use rationale templates]] to the <includeonly> section at the bottom of that page. Otherwise, add <noinclude>[[Category:Non-free use rationale templates]]</noinclude> to the end of the template code, making sure it starts on the same line as the code's last character.
This page provides some basic examples for how to write a fair use rationale. Good rationales might expand on why the non-free item is needed, why a free item cannot be used in its place, and what essential function it performs in each article in which it is to be used. Please modify the text so that it applies to the specific image and use of it.
This is a documentation subpage for Template:Non-free use rationale. It may contain usage information, categories and other content that is not part of the original template page. This template is used on approximately 719,000 pages, or roughly 1% of all pages .
This template is to help users write non-free use rationales for various kinds of posters as required by Non-free content and Non-free use rationale guideline. Include this in the file page, once for each time you insert an image of the poster art into an article. Please use copyrighted content responsibly and in accordance with Wikipedia policy.
Please note that meeting the NFC does not require the use of these templates, as long as the description on the file page addresses all 10 criteria outlined by the NFC. The template {{ Non-free use rationale }} facilitates both adding essential metadata and creating a use rationale with the necessary components.
Template:Non-free use rationale may be helpful for stating the rationale. This tag is not a sufficient claim of fair use. To patrollers and administrators : If this image has an appropriate rationale please append |image has rationale=yes as a parameter to the license template.
Main page; Contents; Current events; Random article; About Wikipedia; Contact us; Donate
This template is used on approximately 2,300 pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage . Consider discussing changes on the talk page before implementing them.