A CATALOG OF DISCONTENTS
|
|
So why do the Responsive blog themes, introduce by Google in 2017, continue to give me pause nine years later?
Don't get me wrong: the fact that these are responsive means they provide a superior user experience on mobile. That is huge.
Most web traffic today comes from phones, and a responsive theme makes your work easier to read, find, and navigate from there.
Nonetheless, there are tradeoffs.
Let's catalog them.
Tabular navigation
|
These are functionally the same as the tabs—click them and they will take you to a new place—but lack the visual clarity of the links arranged like tabs in a notebook.
The new-style links take up the same space as the old.
Arguably not a huge deal, but it demonstrates a kind of hipster design aesthetic that prizes faddish cool over user experience.
Quick edits
I admit that I have gotten acclimated to this clever toolbar workaround from Sam Nordberg at 10원 Tips. Still, Google could have retained quick edits in the Responsive themes.
Snippits
The responsive themes present this as a snippet, a solid unlovely chunk of text. Photos are cropped square.
I have previously described ways you can manage your snippet's appearance (and control the break) while retaining the economical size.
There are more-elaborate workarounds online that will restore formatting to the snippet, or even replace the snippet with old-style presentation. (I'm doing that on this blog at the moment, is it a good idea?)
Older/newer navigation
|
Where the older themes provided this in an intuitive way, the responsive themes only allow readers to turn the page forward.
If you want to see the previous posts, you have to wrestle with the Archive widget. About that:
Archive widget
|
| Smart archive presentation with older themes |
The image shows part of the Archive widget as it would appear in an old theme when reading a post from March of 2014. Note how
- The year 2014 is open, showing all the months when there were posts
- The month of March is open, showing the titles of all the posts in that month
- The other years are listed but closed.
If you jumped to a post in July 2020, the archive would adjust by showing a similar view for 2020, with July 2020 post titles.
You could interact by clicking the little flippy triangles to locate other posts.
All of that thoughtful design has been replaced by the most recent year (not the year of the active post) open to show the months.
"Show more" unfurls the months for every year, making it more laborious to navigate.
I am not criticizing the design decision to retract the whole display inside a clickable link:
|
Considering how cluttered a sidebar can get, that might be an improvement in any theme (though I wish it were at my option).
But it seems to me that when you do click and view the archive, you should get the same nuanced behavior that the older version provides.
Other widgets
All in all
I nonetheless wish for more thoughtful design, and more options that are built-in natively without resorting to hacks and workarounds.
"Thumbs down" photo courtesy of Vitaly Gariev.





Thanks for the shoutout. I use a responsive theme and I like it but I also added a lot of custom CSS to make it look nicer. I still think Blogger's theme choices are overall much nicer than Wordpress, which seems to have become so bloated and unnecessarily complicated over the years.
ReplyDeleteMany of these problems can be ameliorated through custom css. The "true tab" behaviors I miss, for instance, are implemented with css in the Designer themes and the same approach works in the Responsives.
DeleteI just think the better behaviors should be the default, available to newbies and coders alike.
I find myself using my blog's footer to install more widgets. The sidebar has more than enough things in it. Great post. I am following your blog and I have it's link in my blog's footer. Happy blogging.
ReplyDeleteSidebar clutter is a real issue (that I have written about!). I think that the footer, however, is often overlooked by readers. I consider it to be sub-prime real estate.
DeleteI agree with you about that. Now that you mention it I'm going to move one or two sidebar widgets into the footer. If I like the look I'll keep them there. The labels widget instantly comes to mind.
DeleteThe last couple of sites I've made with Blogger have used the old no-responsible Simple theme - but with the design being mobile first. So no sidebars at all, pretty large fonts on desktop. I put the archive in the footer, and everything else has to be linkable from the Pages gadget.
ReplyDeleteIt won't work for every blog. But I just refuse to use the Responsive themes, because I think most non-Blogger-aware users will have no clue what's going on in them.
You are right, the blogger's pagination is missing on Notable responsive theme, especially to the newer posts, so I modify the CSS and HTML to add the button for previous posts.
ReplyDeleteOne thing I'm still curious about is why the title and description on the home page and the monthly/annual archive pages are the same. Do you know how to fix this?
I'm sure this (title description) could be different, but what is wrong with it? I'd argue having a constant identity across the blog is good.
DeleteThere's nothing wrong with that. Let's just say I'm the kind of person who likes to tinker with things just out of curiosity.
DeletePlease take a look at the source code (Ctrl-U) for these three pages on your own blog:
https://too-clever-by-half.blogspot.com/
https://too-clever-by-half.blogspot.com/2026/
https://too-clever-by-half.blogspot.com/2026/04/
How can I make the titles and descriptions of archive pages (yearly and monthly) automatically unique?
For example, for the 2026 archive page, the page title would be "Archive 2026 - Too Clever by Half", and the page description would be "Archive of posts from 2026"
Thanks for clarifying. I can see how that would be useful. No idea how to do that, but I do not doubt someone could.
DeleteHe's trying to tell you how your blog should look. Imagine that. Maybe he should focus on his own blog. Your blog is fine as is.
Delete@Musicman, I really don't feel that way about it. It's an interesting idea! Also, in other posts I have invited comments about this blog theme.
DeleteMy apologies to all for jumping into a conversation that doesn't concern me. Have a wonderful day.
DeleteYou are welcome here any time, @Musicman.
Delete@Musicman, I'm not asking for the blog title and description to be changed.
ReplyDeleteIn short: each post on Blogger has a unique title and description, distinct from the homepage. So, how the archive pages can be like that automatically - not using the same title & description as the homepage (duplicate).
You can use conditional tags to generate titles based on the page type (e.g., data:view.isArchive). The description is a bit trickier because it’s part of the 'all-head-content', so you’d have to generate it all manually. I’m not sure if it’s worth the effort, since Google often selects its own snippet anyway (one that matches the user’s query), and archive pages aren’t as important as post pages.
Delete@Arkadiusz, I think he wants date-specific headers. A bit more complicated perhaps.
DeleteHello Arkadiusz Narowsky, I still remember you helping me display commenter avatars after a setting in the old-school Blogger dashboard disappeared.
DeleteThanks for your suggestion. At least your answer gives something new to me and readers.
Thanks, Adam, for your response.
Previously, I'd modified and removed a lot of obsolete, redundant, and unused Blogger's CSS and HTML code to speed up loading. This keeps my brain engaged, and... prevents "dementia" LOL
Conditional tags can be used almost anywhere. There are also variables for years, months, and days (to generate dates in various formats). Example: meriwild.com/2022/ (title in the browser tab and the header above the list of posts)
DeleteAvatars for anonymous commenters? I remember ;-)
@Arkadiusz, I’m impressed by the changes to the "title" on the archive and category pages. So you’re the one who designed meriwild.com
DeleteWould you mind explaining how to do it in detail? Just treat me like I’m still in elementary school when it comes to HTML.