Template:Cite video game
| 40x40px | This template is a Citation Style 1 specific-source template based on {{Cite book}}. For centralised Citation Style 1 discussions, see Help talk:Citation Style 1. |
| 40x40px | This template employs intricate features of template syntax.
You are encouraged to familiarise yourself with its setup and parser functions before editing the template. If your edit causes unexpected problems, please undo it quickly, as this template may appear on a large number of pages. You can conduct experiments, and should test all major changes, in either this template's sandbox, the general template sandbox, or your user space before changing anything here. |
Usage
{{cite video game
| title =
| trans-title =
| developer =
| publisher =
| date =
| platform =
| version =
| scene =
| level =
| language =
| quote =
}}
- Or use the inline version
{{cite video game |title= |trans-title= |developer= |publisher= |date= |platform= |version= |scene= |level= |language= |quote= }}
Sample input:
{{cite video game
|title=[[Halo 3]]
|developer=[[Bungie]]
|publisher=[[Microsoft Game Studios]]
|date=2007-09-25
|platform=[[Xbox 360]]
|version=1.0
|level=The Storm
|language=
|quote='''Arbiter''': 'More Brutes?' / '''Master Chief''': 'Worse.'
}}
Sample output:
Bungie (2007-09-25). Halo 3 (Xbox 360) (1.0 ed.). Microsoft Game Studios. Level/area: The Storm. Arbiter: 'More Brutes?' / Master Chief: 'Worse.'
Required parameters
- title: Title of the game.
- developer: Developer of the game.
- Use developer2, developer3, developer4, developer5 for listing multiple developers.
Optional parameters
- trans-title: Translated title of the game, if the cited version's title is not already in English
- date: Full date of publication of the specified version. Must not be wikilinked.
- publisher: Publisher, if applicable to translation/edition; omit if identical to developer
- language: language of publication (don't specify "English" as this is the default)
- version: version, if applicable
- platform: platform, if applicable to the reference. (If citing something that is the same across all versions, this is unnecessary)
- quote: the quote that is used as the reference. (Use quotation marks when quoting direct speech)
- scene: scene within which the referred event or quote (if any) occurs (e.g. opening, staff credits).
- level: level or area within which the referred event or quote (if any) occurs.
TemplateData
TemplateData for Cite video game
| Parameter | Description | Type | Status | |
|---|---|---|---|---|
| Title | title | Title of the video game | String | required |
| Developer | developer | Developer of the game | String | required |
| Publisher | publisher | Publisher, if applicable to translation/edition; omit if identical to developer | String | optional |
| Platform | platform | Platform, if applicable to the reference. (If citing something that is the same across all versions, this is unnecessary) | String | optional |
| Version | version | Version number of the video game cited, if applicable | String | optional |
| Scene | scene | Scene within which the referred event or quote (if any) occurs (e.g. opening, staff credits) | String | optional |
| Level | level | Level or area within which the referred event or quote (if any) occurs | String | optional |
| Date | date | Full date of publication of the specified version. Must not be wikilinked. | String | optional |
| Quote | quote | The quote that is used as the reference | String | optional |
| Language | language | Language of publication; specify only if it is not English | String | optional |
| The above documentation is transcluded from Template:Cite video game/doc. (edit | history) Editors can experiment in this template's sandbox (create | mirror) and testcases (create) pages. Please add categories to the /doc subpage. Subpages of this template. |
Welcome
Welcome to the CKN Knowledge in Practice Centre (KPC). The KPC is a resource for learning and applying scientific knowledge to the practice of composites manufacturing. As you navigate around the KPC, refer back to the information on this right-hand pane as a resource for understanding the intricacies of composites processing and why the KPC is laid out in the way that it is. The following video explains the KPC approach:
Understanding Composites Processing
The Knowledge in Practice Centre (KPC) is centered around a structured method of thinking about composite material manufacturing. From the top down, the heirarchy consists of:
- The factory
- Factory cells and/or the factory layout
- Process steps (embodied in the factory process flow) consisting of:
The way that the material, shape, tooling & consumables and equipment (abbreviated as MSTE) interact with each other during a process step is critical to the outcome of the manufacturing step, and ultimately critical to the quality of the finished part. The interactions between MSTE during a process step can be numerous and complex, but the Knowledge in Practice Centre aims to make you aware of these interactions, understand how one parameter affects another, and understand how to analyze the problem using a systems based approach. Using this approach, the factory can then be developed with a complete understanding and control of all interactions.
Interrelationship of Function, Shape, Material & Process
Design for manufacturing is critical to ensuring the producibility of a part. Trouble arises when it is considered too late or not at all in the design process. Conversely, process design (controlling the interactions between shape, material, tooling & consumables and equipment to achieve a desired outcome) must always consider the shape and material of the part. Ashby has developed and popularized the approach linking design (function) to the choice of material and shape, which influence the process selected and vice versa, as shown below:
Within the Knowledge in Practice Centre the same methodology is applied but the process is more fully defined by also explicitly calling out the equipment and tooling & consumables. Note that in common usage, a process which consists of many steps can be arbitrarily defined by just one step, e.g. "spray-up". Though convenient, this can be misleading.
Workflows
The KPC's Practice and Case Study volumes consist of three types of workflows:
- Development - Analyzing the interactions between MSTE in the process steps to make decisions on processing parameters and understanding how the process steps and factory cells fit within the factory.
- Troubleshooting - Guiding you to possible causes of processing issues affecting either cost, rate or quality and directing you to the most appropriate development workflow to improve the process
- Optimization - An expansion on the development workflows where a larger number of options are considered to achieve the best mixture of cost, rate & quality for your application.
.svg){kind=link}
