Adds ‘via @username’ to the Tweet Button provided in “Jetpack by WordPress.com”
This plugin needs Jetpack by WordPress.com to be activated and its Sharing module to be enabled.
Enter the desired Twitter usernamen in Settings -> Sharing. It will then be appended, every time a visitor shares your content on Twitter
See the Tweet Button documentation for details.
I will be more than happy to update the plugin with new locales, as soon as I receive them!
Currently available in:
- Download Jetpack Twitter Via.
- Unzip the folder into the
- Activate the plugin through the ‘Plugins’ menu in WordPress
This year has been a wild ride for me so far, and it doesn’t show any signs of slowing down. I became a member of the WordPress Theme Review Team, had my first patch make it into Core, worked with Lance Willett and Drew Strojny on Twenty Twelve, was invited to the WordPress Community Summit, graduated college, moved to the United States and also attended my first WordCamp.
Today marks my first day as a full-time Theme Wrangler at Automattic, the company behind WordPress.com. I’m beyond excited about joining this crazy talented team of Themers and to become a member of the Automattic family. This is without a doubt the highlight of my WordPress career and truly a dream come true!
Today I received the following question through the contact form on my site:
Given that some sites sell WordPress Themes without checking for quality standards, what would be the right way to sell WordPress Themes?
To me it doesn’t really matter whether the Theme Marketplace you sell your Theme in requires a certain level of quality in the Themes it sells or not. As long as your Theme is coded in a way it would pass a Review from the WordPress.org Theme Review Team, your customers will notice and you will be all good.
So tip would be: Choose the marketplace(s) that pass(es) the T-shirt test!
P.S.: I know the title of this post maybe
misleading a little strong, but hey, it was the subject line of that email! 🙂
My first patch to WordPress was basically just turning the recommendation that was given in-ticket into a patch. This was in June 2011 and is still waiting for further attention. But to be honest, at that time it wasn’t necessarily as much about the content of the patch for me as it was about creating a usable SVN patch in the first place. And actually submitting it. So it seemed like the perfect opportunity, since the content was pretty much outlined already.