FS#2186 Suggestion: Identify past depot changes that are good examples of common tasks

Docs

• 

  2011-02-27 waltergr

  While http://www.dokuwiki.org/development is a good starting point, it would be awesome to be able to see diffs of past changes that are good examples of common development tasks.  (By "good" I mean: well-coded, do everything correctly, follow style guidelines, well-commented, etc.)
  
  These diffs could be linked in the development section of the wiki.  As an added benefit, this would eliminate the need to write additional developer documentation.  That takes time - and the diffs are available right now.
  
  Some example common tasks off the top of my head:
  
  *  creating a unit test
  *  adding a configuration option
  *  adding a new localization language
  *  adding new syntax
  
  (I'd do this myself, but I don't have sufficient understanding of DokuWiki's internals.)
• 

  2014-05-09 Klap-in

  Is this worth the effort?
  
  The current development manual contains already different little examples.
  
  Today, when checking the examples of your short list, the development notes contains explanation of the ideas, samples and sometime pointers to real code. Quite neat.
  https://www.dokuwiki.org/devel:unittesting
  https://www.dokuwiki.org/devel:configuration
  https://www.dokuwiki.org/devel:localization
  https://www.dokuwiki.org/devel:syntax_plugins
  
  I propose closing this issue.
  My suggestion is that when you encounter a development subject or current pages, which require more information/examples/etc, you add a note for these at https://www.dokuwiki.org/teams:documentation or create a separate issue for it in the issue tracker.