Archives for posts with tag: tools

On the last from-scratch CMS I built (for Radford University’s EMS), I utilized jWYSIWYG for the content editor. It was easy to implement, but had a few bugs (including with the content manager). Before that, I used TinyMCE and its MCFileManager to power Dean J. Baer‘s site, which both worked great, but the file manager required licensing fees. Currently I’m looking at these open source options:

The deciding factor here will mostly be how easy it is to add more robust media features.

I like the idea of on-the-page, limited section editing that Mercury provides, though I’m not a fan of the OS X aesthetic. And I also like what looks to be a simple, clean interface and backend for CLEditor. But this is all conjecture right now, so it’s time to dig in.

$ logout

I learned about LESS when I started working for the company I do now. And I can no longer live without it, if anything, for simple nesting of rules. The increased intuitiveness and readability you get from doing stylesheets this way is amazing. The Mixins are freakin’ great, too. Seriously, who wants to look up all the vendor-specific prefixes for all the latest CSS abilities every time?

As you might guess, I’ve switched gears to frontend development.

$ logout

This is my first time using HTML5 Boilerplate. I noticed a lot of people have been talking about it, so I decided to give it a go myself. First impressions (a good judge in the web world):

  • I’ve never liked templates, and this one doesn’t change my mind
  • Like any pre-existing code base, though minimal, you have to learn it before you can begin actually creating things (i.e. creating is no longer fun)
  • At best, I’m getting IE support out of this (and I’m a screw-IE kind of web developer)

I thought since this project is for others and not me, it should be professional and support the myriad microformats and Apple icons and such. But I’m currently doing more work tweaking prefabricated names and changing relative URLs to absolute and thinking about how nothing is how I want it to be.

And I’ve tricked myself into thinking I need a package like this. The work and detail there is great; I already learned things by looking through the code and checking some referenced links. But I can implement these basic HTML5 compatibility features with the minimum necessary developments I’ve kept up with and mostly, as a personal preference, I need full sovereignty over my work. So I’ll be starting from scratch.

$ logout