Last modified on 11 August 2011, at 06:02

Blender 3D: Noob to Pro/Todo

This page is for suggesting and tracking ongoing maintenance for the book "Blender 3D: Noob to Pro". If you want to add another suggestion to the list there that isn't already there, go ahead. If you have a problem with one of the suggestions or want to remove one, please discuss the reason why on the talk page first.

Pages to take care ofEdit

Unit 1 and Unit 2Edit

  • Blender 3D: Noob to Pro/FAQ The page is outdated and the answers are not very good. The FAQ page does not fit well in the scope of the book. We could use a FAQ about the book itself though. There are better FAQs around. Suggestion: rewrite the page to make working with the book easier.
I rewrote it to be clearer about its (the page's) purpose and make it more readable, without changing the content. I think it's a worthwhile page, though not really a FAQ per se. We could possibly rename it About This Book or something. Dolsson5 (talk) 05:18, 12 May 2010 (UTC)

Unit 3Edit

Unit 4Edit

SuggestionsEdit

  • Standardize the commands and instructions to one keyboard layout and operating system (i.e. Linux QWERTY United States English) and break out the alternative options (e.g. differences on Mac or DVORAK) into side boxes so they don't interfere with readability. The troubleshooting and alternative command options interfere with the readability of instruction steps because you have to wade through excess irrelevant information. these alternatives should be migrated either to the end of each article/section or to some offset side boxes with labels like "Troubleshooting" and "alternative command sequences" so that each set of instruction steps stands alone, so it's easy to separate the actual instruction sequence from the side notes and easy to pick out the differences between your system and the system the book/tutorial was written for. Alternatively make each page devoted to one OS, and do other pages, e.g.: http://en.wikibooks.org/wiki/Blender_3D:_Noob_to_Pro/Making_Fire?linux etc. (note: other OS's will have their own ID, such as linux, win, mac, etc., these should be self explanatory). This link will obviously lead back to the ordinary page http://en.wikibooks.org/wiki/Blender_3D:_Noob_to_Pro/Making_Fire.
OS separation is neither useful nor necessary. Only a few pages about the interface would contain any real differences. --SoylentGreen (talk) 19:51, 2 June 2009 (UTC)
  • The ideal layout would be completely writing out and capitalizing the keys, like Control-S, Alt-V, and Super-Q. "Meta", "Windows Key", and "Command" should not be used, but the difference (as stated above) should be in some little box called "Formatting Conventions" near the beginning.. "Keystrip 5" and "Numpad 5" would be a good way to differentiate between number keys, and letter keys should always be capitalized if they are being instructed to be pressed.
  • Always provide the regular Menu path to get to a command (at least the first time) or note that a regular Menu path doesn't exist. Too often the only option provided is a key sequence and the location of the command in the menus is not shown/known. Hot keys should be more along the lines of optional to learn, though obviously in blender it's good to know some of your standard keys, and some key commands possibly don't have a menu equivalent, but Menu paths should always be provided (if they exist) at least the first time a command or key is used/introduced.
  • The intro of the book states that beginners need to read the chapters in sequence but there is a lot of repetition of the beginner information in later tutorials. Again this reduces readability because one must wade through irrelevant information. Remove the beginner explanations from later tutorials and instead include a disclaimer at the top noting the other pre-requisite tutorials.
  • The inter linking of many pages does not fit to the TOC of the book, this should be fixed.
  • Cleanup the "beginner" tutorials section of this book, many tutorials do not seem that beginner and are not even that clear.
  • Redo the beginning section to have a continuous sequence of tutorials.
  • Remove most of the chapter style links connecting unrelated tutorials and instead list the tutorials by subject matter (similar to this)
  • Have a link in the modules going back to tutorial indexes sorted by difficulty and / or subject (i.e.:"back to beginner tutorials list" instead of "next chapter")
  • Remove the "noob note" discussions on the modules and move them over to the talk pages.
  • Link to related content that helps readers locate tutorials that explain topics which the current one assumes knowledge of (similar to {{Template:Japanese related}} for the Japanese wikibook)
  • Add a version note to each tutorial and each image. For the images this should be done by the uploader.
  • Move the mostly unfinished (or unreadable) articles into a development section (similar to How To Assemble A Desktop PC/Development), then move them back into the book once they reach a more complete / understandable state
  • Move all the external links to the tutorial links list, or remove them simply, because they didn't belong here anyway.
  • Create a page about the scope and the purpose of the book
  • Add a flag for excellent tutorials, that may be used as a guideline on how to write tutorials.

DoneEdit