Update design task and todo task instructions.

webroot/rsrc/custom/static/design_guidelines.html

@@ -1,2 +1,16 @@
-Design tasks are created by developers and module members to work out the design of functionality, and involve the community for feedback. They are not intended to be created by users, rather the focus is always on functionality that developers plan to work on.
+<h2>What is a Design Task?</h2>
+<br/>
+
+<p>Design tasks are created by developers and module members to work out the design of functionality, and involve the community for feedback. They are not intended to be created by users to propose ideas or request features, rather the focus is always on functionality that developers plan to work on or ask others to help out with.</p>
+
+<br/>
+
+<h2>Guidelines</h2>
+<br/>
+
+<ul>
+<li>Explain why this change or addition is needed</li>
+<li>Try to figure out weak points in the design and how they can be mitigated</li>
+<li>Write concise and structured</li>
+</ul>
 

webroot/rsrc/custom/static/todo_guidelines.html

@@ -1,2 +1,9 @@
-To Do tasks are created by developers and module members to track To Do items. They are not intended to be created by users, rather the focus is always on tasks that developers themselves plan to work on.
+<h2>What is a To Do Task?</h2>
+<br/>
+
+<p>To Do tasks are created by developers and module members to track To Do items that are not bugs, patches or design. They are not intended to be created by users, rather the focus is always on tasks that developers themselves plan to work on or ask others to help out with.</p>
+
+<br/>
+
+<p>Examples include: reminder to clean up code before the release, to add test files for a new feature, create a tutorial for a new feature, fix broken links in documentation, ..</p>