I was never really happy about how the site looked. Sure, I did choose a couple of custom fonts and settled for a few colors that you can still see on Pony Foo prominently today: pink for most links, the green in the pony’s eye, JavaScript’s yellow, etc. The “paper-bag look” never really stuck with me, even though I was mostly aiming to make the content itself highly readable.
When I decided to redesign the site (around a week ago), the first thing I tackled was “making the logo look cooler”. I had no idea what that meant at the time, but – soon afterwards – it set the stage for the entire redesign. Before getting on with the logo I just knew I wanted a redesign, but I soon realized what I needed to do once I got to play with the logo. See, the idea I came up with was that the logo should “flash in pink” on mouse over. That sounded cool, so I did that, and I thought it looked pretty nice, so I translated the concepts into the entire redesign.
I’ve prepared a different post that focuses entirely on the logo and some problems I had with it for tomorrow, so let’s move onto other parts of the design.
When I say “concepts” I really mean “colorful as hell”. I thought, this looks nice and cheerful, I wonder if I could make the entire site look as much of a happy place as the logo does. And that’s what I tried. I started with the most important part of the site – an article.
Articles
I moved details people rarely care about (like comment count, reading length, or tags) onto the sidebar, and emphasized the article’s title, its first paragraph, and code blocks.
Code Blocks
When it comes to code blocks, I adopted a more colorful and modern color scheme: Tomorrow. I also made tag highlights less invasive, as they were too distracting before the redesign, and many commented on how obnoxious that was.
Headings
A while before the redesign I had added anchors to every heading, so that you could go to an URL like /articles/es6-modules-in-depth#conclusions
, but you really had to have intimate knowledge about the blog to even know you could link to headings like that. Now you can just hover over an anchor and click on it, ta-da!
Comment Threads
Then there were comment threads, those were pretty confusing as there were almost no visual cues differentiating replies in a comment thread versus an entirely different comment thread.
The current design makes an effort to illustrate the hierarchy behind comment threads by adding an imperceptible visual cue to the left of each comment.
The comment editor also got a face lift. It’s now using woofmark
and I think it looks much cleaner now. Let me know your thoughts, though!
Licensing
Lastly, there’s the licensing. I’ve been asked multiple times about whether my content was up for distribution or whatnot, and even though I almost always said yes, I’m sure some people thought they couldn’t use the content and didn’t bother to ask. That’s why today I’m adding an explicit note stating that the content distributed on ponyfoo.com is CC-licensed – at the bottom of every page in the blog.
When I was done with the single article experience, I moved on to the rest of the site.
Buttons and Links
This one bothered me for a very long time. Links looked very fat. Buttons were completely inconsistent, no two buttons looked the same, for some fringe reason. I took care of that, links aren’t fat, and buttons have a cool background powered by the same CSS that animates the logo. How sweet is that!?
I guess while I’m on the topic I can comment on how I added confirm
steps that prevent me from deleting drafts I’ve been working on for days. Yes, that happened, and it wasn’t any fun at the time. I would add an Undo feature if it was user-facing, but since only I see it, the old confirm
dialog is good enough!
Home Page
The home page is probably the second most important page of the site. Even though each article is the most important page of the site, the home page is obviously – far and away – the most visited page in the site. Throughout the history of Pony Foo, the home page was basically a collection of individual articles one after the other. This didn’t really work out great, as people couldn’t effectively find anything other than the first few articles. There was so much information about each article that you quickly lost focus as to what you were looking at.
Don’t even get me started with the first iteration of the home page. Remember these little circles looping around? Ugh! Such shame.
If anything, the new home page looks sort of like a news paper. Except for the bazillion ads. I didn’t add those yet. I think this is a great way to sift through articles that may or may not interest you. There’s 40 different articles on display in the home page, and you can page through to see older ones.
This format made a lot of sense in search results, which used the same stupid “render most of the article” “strategy” as the home page, and failed miserably to help you find what you were looking for.
Publication History
The publication history (ex. “archives”) is probably the page that changed the least. For what it’s worth it now contains a brief history of the site, and a count of the amount of articles published on the site. Can you guess the number?
All the while I was working on the redesign I also had my eye on performance.
Performance
One of the glaring issues in performance at Pony Foo was that I was serving up huge chunks of data even on pages that didn’t need any of it. For instance, the home page served the introduction to six different articles, but the entire body of those articles was served as JSON for later use – even though it wasn’t being actually used. The same issue could be observed in search result pages and the publication history. The publication history made this particularly nasty, as that page contains every single article ever published on Pony Foo. That means that the page was receiving JSON models to render pretty much the entire site!
The other performance issue blocking this redesign was the fact that I was pulling critical CSS content for just the home page. That means that if the home page has different styles than some other content, that other content would be improperly styled while the non-critical CSS was being loaded. I fixed this by pulling critical CSS from many different pages and serving the inlined CSS according to the page being requested. This involved a bit of rework, and I’m planning an article on the subject as I think it’s something most of us should be doing in our sites and apps – it’s not just for blogs.
Easter Egg
Also, what do you think of the, uh, easter egg? I would show you, but then it wouldn’t be an easter egg anymore.
Hope you like the new design and that it makes for a more pleasant reading experience here on Pony Foo!
Any and all feedback is appreciated. If you want to open a discussion on some front, don’t hesitate to email me at hello@ponyfoo.com, and thanks!
Comments