Difference between revisions of "Manual of Style"
Abel Maciel (talk | contribs) |
Abel Maciel (talk | contribs) |
||
| Line 11: | Line 11: | ||
=Tutorial Pages= | =Tutorial Pages= | ||
| − | + | Tutorial pages should contain a '''Title'', the '''Abstract'''only, with no ellaborate introduction, the '''Principle'''explaining in detail the underpining rationaly of the principle being applied in the tutorial, the '''Code''' sample and finaly, whenever possible the '''Download''' for tutorial files. | |
| − | '''Title'' | + | ==Title== |
| − | '''Abstract''' | + | ==Abstract== |
| − | '''Principle'' | + | ==Principle== |
| − | '''Code''' | + | ==Code== |
| − | '''Download''' | + | ==Download== |
| + | ==External Links (More)== | ||
Revision as of 15:08, 26 August 2016
The Manual of Style (abbreviated as DCMoS, DCMOS or MoS) is the style manual for all Design Computation articles. This primary page of the guideline covers certain topics (e.g. punctuation) in detail and summarizes the key points of other topics. The detail pages, which are cross-referenced here and linked by this page's menu, provide specific guidance on those topics. If any contradiction arises, this page has precedence over all detail pages of the guideline.
Contents
Categorizing Pages
Design Computation wiki generates a page collating all categorizations applied in the database.
History and Theory Pages
History and theory pages uses similar style to Wikipedia but are somehow shorter and focus only on computational design taxonomies, cultures and ontologies.
Application Pages
Design Computation Application pages refer to material and methods shared by contributors for the resolution of design issues. This is often associated to live projects in the industry.
Tutorial Pages
Tutorial pages should contain a Title, the Abstract'only, with no ellaborate introduction, the Principleexplaining in detail the underpining rationaly of the principle being applied in the tutorial, the Code sample and finaly, whenever possible the Download for tutorial files.
