Difference between revisions of "ToDo list"

MuseWiki, wiki for the band Muse
Jump to navigation Jump to search
 
(2 intermediate revisions by 2 users not shown)
Line 3: Line 3:
==Royal pains in the arse==
==Royal pains in the arse==
*Publicise. Srsly, need wider exposure.
*Publicise. Srsly, need wider exposure.
*Replace all instances of '''Image:''' with '''File:'''
*Use [[Template:Backto]] at the foot of each page
*Use [[Template:Backto]] at the foot of each page
*Hunt for links to and bypass redirects
*Hunt for links to and bypass redirects
<span style="color: #0f0; float: left">✓</span><ul><li style="list-style-image: none; list-style-type: none !important"><del>Roll out the [[Template:Setlist | setlist template]]</del></li></ul>
<span style="color: #0f0; float: left">✓</span><ul><li style="list-style-image: none; list-style-type: none !important"><del>Roll out the [[Template:Setlist | setlist template]]</del></li></ul>
<span style="color: #0f0; float: left">✓</span><ul><li style="list-style-image: none; list-style-type: none !important"><del>Replace all instances of '''Image:''' with '''File:'''</del></li></ul>


==Layout and appearance==
==Layout and appearance==
Line 14: Line 14:
*Investigate, design and implement a way of laying out media verification hash tables within pages
*Investigate, design and implement a way of laying out media verification hash tables within pages
*Typographical students and those in the know: check whether our conventions are correct
*Typographical students and those in the know: check whether our conventions are correct
*People with Internet Explorer 8: Keep checking the wiki to make sure it displays correctly with IE8. IE is notorious for its layout engine being incomplete and buggy and MuseWiki developers don't use Windows.
*People with Internet Explorer 8: Keep checking the wiki to make sure it displays decently with IE8. IE is notorious for its layout engine being incomplete and buggy and MuseWiki developers don't use Windows.
*Use <nowiki><p></nowiki> instead of <nowiki><div></nowiki> and tables where appropriate, instead using appropriate CSS rules.
*Use <nowiki><p></nowiki> instead of <nowiki><div></nowiki> and tables where appropriate, instead using appropriate CSS rules.


Line 59: Line 59:
:Why :( --[[User:Crazybobbles|crazybobbles]] 20:58, 23 September 2009 (BST)
:Why :( --[[User:Crazybobbles|crazybobbles]] 20:58, 23 September 2009 (BST)
::We live in the UK foo', that shouldn't be a question that you have to ask. --[[User:Tene|Tene]] 21:19, 23 September 2009 (BST)
::We live in the UK foo', that shouldn't be a question that you have to ask. --[[User:Tene|Tene]] 21:19, 23 September 2009 (BST)
::: When is this gonna be implemented? [[User:Lazlo|Lazlo]]


*Set up wiki bots for admins
*Set up wiki bots for admins

Latest revision as of 09:51, 2 August 2014

This is a list of ideas which are deemed either sorely needed, useful or interesting. If you're looking for something to help out with, look no further!

Royal pains in the arse

  • Publicise. Srsly, need wider exposure.
  • Use Template:Backto at the foot of each page
  • Hunt for links to and bypass redirects

  • Replace all instances of Image: with File:

Layout and appearance

  • Hunt artefacts visible with various layout engines and fix them
  • Investigate recent CSS implementation, seeing whether any could be used to improve MuseWiki's appearance
  • Wade through our templates and simplify/prettify if at all possible
  • Investigate, design and implement a way of laying out media verification hash tables within pages
  • Typographical students and those in the know: check whether our conventions are correct
  • People with Internet Explorer 8: Keep checking the wiki to make sure it displays decently with IE8. IE is notorious for its layout engine being incomplete and buggy and MuseWiki developers don't use Windows.
  • Use <p> instead of <div> and tables where appropriate, instead using appropriate CSS rules.

Resources, searching and verification

Files

  • Hunt authorship and source information for uploaded files, tell authors about creative commons and ask whether they'd be happy licensing under a CC licence (tres cool)
  • Descriptions for files which currently have none

Gear

  • Expand and clean up the gear section—particularly suited to musicians in the know.

Gigs

Codemonkey bananas

  • Use HTML5 audio instead of the flash player for Chrome, Firefox, Opera and Safari
Doesn't conform to old browsers, sorry but I'd like to see the day come, but it's not going to happen :( --crazybobbles 20:58, 23 September 2009 (BST)
Use CSS which old browsers don't understand to hide it from them. :P --Tene 21:19, 23 September 2009 (BST)

  • Make references work for people who are not logged in
Should work now i think...--crazybobbles 20:58, 23 September 2009 (BST)
Eeexcellent.... --Tene 21:19, 23 September 2009 (BST)
  • TLS/SSL?
Why :( --crazybobbles 20:58, 23 September 2009 (BST)
We live in the UK foo', that shouldn't be a question that you have to ask. --Tene 21:19, 23 September 2009 (BST)
When is this gonna be implemented? Lazlo
  • Set up wiki bots for admins

What kinda rules are we talking about? Would be pretty fun to experiment on this but need situations where bots are useful --crazybobbles 20:58, 23 September 2009 (BST)

One situation where it would be useful is removing unknown variables, another rolling out simple templates such as backto, another sweeping for Americanisms. :P --Tene 21:19, 23 September 2009 (BST)
  • Get rid of px usage and use oooonly em
Meh they both have their uses :p --crazybobbles 20:58, 23 September 2009 (BST)
em should be preferred when it's not detrimental to do so /me rolls eyes. --Tene 21:19, 23 September 2009 (BST)
  • (Really) fix titles containing ampersands

  • Fix titles containing plus signs

  • Find a way of adding a captcha box

  • Add standard CSS3 border rules. These are implemented in Firefox 4+ and Chrome.

Long-term

  • Get each member of Muse to join and edit. Also known as "take over the world", with originality.


Go back to help