How Far Can You Push Blogger?
Part One asked why you might choose Blogspot as the platform for your website.
The answer was surprisingly simple: free managed hosting, a built-in publishing system, Google's infrastructure and the ability to create your own design.
But that leaves a much more interesting question.
How far can you actually push it?
If Blogger is going to be the foundation of a website rather than simply a place to publish a conventional blog, then the real test is what you can build on top of it.
Can you create a website that looks and behaves like a conventional, professionally designed site?
Can you create your own components?
Can you build a design system?
Can you integrate other services?
And eventually, where does Blogger stop being enough?
You control much more of the front end than you might expect
The first thing to understand is the distinction between the front end and the back end.
The front end is what the visitor sees and interacts with.
The back end is the machinery underneath the website: databases, server-side programming, authentication, application logic and so on.
Blogger gives you considerably more freedom over the first than the second.
You can have substantial control over what the visitor sees, even though you don't control the infrastructure underneath it.
That distinction turns out to be extremely useful.
Write your own theme
The biggest step is to stop thinking of the Blogger theme as something you select and start thinking of it as something you can design and engineer.
A custom Blogger theme can define the structure and presentation of the website.
HTML structure
You can define how the various parts of the page are arranged and how your content is presented.
CSS design
You can create your own typography, spacing, colours, borders, cards, buttons and visual components.
Navigation
You can create navigation appropriate to your website rather than simply accepting the structure of a standard blog theme.
Responsive layout
You can design layouts that adapt to different screen sizes rather than treating mobile presentation as an afterthought.
Once you start doing this, something rather interesting happens.
The Blogger theme becomes less like a skin and more like the front-end architecture of your website.
You can build components rather than pages
One of the biggest differences between casually modifying a Blogger theme and actually designing a website is the idea of reusable components.
Instead of creating every part of every page independently, you can establish common visual patterns.
- Article cards
- Information cards
- Callout panels
- Navigation components
- Newsletter cards
- Sidebar sections
- Buttons and links
- Content grids
- Feature panels
- Reusable typography rules
Once those components have been designed properly, they can be used throughout the website.
That is exactly the same sort of thinking that goes into a modern website design system.
This is where Blogger starts to look less like a blog
Imagine a visitor arriving at a site with:
A custom header
Designed specifically for the publication rather than inherited from a standard Blogger theme.
Custom navigation
Organised around the actual subjects and sections of the website.
Custom content cards
Articles and resources presented in a consistent visual system.
Custom sidebar components
Newsletter signup, related sites, navigation and other useful resources.
There is nothing about that experience that requires the visitor to think:
"This is a Blogger blog."
They simply see a website.
You don't necessarily need a plugin for everything
This is perhaps one of the biggest philosophical differences between this approach and a typical WordPress installation.
When something needs to be done in WordPress, one obvious question is:
Which plugin should I install?
With a custom Blogger theme, a different question often makes more sense:
Can I build this myself with HTML and CSS?
For presentation, the answer is surprisingly often yes.
If you need a card, build a card.
If you need a navigation panel, build a navigation panel.
If you need a callout, build a callout.
If you need a newsletter link, link to your newsletter service.
There is no reason for every piece of functionality on a website to become a software package installed on the website itself.
But external services can extend Blogger
This is where the limitations of Blogger become less restrictive.
You don't necessarily have to make Blogger do everything.
You can let other services do the things they specialise in.
Blogger
Publishing, pages, content, theme, layout and the primary presentation of the website.
External services
Specialist functions such as newsletters, payments, forms, analytics or other services where Blogger itself isn't the appropriate tool.
For example, the newsletter component on a website can simply point to a newsletter provider.
The visitor still experiences it as part of the website.
Behind the scenes, however, the specialist service is handling the specialist job.
Don't make your publishing platform do something simply because you can. Let specialist services handle specialist functions.
Where Blogger starts to hit the wall
So far, this all sounds remarkably powerful.
But there is a boundary.
The more your website becomes an application rather than a publication, the more important Blogger's limitations become.
Server-side programming
You don't have the freedom to install and run arbitrary server-side applications on the Blogger server.
Your own database
You don't get unrestricted access to a database that you can design and manage for your own application.
User accounts
A sophisticated custom user-account system is outside the normal Blogger model.
Complex application logic
If the website needs extensive bespoke business logic, Blogger's publishing architecture becomes a constraint.
This is the point at which the distinction between a website and a web application becomes important.
Publication or application?
Consider two very different websites.
A publication
A site containing:
- Articles
- Pages
- Reviews
- News
- Images
- Archives
- Categories
- Commentary
Blogger is naturally suited to this sort of project.
An application
A site requiring:
- Complex user accounts
- Transactions
- Private databases
- Custom workflows
- Extensive server-side processing
- Complex business rules
- Highly customised application logic
This is where Blogger becomes much less suitable.
The dividing line isn't really whether the website looks complicated.
You can make a Blogger website visually extremely sophisticated.
The dividing line is what the website needs to do behind the scenes.
Presentation versus infrastructure
This is probably the most important lesson when considering Blogger as a website platform.
↓
Custom HTML + CSS + Blogger template
↓
Blogger publishing infrastructure
↓
Google infrastructure
You have considerable control over the upper part of that stack.
You have much less control over the lower part.
And that is the trade-off that makes Blogger interesting.
You are giving up some technical freedom in exchange for not having to build and maintain the infrastructure yourself.
So how far can you push it?
For a publication-oriented website, surprisingly far.
- You can have your own domain.
- You can create your own visual identity.
- You can write your own theme.
- You can create reusable design components.
- You can create sophisticated layouts.
- You can make the site responsive.
- You can build custom navigation.
- You can integrate external services.
- You can connect the site to Google's wider ecosystem.
- You can make the finished site look very little like a conventional Blogger blog.
What you cannot do is turn Blogger into an unrestricted web application server.
And perhaps you don't need to.
The real question is what you are building
If you are building a publication, Blogger's limitations may be relatively unimportant.
If you are building an application, they may become decisive.
The question isn't "Can Blogger build a website?"
The question is "What does your website need to do?"
If the answer is primarily publish, Blogger starts to look very attractive.
If the answer is primarily process, transact, calculate, authenticate or manage complex data, then you probably need a different platform.
The interesting compromise
Blogger doesn't give you everything.
But you don't need everything to build a very good website.
You can take the parts that Blogger does well, build your own presentation layer on top, and bring in other services where specialist functionality is required.
Cheap
The underlying Blogger hosting is free.
Simple
You aren't maintaining an entire web server and application stack.
Custom
Your theme can be designed around your own website rather than a generic template.
Expandable
External services can provide functionality that Blogger itself doesn't need to provide.
So how far can you push Blogger?
Far enough to build a website that, to the visitor, may have very little resemblance to a traditional Blogger blog.
The real limitation isn't necessarily what you can make the website look like.
It is what you can make it do behind the scenes.
And perhaps that is a perfectly reasonable trade.
If all you need is a place to publish, why pay for and maintain an entire application stack simply to get there?
Use Blogger for publishing. Use your own design for the website. Use specialist external services where you actually need them.
That may not be the right architecture for every website.
But for a publication, it is an option that is surprisingly difficult to dismiss.

Comments
Post a Comment