Portal:Social entrepreneurship/lessonslearned

Personal reflections by authors intended to improved processes of Wikiversity project development.

Technical
Sometimes a small thing can take a lot of time to find and sort out. For example, for some time I could not use multiple style elements with my theme templates. The problem was eventually solved by having no space between the end of the template definition " }} " and the " " tag which followed it.

So, here please list any reminders:


 * Convert spaces to underscores in a path - solved via (note the 'e').
 * At the end of a template definition, insert no space between the end of the template definition " }} " and the " " tag which normally follows.
 * For colour values in templates which return them, try returning the quotes too if the "#" is being interpreted as a numbered bullet for example. This should not be necessary and may indicate another problem.
 * Remember to end the template with the tag (and not a Category tag for example).
 * For main (default) name space references try : (note the ':').
 * If there are spaces in the FULLPAGENAME try : (note the extra 'E').

Links to resources for learning wiki markup

 * Parser Functions
 * Parser Function

Methodology

 * Remember the xP/agile 40 hour weeks rule.
 * Document your design decisions for quick answers to the question "Why did I design it this way?"
 * Track issues in one place - e.g. Issue Tracker.
 * Could be handy to maintain a test page which tests key things spanning a project.
 * Visit it on a regular basis.

Templates
Learned a lot about separation of concerns. Still much to learn.


 * Do not send parameters to named navigation templates which occur on each associated page of a course. The idea is to have a fixed view template for that page set.
 * Generic boxes: within the definition of the template, do not include references to project-specific templates.
 * this raises a question about when to elevate a project-specific template to something more generic for Wikiversity.