• The wise writing from Dave Pollard about Un-learning to play. I find his let-self-change  concept both powerful and poetic. Change is a posibility most of the time.
• Dave also writes about building natural enterprise. How to make a living doing what is relevant.
• The road itself is inspiration: social media, online conversations, blogs, … whatever, just watch your steps.
• People like Crossfit-Hq demostrate the many niches available for meaningful, community-based business.
• Small changes, a word at a time, that invite to change and reflection, ecopreneur, entregreeneur, communities of practice, openspaces.

And from the experiences of people playing with money and free/open software:

• Running your company as an Open Source Project
• Software as a public good
• The meatcloud manifesto: men trying to tame infrastructures and meatclouds, and making money in the process.
• And learning from the errors of others, never forget that money changes everything.

I’m trying to collect some good practices and advise for those trying to add i18n support to their themes:

• Read the WordPress documentation on i18n. Print their best practices, put them in a visible place and recite them before any i18n effort.
• Use plenty of format strings. Ok, you already read the best practices, so you known I’m repeating them here. For better format strings use descriptions and comments (the _c() function)
• Use boilerplate copy everywhere. Don’t be too original with the text you include in your theme; “Submit It” better than “Say It Pal!” for a submit button. If your theme includes strings used by most other themes, chances are those strings are already i18n and l10n in . You can always have private copies of your theme with unique headers, titles, and button; the version you share should be as plain and simple as possible.
• Keep out strings that need no translation: and don’t skip small strings subject to translation; alt and title html parameters, submit buttons value, next|prev_post_link and other wp template tags, all accept i18n. See the next two samples; why “Comments” is left out of the _e() function?; is there a translation for ‘|’ in any language?
  

  <?php _e($numComments, ‘XXXXXXX’); ?> Comment(s)

  __(‘ | ‘)

The last and best tip is to use a theme with good i18n support and clean code as base template; sandbox is a great, clean, and fully i18n WP theme.