yakovl / tiddlythemes_fork Goto Github PK

Here's a bunch of things that should be done to make this usable and useful:

• index: fix main column (make left ~sidebar scrollable)
• index: remove bg color and title underline from MainMenu
  • review style updates here, merge good bits
• update readme
• index: update page title
• decide the structure of info (readme, intro tid, this issue), update readme again
• index: add an Intro tiddler to display on start:
  • explain status
  • explain/link how to view/install a theme
  • explain/link how to and encourage to contribute
• link this in c.tw.com, dev; announce and invite to help with this updating process
• index: add ~constant permaview to the index (opening Devfire should set hash to #Devfire)
  • highlight the open theme in the main menu
• test on a single theme (blackicity; bleach):
  • update TW to 2.9.4, preview image, do minor adjustments
  • move files into the themes/ folder (blackicity, bleach – but these don't involve other assets, unlike some themes)
  • pack into an actual TW theme (blackicity, bleach)
  • optionally, refactor the theme (reuse ColorPalette, remove styles that don't alter defaults, lint)
• pack themes and images into the themes/ subfolder
  • prefix all images with their theme name
    • tiddlypedia: bullet.gif, external.png, headbg.jpg, wiki.png
    • gtd: bodygradient.png
    • monkymind: blue.swf (but it's actually 404.html, may be drop instead)
    • ijobs2: chronograph.swf (but it's actually 404.html, may be drop instead)
• update TWs to 2.9.4 (ideally, set autoupdating core if possible, or at least an action to update all at once)
  • this will require review of result for each theme on the first update
  • update images accordingly (and in a higher res)
• create a EEP collection, index all themes (may be extract them into small files)
  • pack into actual TW themes
    • this will require review of result for each theme on the first update
  • add responsive theme there

Other optional bits:

• ensure CSS includes [[StyleSheet]] to keep user customizations;
• lint CSS;
• ensure compatibility with DarkModePlugin;
• ensure responsiveness.