My two flagship websites, (web portfolio), and (original music), have been updated to versions…uh…they’re newer. (Nebyoolae + web; genius, I know) is my personal web development/design portfolio. If anyone wants to know how I build websites, then this is a good portal. This new version has quite a few changes.

It now has a web development blog on the front page (culled from this blog), with a little “Latest Project” widget, too. Sections include Projects, where descriptions of sites I’ve done exist, Resume for a more traditional view of my web development history, a short About page, and the ubiquitous Contact form.

The look of it has been completely revamped, going from a fixed width to a dynamic one based on the browser window. When I made the previous version, I wanted something that fit in a single, portrait window, so making it fixed-width made sense. Unfortunately, I usually use my computer at a high resolution, leaving a lot of unused whitespace visible, making the site seem overly empty. Using a liquid design makes sure that no part of the window looks so…barren.

I didn’t have a blog of any sort on the old site, and that was a mistake. Besides showing off what you’ve done, most people want to know you can talk about it, too. Making a separate dev blog just for this site was unnecessary when I was already making dev posts here. I found a PEAR component that would help me parse Lazy in the Blog’s public RSS feed for specific posts and then display them here. Mission accomplished.

The about page removed a lot of pretentious and unneeded cruft about the technologies I use. For the record, the site is built using PHP via the CakePHP 1.2 framework. It’s XHTML 1.0 compliant and uses mainly CSS2 with some CSS3 garnishes for flavor. User interaction here and there is accomplished with jQuery.

My resume got updated and the ways in which you can view it are new. Besides the carried-over text-only view, you can now change it to a PDF-printable version, perfect for printing to PDF if on a Mac, or using a plugin like CutePDF on Windows. Finally, a generic printable version that’s not as bare-bones as the text-only view has been added, for printing to paper. I spent a lot of time getting the neat transition animation to work, but it’s not optimized yet.

The contact form is pretty much the same, but it works with AJAX now, giving better feedback to the user about required fields and whether the message got sent or not.

All in all, I’m happy with the new look and added functionality. Using CSS3 is fun because it allows me to make rounded corners and shadows without having to make images in Photoshop. I’m not a great visual artist, so any programmatic tools to get around having to make little graphics is helpful.


Whereas is more consistent in look and color scheme, has always been more of a playground. I started it as my “personal homepage” sometime back in the 1990s, and its focus has ebbed and flowed with each variation. Initially, it was probably more of a free-for-all, but then narrowed to just music. Later it added pictures and videos as I made them. Then it later got stripped back down to just music in 2003, as well as getting a dynamic overhaul when I changed everything to PHP and created a database for all of the music I’d created up to that point. Now I could more easily look up albums and songs and display them in more useful ways. I even made an administration side that allowed me to add and edit information without having to edit the database directly or raw HTML files. It was the first “modern” version of

Since then, I moved it from vanilla PHP to CakePHP, a framework that speeds up the creation of dynamic websites by doing a lot of the initial scaffolding. Most sites are just interfaces to a database, and frameworks know this and harness the conventions established by millions of web designers to formalize things so it can build a skeleton of your web site before you even begin to type anything. This, I like. Once all that was set up, I really needed to work on the user experience, which was the focus for the latest update.

The homepage is no longer a blog, but the main albums index. Blog entries still exist, but are now relegated to a small box, hidden until clicked on. They are parsed from the same RSS feed as, just with a different category. While I think that blog entries are important, music should be the thrust of why people are here.

Song views never sat right with me, aesthetically. I just couldn’t figure out how I wanted to display all of the related information at the top. My latest design uses a faux-gradient style with a larger font that I really like. Song comments and ratings have been flawed for a while. The design was rough and the AJAX was minimal or wonky. Now, comments are added dynamically and ratings update correctly, all without refreshing the whole site. The song search function has been fixed and improved, as well. Start typing and it dynamically loads the songs that match below. A small delay is created before doing a lookup so that each 350ms period of combined keypresses, and not each individual one, is sent, limiting the DB queries.

The tag cloud was always a point of contention. Horizontal lists made things difficult to read, as it would look like one long, run-on sentence. My friend suggested I use columns of a few items each, with the remainder moving rightward to a new column until it wrapped onto the next line, which is what ended up making the cut. I still haven’t implemented a weighted tag display (showing, usually by size, a tag’s relative importance), which would be ideal, but that will come in a later variation.

The studio information page hasn’t changed, but the about page’s overall length got truncated, to minimize scrolling. I buffed up the description a bit, but made the gallery slideshow smaller. Images now change with a minor fade.


One thing that was not included in these revisions was any kind of significant update to the administrative side. The public-facing part was most important, since that’s what everyone sees, so I made it the focus. will be changed from CakePHP to Ruby on Rails and the resume transition will be optimized. will most likely have its fixed-width design changed to a liquid one, and the Flash player for songs may change to HTML5 once that becomes more standardized. The color palette will also be reduced and made more consistent.