Last two days felt like a WordCamp. Since I published my previous post about releasing a WordPress plugin together on Tuesday almost twenty people expressed interest in co-releasing WordPress plugins. Can’t name drop everyone here, but @Josh412‘s enthusiasm about this is something that can’t be properly described.
So, How Do We Do It?
With so many people involved, we need a system or it all falls apart. For ideas and plugin discussion we’ll use P2 installed at make.wpcollab.co. It’s actually a mapped WordPress.com blog, so you don’t need to create another login, all you need is a WordPress.com account (this awesome idea brought to you by @cFoellmann). For development we have WPCollab organization at Github (still setting it up and adding people). There’s also #WPCollab on Twitter, if you want to join the discussion there.
We already have a few plugin ideas I think we’ll start working on over next few days. Check make.wpcollab.co for details and if you have your own ideas, please post them. Still don’t know what to do with main domain there, maybe list all contributors, or have a contact form, signup form, something like that? Suggestions?
If you’re in this and think we can improve the process, please share it here, on Twitter or make.wpcollab.co.
How You Can Be a Part of This
You don’t need to be a developer to contribute.
- If you’re a project manager, please help! I’m not a project manager, I just play one on TV right now.
- If you’re a designer, least you could do is create wordpress.org repository banner image for a plugin.
- If you’re a copywriter, documentation is something developers are usually too burned out to do after hours of coding.
- Finally, if you’re a developer, you probably know how to release a plugin. If you don’t, there’s enough of us who have done it and we’d love to guide you through the process. And if you’re really good, but also super busy, you could do a code review or share some workflow tips.
Not sure, but I think we can start actually working on some plugins this weekend. Let’s use today and Friday to decide which ones it will be and let people volunteer to work on them. What are your thoughts? Anyone up for some weekend side projects?
Last weekend I was lucky enough to attend WordCamp Norway. It was my first WordCamp since the big one in Leiden last October and even though this one was smaller in numbers the vibe was the same. It was so great to see some of the familiar faces again. The only things missing were North End pub and poor Wi-Fi
As much as I loved WordCamp Europe, looking back I feel like I blew it. Coming back I was full of ideas, planned to get in touch with people I met and build all those cool things speakers were talking about, blog about it and who knows what else, but it didn’t really happen. I really want this time to be different.
Last February Tom McFarlin, Pippin Williamson and Andrew Norcross did something similar when they released Comments Not Replied To plugin. For added degree of difficulty they did it during a WordCamp, which makes it even more awesome.
If you’re a developer thinking about releasing a plugin, let’s do it together. I’m sure we can learn from each other while doing it.
Main reason I want to do something like this is so I could work with another WordPress developer. I really love my job, but I’m the only WordPress person there and that’s hardly ideal if getting better at WordPress, as fast as possible, all the time, is your goal.
A few things though, it has to be free, released to wordpress.org repository and lean. Other than that, anything goes. So, let’s do it together. Leave a comment or send me a tweet if you’re interested.
Continuing the tradition established by Rhys, Nuno, Jeremy, Daniel, Florian and Thomas I’d like to introduce myself as well:
My name is Slobodan, I live in Västerås, Sweden (moved here yesterday, actually) and WordPress has been a huge part of my life since 2007. The reason I fell for it is the same reason so many people have when they chose WordPress over any other CMS – its simplicity. The reason I stuck with it is a bit more complicated, though. At the time I started learning about WordPress development I was studying for a profession I didn’t really care for, doing a job I didn’t feel like doing, desperately looking for a way to change my life.
Turns out, WordPress was my way out and that’s why I’m so crazy about it staying as easy to use as it is now, if not easier. I honestly think that if WordPress’ learning curve was steeper than it is, lives of so many WordPress professionals, mine included, wouldn’t be as good as they are now. So if you’re not a fan of stupid, mile-long options pages, blurred lines between themes and plugins, anything that prevents you from being able to just publish and worry about what you’re publishing vs. how you’re publishing it, I would love to meet you in Leiden.
I’ll arrive in Leiden on Friday evening, so if you’d like to discuss any of these, please get in touch:
- Theme development and blurred lines between themes and plugins
- Challenges of selling organic themes (organic = would pass wordpress.org theme review) in WordPress marketplaces
- Contributing to WordPress – see you at Contributors Day
- NBA, cause new season is right around the corner
You can connect with me on Twitter, or you can send me an email, whichever is easier for you. See you there!
Featured image credits: Flickr
Flexible is good, at least when it comes to websites. After all, responsive has been THE buzzword of all buzzwords for quite some time. Using media queries, you can make a three column layout switch to two columns, than one, depending on width of device website is being displayed on. But what about setting number of columns based on content? Easy, using WordPress widget areas. Continue reading
Last June Dragan and I published our very first public WordPress plugin. It was pretty successul, still sells well, so if you need an author box WordPress plugin for your blog, please check it out. End of plug, I promise.
We had no idea what to expect, more than anything how much time we’d spend supporting the plugin. Turns out that even the little worry we had was there for no good reason. Of course, that doesn’t mean there were no support requests at all. However, huge majority of them were not caused by our plugin doing something wrong, but by it not being allowed to do something right instead. Continue reading