document skins

[Owen Williams]

We are getting more bug reports to which the answer is "this skin is tricky, do this thing". So we should create wiki pages for the skins and explain the advanced features and hidden buttons. This esp goes for Deere, and for effects in general.

[Owen Williams (ywwg)]

and Deere has a friggin' menu, so maybe we can add a link to the wiki from the skin itself?

[RJ Skerry-Ryan (rryan)]

Maybe it would be more appropriate to have a manual section on the skins (so that old vs. stable vs. beta versions have their own pages)?

[RJ Skerry-Ryan (rryan)]

Following that logic would suggest we do the same for controllers though. Maybe some dokuwiki -> RST converter?

[Owen Williams (ywwg)]

yeah I agree, controller wiki pages should be in the manual as an addendum. So yeah, skins too. Automating it would be great.

To be clear, I think wiki pages for skins is sufficient for this particular bug

[Be (be.ing)]

If skins need their own documentation, we have failed badly in designing them. We have well designed skins now with only minor differences in behavior. Anything that needs to be explained in skins should be handled by tooltips, not the manual.

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/8379