Coincidentally, a little over a week after I describe my favorite editor to put in web apps, they folks over at Basecamp announce their new editor: Trix.
Without actually integrating it yet, I feel like this is a safe bet on the next great editor for the web. Check it out at:
My awesome wife and daughter handle the swordplay by stoping to smell the candles.
The amazing thing is I edited this entirely on my phone. What a world we live in. It used to take me an hour to edit down a 60 second clip of Hi8 film!
Over the past few years we have seen a huge reversal in the amount of complexity we hand over to our users through our interfaces. This is such a good thing. One item that has always remained for me is finding a decent WYSIWYG editor. There are quite a few good ones of late.
Medium’s editor interface is the gold standard these days. Unfortunately, we don’t get to recreate that easily unless we have the huge capital investment they do 🙁
TinyMCE and FCKEditor (CKEditor now?) were the most powerful editors for some time. But they brought complexity.
My new favorite is EpicEditor. It’s syntax is in markdown which is really nice for the sweetspot of a newbie user vs a power user. Check it out:
We’ve been lax in implementing CI in the latest project I’m working on. Now that decision has caught up with me and its time to implement something. I mainly held off on CI because I couldn’t bring myself to have to setup another Jenkins instance. I’m a long time user and fan of Jenkins, I even developed the Perforce plugin for it back when it was called Hudson.
But these days, I no longer want to manage servers, be they physical or virtual. Life is just too short. Instead, I’d like to use one of the new CI services that has cropped up in recent years. For something as important as CI, I’m not going to make a blind choice. Especially, when we’ve been spoiled with how customizable Jenkins is. So let’s get down to reviewing some build tools…
Bootstrap 4 is moving from LESS to Sass!
In the early days of bootstrap, we had to rely on outside developers maintaining a port of bootstrap in Sass so that we could integrate with our existing Sass projects. It got better with Bootstrap 2 and an official Sass repo. But it always felt an after thought and you would get some strange problems every once in awhile as the main developers were lax in focusing on the Sass side of things.