<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>I dunno.<br><br>I remember being determined to update the wiki after seing the same void pages for years.<br>I wasnt great at adding content when I started, and I see im not adding some of the correct content now.<br>So I can try and adapt, but it seems there will probably a new process in the future anyway.<br><br>..<br><br>Usually I copied 2.4 or added the same kind of content others added.<br>Which kinda grew in to this style.<br><br>Intro<br>- What it does. What its used for.<br><br>Elements<br>- Parts unique to the user interface or subject.<br><br>UI Reference<br>- Reference for panels, header buttons, with extra info.<br><br>Menu Reference<br>- Reference for the menus in the editor.<br><br>Editing Reference<br>- Relative operators with context mode and keyboard reference.<br><br>Workflow<br>- An example of a process or hidden process related to the subject.<br><br>Examples<br>- Examples with a picture, description, and maybe blend file.<br><br>Trouble Shooting<br>- Common problems related to the subject.<br><br>Notes<br>- Importent notes related to the subject.<br><br>There wasnt really a guide on what content to write. There were some examples but it wasnt well defined.<br><br>I kind of realize the reference is not something desired, and I agree.<br>I think it can be good for some pages like keying sets: http://wiki.blender.org/index.php/Doc:2.6/Manual/Animation/Basics/Keying_Sets<br>Its nice way to find an operator or property, but not all operators and properties need to be reference.<br><br>I dont think its good for editors, with the header menus.<br>With an editor its probably best to write an editing page with basic controls.<br>Its probably best to just describe what the panels are for and only add extra info for different properties and operators if desired.<br><br>I would like it if there was more info, like What To and What Not To write, with well defined examples.<br>But thats up to the developers.<br><br>..<br><br>Anyway from what ive read so far, I like what is proposed.<br><br>I like the process of a user saying, 'Hey thats not mentioned in the doc, add to doc' like a bug report.<br>This would probably be a better process to follow.<br>Theres some features for Drivers ive recently discovered, like adding #frame to a property will add a scripted expression driver.<br>And if a user wants scripted expression objects to update in the UI, they have to add the object id to a driver variable.<br>These would be good Bug Report/Todo examples.<br><br>Id also rather follow a process of adding proposed fixes for TODO's to a webpage, then its up to a developer/reviewer to add, partially add, reject, and give feedback.<br><br>I think the current old Writers Guide can be a hard read for new users.<br>If you do want user contribution, It would be nice if a new one could be written, for if/when to new manual is online.<br><br>..<br><br>I probably wont update the wiki doc much this year, unless a new directive is added.<br><br>I like the new webpage for the doc, and I hope it works, if user contributions exist or not.<br><br>Koilz.<br> </div></body>
</html>