Posts

Building My Automated Social Media Publisher — Part 3: Building the Machine

Image
In the first two parts of this series, I explained why I wanted to automate the promotion of my blog posts and why we eventually decided to use Buffer as the intermediary between our application and the social networks. That decision solved one major problem, but it left another one: What exactly should our application do? The temptation when starting a software project is to keep adding features. Once you realise that something is possible, it is very easy to decide that the application should do that as well. We deliberately went in the opposite direction. Start With the Actual Job The application had one basic purpose: take articles from my blogs and turn them into scheduled social-media promotions. Everything else was secondary. That gave us a relatively short list of things the appli...

Building My Automated Social Media Publisher — Part 2: Finding the Middleman

Image
In Part 1, I explained how the idea began with a fairly simple problem: I wanted to automate the repetitive job of promoting my blog posts on social media. Our first instinct was to connect the application directly to the social networks. It was a logical idea, but the more we considered it, the less attractive it became. Every social network meant another API, another authentication system, another set of permissions and another integration to maintain. So we changed the question. What if my application only had to talk to one service? Looking for an Intermediary What we were looking for was effectively a middleman. My application would prepare the promotion and tell the intermediary where and when it should be published. The intermediary would then deal with the individual social networks. ...

Building My Automated Social Media Publisher — Part 1: The Problem

Image
Publishing a blog post is only part of the job. Once an article is written and published, there is another task waiting: getting people to actually see it. With several blogs producing articles on different subjects, that means repeatedly creating social-media posts, deciding where they should go, deciding when they should appear, and remembering to do it. At first, this doesn't seem particularly difficult. One article, one social-media post — job done. But multiply that across several blogs and several social networks, and the simple task becomes a recurring administrative chore. The Problem I Wanted to Solve That was the problem I wanted to solve. I didn't want to build a giant social-media management system. I wasn't interested in replacing the commercial platforms that already exist, and I certainly didn't need hundre...

How Far Can You Push Blogger?

Image
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 i...

Why Choose Blogspot as the Platform for Your Website?

Image
Can you build a proper website using Blogger? Yes. But that leads to a more interesting question: why would you choose Blogger as the platform for a website? When most people hear Blogger , or its familiar Blogspot address, they probably think of a blog. They imagine a page containing a stream of articles, perhaps with a sidebar and a collection of Blogger gadgets. But Blogger doesn't actually require your website to look like that. With a sufficiently customised template, you can build your own HTML structure, your own CSS, your own navigation, your own components and your own visual identity. At that point, the question becomes less about whether Blogger can be used for a website and more about whether there is any particular reason not to use it. The biggest attraction is remarkably simple: Blogger gives you free hosting. Free hosting is a pretty big deal If you build a conventional website, one of the first things you normally have to consider is h...

User Functionality Part 4: From Accounts to Capabilities

Image
Once the framework had a common Account page, I had solved one problem. Users now had somewhere to go to manage their account. But that immediately created another question. What exactly should a user be able to manage? At first this sounds like an application-navigation problem. If someone uses the Publications application, give them a link to Publications. If they use the Marketplace, give them a link to Marketplace. But I wanted something more structured than a collection of application links. I wanted the account area to describe the things that a user could actually do. That led to the idea of capabilities. A capability is not simply an application. It describes something that the user can manage or access. For example, one of the framework's planned capabilities is: Manage My Publications Another is: Manage My Marketplace Business Those names are deliberately written from the user's perspective. They aren't saying "Go to the Publicati...

User Functionality Part 3: Building a Common Account Area

Image
Once authentication had become a framework responsibility, the next question was fairly obvious. If the framework knows who I am, where do I go to manage my account? Until this point, the individual applications had been the things users interacted with. The framework existed largely behind the scenes, providing the infrastructure that made those applications work. User accounts changed that relationship. The framework now had something that users needed to interact with directly. That led to the idea of a common Account page. Rather than having each application create its own account page, the framework could provide one place where a user could see their account and the functionality available to them across the website. This might sound like a relatively small interface decision, but it reinforced an important architectural principle. The account belongs to the user, not to the application. If I use the Publications application and then move to the Marketplace, I s...