How To: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(even more ^_^ (Imported from MoinMoin))
((Imported from MoinMoin))
Line 24: Line 24:


** [[How To Add Script And Language|HowToAddScriptAndLanguage]]
** [[How To Add Script And Language|HowToAddScriptAndLanguage]]
** [[How To Get Your Edits Accepted|HowToGetYourEditsAccepted]] ''(I'm thinking this can be a page where we describe the most common reasons for down voted edits, and how we want people to use the database, etc.)''
** [[How To Get Your Edits Accepted|HowToGetYourEditsAccepted]] ''(or Moderations in [[Bad Terminology|BadTerminology]])''
<ul><li style="list-style-type:none">What about the much simpler [[How To Get Your Edits Accepted|HowToGetYourEditsAccepted]]? ''agreed, much better, but I'd use 'mods' of course.''
</ul>
** [[Advanced Relationship|AdvancedRelationship]]<code><nowiki></nowiki></code>s
** [[Advanced Relationship|AdvancedRelationship]]<code><nowiki></nowiki></code>s
*** [[How To Make Relationships|HowToMakeRelationships]]
*** [[How To Make Relationships|HowToMakeRelationships]]

Revision as of 21:45, 5 February 2006

This page gives a structured overview over existing and planned HowTo's. For a plain list, see the. HowTo's are the lightweight, user-orientated part of the MusicBrainzDocumentation. The pages' stress lies on tutorials and not exhausting exact documentations.

If you want to create a new HowTo, please consider the following points:

  • Use the HowToTemplate for the layout of new pages.
  • Titles of HowTo pages always start with "HowTo". The titles should not contain complicated MusicBrainzTerminology but be simple and orientated at what the users could look for. E.g. HowToMakeRelationships rather than HowToAdvancedRelationships.
  • Find a good place in the structured list below to link to your HowTo. Don't think about the technical background of it but where users would expect to find it.
  • Remember: HowTo's should just be simple step by step instructions for how to do things, not document features! You can link to the documentations for further information though.
  • For short questions we have the FrequentlyAskedQuestions, so HowTo's should be a bit longer than that. ;)

Existing and Planned How To's

  • Development
    • ...