There’s a new reissue of the twenty year old documentary on Justin Hall’s links.net and the early days of the web.
Wednesday, April 24th, 2019
Thursday, December 21st, 2017
This homepage is media-querytastic. It’s so refreshing to see this kind of fun experimentation on a personal site—have fun resizing your browser window!
Sunday, November 19th, 2017
Two decades redesigning/realigning the BBC News home page.
Monday, May 2nd, 2016
I’ve been on the web for most of my life, but, without a site to call home, I haven’t been of the web for far too long.
Friday, April 22nd, 2016
I was in Nuremberg last weekend for Indie Web Camp. It was great.
At some point I really should stop being surprised by just how much gets done in one weekend, but once again, I was blown away by the results.
On the first day we had very productive BarCamp-like discussion sessions, and on the second day it was heads-down hacking. But it was hacking with help. Being in the same room as other people who each have their own areas of expertise is so useful. It really turbo-charges the amount that you can get accomplished.
For example, I was helping Tom turn his website into a progressive web app with the addition of a service worker and a manifest file. Meanwhile Tom was helping somebody else get a Wordpress site up and running.
Actually, that was what really blew me away: two people began the second day of Indie Web Camp Nuremberg without websites and by the end of the day, they both had their own sites up and running. For me, that’s the real spirit of the indie web—I know we tend to go on about the technologies like h-card, h-entry, webmentions, micropub, and IndieAuth, but really it’s not about the technologies; it’s about having your own place on the web so that you have control over what you put out in the world.
For my part, I was mostly making some cosmetic changes to my site. There was a really good discussion on the first page about home pages. What’s the purpose of a home page? For some, it’s about conveying information about the person. For others, it’s a stream of activity.
My site used to have a splash-like homepage; just a brief bio and a link to the latest blog post. Then I changed it into a stream a few years ago. But that means that the home page of my site doesn’t feel that different from sections of the site like the journal or the link list.
During the discussion at Indie Web Camp, we started looking at how silos design their profile pages to see what we could learn from them. Looking at my Twitter profile, my Instagram profile, my Untappd profile, or just about any other profile, it’s a mixture of bio and stream, with the addition of stats showing activity on the site—signs of life.
I decided I’d add signs of life to my home page. Once again, I reached for my favourite little data visualisation helper: sparklines
A sparkline is a small intense, simple, word-sized graphic with typographic resolution.
I’ve been tweaking them ever since I got back from Germany. Now I’ve added in a little h-card bio as well.
Initially I was using the fantastic little scripted SVG that Stuart made , the same one that I’m using on Huffduffer and The Session. But Kevin pointed out that a straightforward polyline would be more succinct. And in the case of my own site, there’s only four sparklines so it wouldn’t be a huge overhead to hard-code the values straight into the SVGs.
Yesterday was the first day of Render Conference in Oxford (I’ll be speaking later today). Sara gave a blisteringly great talk on (what else?) SVGs and I got so inspired I started refactoring my code right there and then. I’m pretty happy with how the sparklines are working now, although I’m sure I’ll continue to play around with them some more.
There’s another activity visualisation that I’m eager to play around with. I really like the calendar heatmap on my Github profile. I could imagine using something like that for an archive view on my own site.
Luckily for me, I’ll have a chance to play around with my website a bit more very soon. There’s going to be another Indie Web Camp in Germany very soon.
Indie Web Camp Düsseldorf will take place on May 7th and 8th, right before Beyond Tellerrand. Last year’s event was really inspiring. If there’s any chance you can make it, you should come along. You won’t regret it.
Sunday, August 19th, 2012
URIslands in the stream
For over a decade the home page of this website has effectively been a splash screen.
A splash screen! The only person with a splash screen these days is— Drew McLellan (@drewm) July 27, 2010
Well …not exactly. I mean, it’s not as if it contained an animation and a “skip intro” link. But it has been very minimalist: a brief one-sentence explanation of what this website is and a brief one-sentence description of the latest post I’ve published.
Most blogs are standalone sites—i.e. the blog isn’t part of a larger site—so the home page and the latest blog posts are one and the same. My site is a bit different. The blog part—my journal—is just one piece. There’s also the links section and the articles section. That raises an interesting question: exactly what should the homepage contain?
I’m a great believer in well-designed URLs but oftentimes the home page is something of an exception (one of the reasons I advocate designing the home page last). The URL
/ doesn’t tell you anything about the resource. There’s basically two different ways to go: keep it really, really minimal (like I’ve been doing for ten years) or make it a patchwork containing a little bit of everything (the way that most news websites work).
For the past few months I’ve been contemplating making the switch from the minimalist to the maximalist approach for the home page of this site. On the one hand, I think it’s RESTfully correct to have the URL
adactio.com/ return a terse description of what the site is, with links to further resources. On the other hand …it’s a splash screen.
After much deliberation, I’ve decided to flip the switch.
It’s a bit of a shame. I quite enjoyed being one of the last people I know to have a quirky intro page. But the new home page alleviates a concern I’ve had for a while. I get the feeling that a lot of people have only been paying attention to what’s written in my journal without realising that I post multiple times a day to the links section. The new homepage shows everything—journal entries, links, and articles—grouped by date. It is, if you like, a stream.
Most users on the web spend most of their time in apps. The most popular of those apps, like Facebook, Twitter, Gmail, Tumblr and others, are primarily focused on a single, simple stream that offers a river of news which users can easily scroll through, skim over, and click on to read in more depth.
Glossing over the lack of definition for “app”, there’s a good point here. The “stream” idea makes a lot of sense …in the right situation. That situation is the list view. If you think about the situations where the never-ending stream has been employed—Twitter, Facebook, Instagram, Pinterest—they are views of lists, usually reverse-chronologically ordered lists.
Going back to URL design, these kinds of list views are the ones that often have a single URL filtered with a query string. You’re much more likely to see
/popular?start=10 than you are to see
/popular/10-20. There’s a good reason for that. While the kind of resource located at the URL remains unchanged—a list of items—the specifics are likely to change every day or hour or even minute—which items are in the list.
So traditionally list views have been paginated using query strings. The streams that Anil is talking about are an alternate way of navigating list views that does away with pagination and query strings. I think that this way of navigating a list view can work well but, as always, the devil is in the details.
First of all, there’s the issue of when to append to the stream. This could be triggered by the user with a link—“load more”—or you could assume that when the user gets to the current end of the list that they’ll automatically want to load more …the dreaded infinite scroll.
As Frank put it:
Infinite scroll is so frustrating for me. It turns every website into a battle I can’t win. There’s no finishing, only forfeit.— Frank Chimero (@frankchimero) July 11, 2012
Quite apart from any psychological implications, there’s a usability issue here. Interpreting one action by a user—scrolling down the screen—as implicit permission to carry out another action—load more items—is a dangerous assumption. It’s similar to the tyranny of mouseover:
If I click on a link, I am initiating an action. If I fill in a form and press a submit button, I am initiating an action. But if I move my mouse over a page element, I am not initiating an action.
Oh, and if your site has footer, please do not use infinite scroll. Think about it.
In case you hadn’t guessed, I’m a big proponent of allowing the user to explicitly request more items to be appended to a stream rather than using the infinite-scroll pattern.
That said, you could introduce a nice compromise. What if, when the user scrolls down the screen, you begin pre-fetching the next items in the list? That way, when the user explicitly requests more items they’ll load lickety-split.
Anyway, you’ll notice that the new home page of adactio.com is still using pagination. That’s related to another issue and I suspect that this is the same reason that we haven’t seen search engines like Google introduce stream-like behaviour instead of pagination for search results: what happens when you’ve left a stream but you use the browser’s back button to return to it?
In all likelihood you won’t be returned to the same spot in the stream that were in before. Instead you’re more likely to be dumped back at the default list view (the first ten or twenty items).
If your stream is self-contained—like Instagram or Pinterest—then there’s no problem. Twitter attempts to get around the problem by showing you the linked content inline where possible (with some judicious use of oEmbed) and by opening external links in a new window or tab—not so much the cure that kills the patient as the cure that ignores the problem.
In my case, my home page stream is crammed full of hyperlinks. Until there’s a way to make unpaginated streams work nicely with the back button, I’ll stick with pagination.
Anyway, I hope you like the new home page. If you do, you may want to subscribe to the RSS equivalent of the combined stream of my journal, my links, and my articles.
Friday, December 14th, 2007
Flickr have launched a new stats feature for pro members. It’s very nicely done with lovely graphs and lists. It kept me occupied for at least five minutes. Personally, I’m just not all that into tracking referrers but it’s really nice that this data is available.
One of my more popular pictures lately is a surreptitious snapshot of the new BBC homepage that I snapped at BarCamp London 3. The photo generated quite a bit of interest and speculation. Fortunately there’s no longer any need for pundits to form their opinions based on a blurry photo of mine—the BBC blog has revealed that the new homepage is available to preview as a beta.
The greek letter isn’t the only Web 2.0 cliché that has been embraced:
- Rounded corners: check,
- Sloppy gradients: check,
- Garish colours: check,
- Drag’n’drop: check.
Overall it’s fine but some of the visual design elements irritate me. The gradients, as I said, are sloppy. As is so often the case with gradients, if they aren’t done subtly, they just look dirty. Then there’s the giant Verdana headings. Actually, I kind of admire the stubbornness of the BBC in using a font that really only works well at small sizes.
But the biggest issue—and this was the one that generated the most debate at BarCamp—is the way that clicking a link under the big image changes the colour of the entire page. I like the idea of pushing the envelope with CSS like that but the effect is just too extreme. It implies a relationship between the action of clicking that link and changes to other areas of the page. No such relationship exists. Confusion ensues.
I love the clock in the corner though.