Sep. 17th, 2011
For THEME Designers: Helping Patchers Out
Sep. 17th, 2011 11:38 amHere are a few things you can do to help developers patching themes. If you have the time and energy to do any of them, please consider it. Otherwise, don't worry, 'k?
-- Alphabetizing themes when your submit them seems like a tiny detail but actually makes editing our giant spreadsheet (currently at over 1,000 lines) ten times easier.
-- Keeping code lines alphabetized and removing any empty ones such as
-- Making sure you have set color_page_text as black may not be the default for everybody.
-- Keeping the # symbol before any color code. This one is pretty unexpected and very easy to miss so pretty please?
-- Using #000 for black and #fff for white instead of the full hexadecimal code. This works for #333, #666, etc.
-- Setting apart code lines which aren't color settings or things which won't end up in the theme such as module settings is very helpful too.
-- Sorting colors into categories -- page, header & footer / entry and comment / module -- would be most helpful, even if it's just by adding blank lines between section.
Besides testing, reformatting themes to sort settings into categories and adding proper headers is what takes patchers most time.
Here's a good example of what a color-only theme look like and here's another one with one with fonts, images and custom CSS.
Also, we've had about 200 new submissions since August. What have you been eating?! *is stunned*
-- Alphabetizing themes when your submit them seems like a tiny detail but actually makes editing our giant spreadsheet (currently at over 1,000 lines) ten times easier.
-- Keeping code lines alphabetized and removing any empty ones such as
set blahblahblah = ""; makes patching much easier and faster.-- Making sure you have set color_page_text as black may not be the default for everybody.
-- Keeping the # symbol before any color code. This one is pretty unexpected and very easy to miss so pretty please?
-- Using #000 for black and #fff for white instead of the full hexadecimal code. This works for #333, #666, etc.
-- Setting apart code lines which aren't color settings or things which won't end up in the theme such as module settings is very helpful too.
-- Sorting colors into categories -- page, header & footer / entry and comment / module -- would be most helpful, even if it's just by adding blank lines between section.
Besides testing, reformatting themes to sort settings into categories and adding proper headers is what takes patchers most time.
Here's a good example of what a color-only theme look like and here's another one with one with fonts, images and custom CSS.
Also, we've had about 200 new submissions since August. What have you been eating?! *is stunned*
Line Up (TABULA RASA)
Sep. 17th, 2011 07:18 pmTheme || Layout: Line Up (Modernity) || Tabula Rasa
Author:
timeasmymeasure
Layout Submission Type: CSS layout based off Tabula Rasa
Image Preview: http://i52.tinypic.com/200wety.jpg

Image Info: No images
Additional Info: CSS currently only works with "2 column sidebar right" but please feel free to fix that and anything else that needs fixing/changing. The name for this particular color scheme is Modernity.
CSS:
Originally posted over here.
Author:
Layout Submission Type: CSS layout based off Tabula Rasa
Image Preview: http://i52.tinypic.com/200wety.jpg

Image Info: No images
Additional Info: CSS currently only works with "2 column sidebar right" but please feel free to fix that and anything else that needs fixing/changing. The name for this particular color scheme is Modernity.
CSS:
Originally posted over here.