I've had a few questions via Twitter and Email about when things will be ready for EE3. Here is what I can tell you...
If you caught the email blast that was sent out last month, then this isn't news to you. If you missed it or your email automatically filtered it to your spam folder, keep reading.
ExpressionEngine 3 is around the corner, which means devs are scrambling to upgrade their add-ons. Here are my plans:
On November 1st, 2015 Devot:ee will increase their take on all sales from 20% to 30%. To offset this increase, All BoldMinded add-ons will increase in price accordingly. Prices will be adjusted just enough to offset the additional 10% increase to keep our revenue per add-on sale about same as it was when Devot:ee took 20%. For instance, Publisher will increase from $175 to $200, which means we still recieve $140 per license sold.
I've been thinking about this for months now, every time an obscure bug report comes in I tell myself I'm going to stop selling it.
As many of you know ExpressionEngine 2.7 is on the horizon. What that means is there will be many people still using the 2.5 branch, a few brave people using 2.6 and some even braver people jumping to 2.7. It also means that there can effectivley be 3 different relationship fieldtypes in play depending on which version you're using (old relationship field, new relationship field, and Playa).
In the summer of 2011 I tweeted about a very large project I was working on, victaulic.com, and included screenshots and even a video demo of an add-on I created for it to allow for publishing workflow and translations. At the time there was nothing like it for ExpressionEngine 2, thus I had to build it from scratch. The result was a module called Uhura.
I'm proud to finally release Blueprints 2.0. If you follow me on the Twitters you might have seen me tweeting "Blueprints 2 will be released soon," or some variation of that for the past several months, if not year. To some it might have appeared to be vaporware. Rest assured it is not, and I have learned my lesson about tweeting things too early.
Sometime back in October 2011 Marcus Neto posted a tutorial on expressionengine.com on how to build a custom support ticket system. I thought his approach was very intuitive, and the best part is its completely customizable. Prior to the Devot:ee support forum launch I had I tried GetSatisfaction, which was OK, but didn't feel it was the best tool. The best part about the Devot:ee forums is convenience for customers, but its feature set is, how should I say it, limiting. It works fine, don't get me wrong, but I want and need more control.
At The Nerdery when someone does something exceptional during the week they may get "Shout Out" from another employee. You might get a shout out by stepping in and helping out another developer with an issue, or going above and beyond your job title, or just being full of awesomeness. The shout outs may come in the form of a simple form submission on our intranet, or a full blown video (I would link to a video here but they are private due to possible NDA, and while not necessarily a shout out video, you can watch these to get an idea of the production that we put into these goofy things). At the end of the week at our company Bottle Cap where we present a recently commpleted project to the rest of the company, 5 randomly selected shout out recipients win free lunch the next week on behalf of the company. A pretty cool perk if you ask me.
Over the next few days I'm going to be posting some download codes with a corresponding URL on Twitter. The code will only be valid for 3 file downloads, or more accurately, 3 page loads with a valid download code. If you get lucky enough to be one of the 3 people who have entered a valid code you will receive a download link to an add-on zip file. Once a valid code is entered 3 times, the code is no longer valid, so you'll have to be fast to win a copy of something.
With regret I have decided to stop supporting the Images outside of p tags option in Wyvern. I created the option when Wyvern was originally WYMeditor for ExpressionEngine as a way to provide better HTML output from the editor. It's not very common that you want your image tags wrapped in a p tag. If anything you don't want them wrapped at all, or within a span or div tag as a last resort.
Before I started selling add-ons commercially, I sold Custom System Messages through a "donation required" model. I suggested a price of $10, but left it up to the buyer to decide how much they pay. This model works. Here are some numbers from when I sold CSM this way:
Disposition is the result of an idea I had over a year ago for sorting entries on the edit list page. It's something I've been meaning to get around to creating, but just kept pushing it off, then finally a few weeks ago started to put something together.
Wyvern now includes even more 3rd party add-on support. Taxonomy and NavEE users can easily link to their pages through Wyvern. With the addition of these two modules Wyvern now supports all the navigation add-ons for ExpressionEngine 2.
About 4 years ago I was looking for a simple and clean WYSIWYG editor for a project and stumbled upon WYMeditor. It had everything I needed without any extra cruft, and produced clean HTML. It has since been my go to editor.
This past weekend I tweeted about the awesome multi-lingual add-on I just got working. I think it's so awesome that I just can't wait to share some details...
CSM is now a commercial add-on available for purchase on Devot:ee. I've been thinking about this for awhile, and the main reason is to centralize all my add-on sales into 1 place. It's difficult to manage 2 different sales models setup on 2 different sites. This is the first step in migrating everything to boldminded.com.
This is without a doubt the biggest release day for my add-ons. WYMeditor 2.3, Blueprints 1.2.7, and my latest add-on, Super Globals 1.0b are now out. To celebrate each one of them are on sale for $10 for the next 24 hours. w00t!
Last week I released version 1.2.5 of Blueprints, which is a pretty major upgrade from the pervious version. It is basically what I wanted to create with version 1.0, but was not sure how. EE's Publish Layouts rely heavily on Member Groups, which can be good in some cases, but I found it very limiting with how I wanted to use it. Blueprints removes Member Groups from the equation and lets you create Publish Layouts that are assigned to templates instead. Don't worry, you can still create Publish Layouts based on Member Groups too.
Welcome to Bold Minded. The new home for my Expression Engine add-ons. I decided to put this site together after making the decision to take WYMEditor for ExpressionEngine, and my latest release Blueprints, commercial. WYMEditor started off as a donation only add-on. This was because I wanted to keep costs down and provide a competitive alternative to the other WYSIWYG editors for EE. Then I realized how much time I had actually put into it's development and support, and rethought my plan. I believe going commercial will actually make it more competitive because I will be obligated to provide better and quicker support as well as spend time on new features to make it the best WYSIWYG editor for ExpressionEngine.