v50 Steam/Premium information for editors
  • v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
  • Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.

Editing 40d Talk:Your first fortress

Jump to navigation Jump to search

Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.

You are editing a page for an older version of Dwarf Fortress ("Main" is the current version, not "40d"). Please make sure you intend to do this. If you are here by mistake, see the current page instead.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 183: Line 183:
 
::: I suggest that if you want to "completely rewrite" a tutorial, it would be better to keep the tutorial as it is and write up a completely new one. A variety of examples is more useful than a single thoroughly edited tutorial. There are differences between a Prima Strategy Guide and a wiki. These differences should be harnessed in a way that empowers the wiki.  
 
::: I suggest that if you want to "completely rewrite" a tutorial, it would be better to keep the tutorial as it is and write up a completely new one. A variety of examples is more useful than a single thoroughly edited tutorial. There are differences between a Prima Strategy Guide and a wiki. These differences should be harnessed in a way that empowers the wiki.  
 
::: Here's an example that is beyond my own wiki-editing capabilities, but should give ThunderClaw what s/he's looking for without requiring a complete rewrite, or a new tutorial: create a "why" tag which, like the verify tag, allows newbies to easily ask for expansion.  This could even be a FAQ-like new category, so that we could quickly edit this tutorial in small, easily managed chunks that more users would likely contribute to. Eg,
 
::: Here's an example that is beyond my own wiki-editing capabilities, but should give ThunderClaw what s/he's looking for without requiring a complete rewrite, or a new tutorial: create a "why" tag which, like the verify tag, allows newbies to easily ask for expansion.  This could even be a FAQ-like new category, so that we could quickly edit this tutorial in small, easily managed chunks that more users would likely contribute to. Eg,
[[Temperature]], amount of [[tree]]s ([[why trees]]?), amount of [[plant]]s ([[why plants]]?), and a hint at the sort of [[Animal|wildlife]] ([[why hunt]]?) at the center of the selection rectangle.
+
  [[Temperature]], amount of [[tree]]s ([[why trees]]?), amount of [[plant]]s ([[why plants]]?), and a hint at the sort of [[Animal|wildlife]] ([[why hunt]]?) at the center of the selection rectangle.
 
::: Put another way, introduction to concepts and keyboard commands should be distinct content, and a step-by-step guide should contain only enough enumeration and/or examples to cover all exceptions once. Additional exploration should be available as links. But then again, that's just my take on it, and the prize goes to the guy who actually does the deed. --[[User:RomeoFalling|RomeoFalling]] 20:38, 4 November 2008 (EST)
 
::: Put another way, introduction to concepts and keyboard commands should be distinct content, and a step-by-step guide should contain only enough enumeration and/or examples to cover all exceptions once. Additional exploration should be available as links. But then again, that's just my take on it, and the prize goes to the guy who actually does the deed. --[[User:RomeoFalling|RomeoFalling]] 20:38, 4 November 2008 (EST)
 
::::That is a good way to deal with the ''example'' part of what I was talking about.  It'll shorten the article fantastically for people who don't feel they need detailed explanations, but it doesn't address the other problems: bad enumeration and incomplete explanation.  The bad enumeration part is really what's killing this guide most, because many times concepts run together and it's difficult follow.
 
::::That is a good way to deal with the ''example'' part of what I was talking about.  It'll shorten the article fantastically for people who don't feel they need detailed explanations, but it doesn't address the other problems: bad enumeration and incomplete explanation.  The bad enumeration part is really what's killing this guide most, because many times concepts run together and it's difficult follow.

Please note that all contributions to Dwarf Fortress Wiki are considered to be released under the GFDL & MIT (see Dwarf Fortress Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Please sign comments with ~~~~

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)