User:Mbrickn/Development
Books I started
editPlease help contribute!
Continuous Improvement
editContent complete at time of editing. I doubt these will ever be finished.
- How To Assemble A Desktop PC - Modernization
- History of video games - Major contributions
- US History - Sourcing and Improving
Developing
edit- College Survival Guide - Modernizing
- Art History - Expanding
- Home Remedies - Primarily fact checking and rewriting.
- Linux Basics
- Pokémon Crystal
Books I want to work on later
edit- File:InfinitiPlanet-Console.png
- amazon fire tv cube? File:AFTG.jpg
- Disaster and WMD Defence Guide
- Symptoms of Radiation poisoning.
- Colonizing Outer Space
- Human Geography
- When It Hits the Fan
- Energy Efficiency Reference
- GUI Design Principles
- Taxi Language
- Using DepEd Baguio CCApp
- Video Game Design/Archetypes
- French History
- Hawaiian Monarchs
- User Manual for OpenClinica - TOC
- Critique of the 1776 Commission Report
- Programming for the consultant
- Evolution of Operating Systems Designs
- Python book of magic
- Python Imaging Library
- Television Manufacture and Repair - Split and style.
- Understanding Multitouch - Content expansion
- Web Development - Content
- Carpentry
- Coordinate Reference Systems and Positioning - Split and TOC
- Contradancer's Guide to Successfully Beginning Scottish Country Dance - Split and TOC
- Understanding Home Finances
- Dendrochronology - Split and expand by citing EL Moseley studies and other early work.
Wikibooks thoughts
editTechnical
editThese are my personal ideas, and don't always represent the views of the community or official Wikibooks policy.
- Automatic credit tool for pictures in printable versions to comply with licensing. Ideally it would just be something like {{ImageCredits}}
- Optional automatic tool to take inline citations, and do traditional style references. This gives the advantages of inline citations for review, while preserving the readability of book style references.
- Add Template:Inflation from Wikipedia. Would be useful for history books, and aid maintainability of texts.
Philosophical
edit- As a reader, it's annoying to have underdeveloped books rated at a higher completion status then they actually are. However I find it more annoying when books that are complete, or are nearly so are rated as barely started. This does the reader a disservice because finding quality material is harder, and it does the editor a disservice, became it makes finding easily developed topics harder. Overall it harms Wikibooks to be overly cautious here. Of course, the inverse would be just as bad if it were as widespread.
- Recentism is an interesting issue.
- Indeed A Wikibook should be more than a collection of links to news articles. Yet the process of quality writing on a platform where anyone can edit, and really any serious academic writing, involves citing sources so claims can verified. Building a scaffolding of factual claims to later grow into a cohesive narrative is a good strategy, and withholding text from others until it is fully developed seems to defeat the purpose of a collaborative platform.
- Ongoing news and events should certainly be added with care, but if it is obviously in the readers interest and factual it ought to be added. The ability to keep content up to date is one of the major advantages of electronic books over physical books. It comes down to if an incomplete or underdeveloped section is more desirable than nothing at all. I would dare say most readers have the intelligence to value what information is available, and understand that ongoing stories may be unfinished.