Updated design: bermuda v1.1, ‘Atlantis’

I just deployed a new design to my blog. The bright turquoise/teal was getting on my nerves. I knew full well when I sent it live in May 2014 that someone was bound to complain about the bright colour. No one complained, and people began to associate the bright colour with my blog, so I started to think of branding and associating certain colours with my blog.

It was hard to let go of the teal, but I am using a more toned down version of the colour now.

Farewell ‘pinky’

Good old pinky. I asked Nick, my brother Brandon and my friend Daniel for their opinion and all three of them said the hot pink was a nice touch, it was ‘actually kinda nice’, ‘gonna miss it’, etc. Pink is my least favourite colour, and although some things are nice in pink, it wouldn’t be my first preference if I had another choice. Of course, in my documentation of bermuda, I based the design off a Hey Geronimo tour poster, so letting go of the pink was hard, but I was just getting sick of it.

I’m not sure why I chose a shade of red/coral, but an old design I did for my blog was titled Strawberry Custard and had a similar shade of red, which I really liked. Despite red being my favourite colour, I didn’t want to use too bright a shade and put back the brightness I was trying to remove!

Before/After

Old design: bermuda
Old design: bermuda
New design: Atlantis
New design: Atlantis

Bring back the rounded corners

bermuda was a silent protest to the work I had to do at my previous workplace. Making the tiniest of tweaks to small components was a pain in the backside, so I made all inputs and buttons have square corners, had no transitions whatsoever, and even avoided using border-box.

So in this design I decided to bring them back. And I added subtle transitions to hover states. I brought it all back subtly. I haven’t checked if performance has decreased simply because of these tiny changes, but I know that there is still a lot that can be cleaned and removed from my CSS.

Stripping out unnecessary CSS

In CSS Adventures: Converting from Stylus to Sass, I mentioned:

My CSS, unminified, is 23KB, and minified, it is 19KB.

(Also, look at that blockquote, doesn’t it look fab?)

Well, now my CSS is 19KB unminified, and 15KB minified. I did a good job cutting out what I didn’t need.

Using rem units instead of em units – sorry IE8!

It was a huge (not really) sacrifice to use rem units (relative em units), but I have stopped supporting IE8. At least I can say that yes, my website works in the browser, but I have not gone to the effort of making a separate stylesheet or including IE8-specific styles to remedy the fact that IE8 does not support rem units. My total traffic from all IE in the past month was something under 2%, so I don’t think too many people are missing out.

That said, using rem units has made small details like margins and padding much easier to deal with. In setting a font size and line height on body, I was able to easily scale that up for larger displays simply by declaring a font size in rem.

I think there are some units that I have set to .9rem, for example, that look a tad too small, so they ought to be something like 1rem, anyway…

More interesting and readable image captions

It looks much better now, rather than a coloured block of blue. The captions actually look like captions to the image.

Before/after image captions
Before/after image captions

Other small improvements

I updated the mobile navigation:

Before/after mobile navigation
Before/after mobile navigation

I also decided that the in-post navigation was too confusing with the little arrows and the next/previous post text should communicate more effectively, not to mention the positioning of the elements. Rather than making the item on the right aligned to the right, I just made both items left-aligned and they will shrink or grow to both occupy as much space as they need as long as they are both on the one line.

Before/after post navigation
Before/after post navigation

Improved sidebar (somewhat)

The sidebar is on my list of things that could still be improved, content-wise. Let’s hope that including a friendly photo of yours truly, along with a brief introduction, will get more people reading my posts.

I’m thinking of adding recent posts to the sidebar as well, as people may not scroll through the posts on the homepage, or even go much further.

Let there be bugs

I only meant for this to be an MVP, but I spent a lot of time on this update so it’s probably steering more towards an actual definable release. There are undoubtedly some bugs that need to be fixed – I know there is a bug with the button on the contact page (which I also still need to bring to prominence somehow, it’s hidden in the pages).

The footer is yuck and needs some real content, and I still plan to improve the experience on smaller screens/phone view, as there is too much content to scroll through in the post excerpts.

EDIT: Known/reported bugs

  • Navigation is on two lines on tablet view. [Nick]
    I would not really call this a bug, it still works, but yes it needs fixing.
  • Checkbox is out of line for logged-out users. [Rachel]
    I just noticed it borks when you click it, too. Such bad UI, oops.
  • Some padding discrepancies for the ‘Continue Reading’ links and the start of the post content.

Hello, Atlantis

Since I feel like this is an obvious change, I have decided to still call this overarching theme bermuda, but this release is called Atlantis, for hilarious enough reasons that the lost city of Atlantis is a story just like the myth of the Bermuda triangle.

There are probably other bugs and issues. If you notice any, please let me know. I know this isn’t a perfect version and everything is always improving and changing and I definitely do welcome suggestions.

Leave a Comment

Comments on this post

I really dig the update, especially the subtle details of the hover states. Also, you reminded me that my image captions suck currently. 😛

Speaking of bugs, in case you didn’t know and because I just noticed it staring me in the face as I type this–the checkbox doesn’t line up with the “Notify me of new posts” text. The box is at the top-left corner of the text.

Thanks Rachel! I just updated the post to list some known bugs, that way I won’t forget about them. I put a min-height on my inputs which is probably why the checkbox input isn’t lining up, haha.

LOVE IT. I’m typing this on my mobile and it looks great 🙂 I’m loving the coral colour. I think the whole thing looks cleaner.

I really love this. I also like that you go through and explain everything, it makes it really interesting to also see a little insight into your creative web process. 😄

Gorgeous! Love the subtle changes. It looks amazing on all my devices, minus my lame screen at work. The resolution on this thing is not that high so light text is harder to see. The coral is a really nice contrast to the teal! I think the thing with a blog is it is hard to get rid of a lot for mobile. Personally I never read blogs on my phone, and if I read an article I hit the little reader button so it looks like a book instead of the website. I think we talked about this recently about captions on photos, I’m really digging the new caption set up!

I love reading articles like this. Seeing your thinking process, and what logistics went into which decisions makes it cool to see how you create the overall audience experience better! 🙂

Thanks! 🙂 I hope the text isn’t too light, I know it isn’t completely black either.

I know what you mean about the reader button – it can make the reading experience a lot cleaner. It can be a challenge to get your website looking user-friendly on mobile because at the same time you still want it to look really pretty!

I think it’s a good idea to write about design decisions. I find it fun to write and fun to share. 🙂

I definitely love this redesign and color scheme! I like how you reworked the theme instead of starting a new one – especially that you decided to brand it with teal and coral. Pink is one of my favorite colors but not really to use on the web (or wear as clothes, but ITEMS is a different story haha).

The current theme on my blog is also a redesign of my previous one. It was nice to improve upon it, because too much pressure is put on making the “perfect” theme on the first go. It defeats the purpose of web design if we are not allowed to improve it!

Also I don’t think there’s anything wrong with not supporting IE8, so that’s great. A lot of people stress you could be losing 5% of your customers / readers … but they should be the ones updating their poor computers haha.

I like pink things, but I have trouble liking pink clothes, haha.

I agree with that. It was a lot easier to tweak and improve my existing design instead of trying to make something completely new. After working in the industry I have realised that sometimes the best designs come about after a lot of testing and trial and error.

I suppose if I owned a huge website with a lot of revenue, it would make more sense to cater for those (poor) IE users! That aside, I wish Windows would force users to update something that old an incompetent, but that’s a different story.