Posted 03.10.2010 by Jack
Jen Simmons on the Bartik theme
- Garland - been around since D5 as the core/standard theme
- D6 - use a good base theme to override crappy HTML in core
- D7 - folks focusing on making core tpl's non-crappy
- Stark theme - "Zen Lite" - see the HTML that comes straight out of the core tpls - better theme to adapt than Garland (don't do it!)
- Seven - the new core admin/back end theme
- Bartik!
- new core theme, but it's not actually in core yet because it's not done
- Check it out at http://bartik.milkweedmediadesign.com
- Named after Jean Bartik, one of the original ENIAC computer
- New featured region - hide all the blocks in the content and sidebar regions, but it doesn't work yet because of a D7 bug
- $content is now a block in D7! Should be hideable/disableable... but it's not quite yet.
- "If you let people hide content everywhere, then unicorns will die..."
- triptych regions (first middle last) with three boxes in a row
- footer-columns regions (first second third fourth) and footer region and header region all make menus look different when dropped in (see the demo site)
- Bartik rounded corners are CSS3, woohoo. Also, gradients, text shadow, etc
- Imagecache is in core in D7 (woohoo!) so it's utilized in Bartik
- Color module - was written for garland, but it can be shoehorned to work with other themes
- Get the source: http://github.com/jensimmons/Bartik
- Check it out on Drupal.org: http://drupal.org/project/bartik
- Most likely the Bartik issue queue will be on drupal.org but code development will be on github for the foreseeable future
- Jen doesn't have plans to backport it to D6, but there is interest and would make sense once the D7 version is tight
Orbgasm (Can Alptuna) (and audience) on Freelancing
- Notes from Can's talk, so I won't be taking notes in deep detail. (Note, this link is not an endorsement of certain elements of the PDF, e.g. that "don't be a pussy" comment!)
- in your proposals, break things down into phases that are well defined so that the client knows exactly what you're planning/committing to, no surprises for anyone down the road
- don't sign any contracts until those details are hammered out
- be up front about who you are so that you know you're a good match with your client, their image/politics/style
- idea on copy: bill .20/word to "copy and paste" content into the site (since it's usually not in an easy format to copy and paste in); bill .50/word to actually write content
- let clients know that Drupal is under GPL, so they're clear on licensing
- be clear about who owns the code you write - good idea to explicitly GPL it so client's don't think they own the code