Texelate - the Leeds Web Design StudioHomeAbout MeServicesTestimonialsPortfolioBlogQuoteContact
My BlogGet a free quote now

Web Development

Archive for the ‘Web Development’ Category

My gallery of bespoke content management systems

Tuesday, July 6th, 2010

Because I always advertise myself as a web designer rather than a designer and a developer I often meet fellow web designers who express surprise that I’m also a programmer. Without boring you with the details I actually started learning programming a couple of years before I first started with design.

I’ve developed all sorts over the years. During my student placement I built a college website and intranet and authored some multimedia learning tools with Flash. At Uni I programmed two games—albeit pretty basic ones—as part of my dissertation and then went on to design and build a corporate website for a software company.

So although I can’t show any of the above projects for copyright reasons (and trust me you don’t want to play the games) I thought I’d post some screenshots of some content management systems (CMS) I’ve built since setting up as a freelancer (as a freelancer most programming generally revolves around CMSs).

So here are a few projects that prove I’m not just a designer.

Login

This is a simple bespoke login system with ‘Remember me’ functionality. It’s nothing ground–breaking but login systems are an integral part of any CMS.

Online Editing

This is a sample online editor; this brings a taste of desktop publishing to the browser allowing the user to format text (bold, italic, underline, lists, links, etc) online without having to install a plugin.

eCommerce

This show a sample product management page for a CMS used to manage the stock on an eCommerce website. Notice how the system automatically generates a search engine–friendly URL.

Image Editing

This CMS features effortless image editing at the server end. The user can get the system to automatically crop and resize images thus saving them the inconvenience of having to edit the images themselves.

Diary

This is a bespoke booking system for a photography studio. The system allows them to take bookings for both of their studios as far into the future as the want. The calendar–based interface and colour–coding system makes it very easy to use.

So I hope this little gallery gives you an idea of the kinds of things I can program.

If you want me to program anything for you call me on 07843 483 078 or get a free quote online.

Should I backup my own website?

Tuesday, May 4th, 2010

Sometimes it pays to be pessimistic as it means you’re better prepared when things go wrong. One of the primary ways you can prepare for a website disaster is to back it up regularly. You may have wondered who should back your website up and how often. In this blog I aim to briefly answer the question: should I backup my own website?

Why back a website up?

As mentioned in the outset a website should be backed up for when something goes wrong. What can go wrong? One of the most common ways is because of server hardware failure, usually the hard disk. The malfunction causes the server to go down until it is repaired via human intervention; how long this takes depends on the severity of the failure.

One of the other reasons is a software problem. Specifically this means a problem with one of the programs that run on the server—or the website itself. These are usually the result of a virus, a computer hacker or an inherent bug in the operating system or software on your own website. It is common for a single server to run lots of websites together; sometimes a problem with one of these adversely affects all other websites.

Thirdly, there may be an environmental issue where the server is being held such as a fire or flood. These are by far the most destructive and the time–consuming to fix but they hardly ever happen…ever.

It may sound like you should be really worried about your site’s safety as there’s plenty that can go wrong. Thankfully, all the above problems are quite rare. Normally hardware issues can be repaired quickly and easily by a technician. Software issues are even less likely to happen—especially if you use a good hosting company as they’ll have strong security and will keep their anti–virus software up–to–date.

So, let’s say something has gone wrong. What happens next?

How do backups work?

Once the underlying problem is fixed the technician will decide whether or not your site needs to be restored from a backup. Problems such as hard disk failure and sites getting hacked can result in data loss and therefore the site needs to be restored. Every time your site is backed up a copy of all its code and files is created and stored on a separate device (CD, DVD, memory stick, tape or another server or computer) and hopefully a good distance away from the server. The site would ordinarily be backed up from the most recent backup. The important point here is the more recent the backup, the less data you lose. If your hosting company backs up every hour, you’ll never lose more than sixty minutes of data. If it’s every month, you could lose up to thirty days of data.

How often will my hosting company be backing up my site?

It depends on their backup policy. As a rule–of–thumb you’d never want to use a company that backed up less frequently than every day. If you have a site where the content changes regularly (i.e. daily) you’d probably want them to backup even more often than that (see How often?). To find out, contact your hosting company or web designer.

Whose responsibility is it?

So it’s evident that how often backups are taken is the critical factor when determining the amount of data you lose when a crisis occurs. So if you’re running an eCommerce shop and you lose thirty days of orders, whose fault is it? You might instantly want to blame the hosting company but they will probably have a ‘Loss of liability’ clause in their terms that states while they do their best they cannot guarantee no data loss. Unless you have a contract with your web designer it’s not their responsibility either. While it may seem like their territory, blaming a web designer for a hosting problem is like blaming your mechanic because you got stuck in a traffic jam. It sounds like everyone is passing the buck but in reality you’d almost never get to this stage as a good hosting company is well prepared for disaster striking. However, because we know the value of pessimism—and the dangers of putting all our eggs in one basket—it’s a good idea to periodically back the website up yourself. Or, get your web designer to do it.

How do I backup a website?

In most cases if you’re technically–minded, backing a website up is quite easy. All you need are the access codes to the website and a FTP client to download the files. Anyone vaguely computer–savvy can be shown how to backup a website. You’ll also have that feeling of control knowing that should the hosting company get destroyed by a meteor and your web designer get abducted by aliens (okay, maybe that’s being too pessimistic) you’ll still have a backup of your site.

If that sounds like too much jargon to you, you can get your web designer to do it. Of course, this may cost you. Backing up a site is usually quite a quick job so the cost shouldn’t be too much.

How often?

How often should you back the site up? It depends on how often the content changes. If you have a ‘static’ site (one that’s just text and images) then once a week or month is usually enough. If you have content that changes quite often such as a blog or online shop you’d want the backup to reflect how often you make new posts or add new stock. It could be weekly, hourly or every ten minutes.

By default my contracts typically leave the hosting company to backup the site. As a gesture of goodwill though I generally backup sites once per month gratis. Prices for more regular backups are available on request (I usually warn clients if I think they’ll need this).

I’ll end on a positive note though and say that I look after about sixty websites at the moment and have never had any major downtime on any of them. I’m pleased to say what little downtime has been suffered has been for a simple server problem that the hosting company fixed without me ever needing to use one of my own backups. Over the years I’ve whittled down the amount of hosting companies I use to a select few and they’re all first class.

I hope that gives you some insight on the subject of backing websites up. For more information call me on 07843 483 078 or get a free quote online.

Why can’t I see my recently launched site in Google?

Thursday, April 1st, 2010

I find one of the first things a client will do when their new site goes live is search for it on Google*. People are surprised, however, to find that immediately after their site’s launch the brand new web pages are nowhere to be seen. Why is this?

*Note: throughout this article I am referring to Google rather than search engines in general. This is because Google accounts for the vast majority of search engine traffic and it is far more advanced and sophisticated than any other search engine. My ethos with search engines is optimise for Google and the other, lesser search engines will follow suit.

To understand why this is the case it is first necessary to discuss how search engines work. Search engines are huge indices of web pages. They don’t just store information, however, they also hold information about how different web pages link to one another. When one page links to another, a search engine counts it as a ‘vote’ for that page. All votes are not equal either; a search engine will look at the context of the page (the relevancy of the subject matter) and the quality of the web page (how many pages have already ‘voted’ for that).

When you enter a search term in Google a marvel of modern science actually takes place in the blink of an eye. The search term is sent to Google which then queries an index of billions of web pages. Using a very complex version of the ‘voting’ procedure described above, Google will return a handful of pages it thinks are most relevant to your search. So why am I telling you this?

Well, because of the volume of information searched and the way in which it’s linked together it is not possible to search in realtime. So search engines have special automated programs called ‘spiders’ that ‘crawl’ the web, indexing web pages. The spiders create a copy—or snapshot—of the page periodically. So when you conduct a search on Google, Google is actually searching the snapshot (which is held on its own servers) rather than what’s on your site.

As an aside, Google has actually started returning some results in realtime but generally speaking you can forget about that as it mainly applies to live feeds on high profile news and social networking sites.

This brings us round to the point in question: why can’t I see my recently launched site in Google? Hopefully, you can answer the question yourself now. Google can’t see it because it hasn’t indexed it yet.

How do you get your site to appear? If it’s a brand new site (on a new domain) you can let Google know your site is live but submitting the URL to them. If you’ve used me to build your site I’ll have already done this on your behalf. If you’ve redesigned your site and are relaunching it on a domain already indexed by Google you can just sit back and wait for Google to reindex it.

How long does all this take? I’ll answer that with a question: how long is a piece of string? As a spam prevention mechanism, Google is never too quick to start listing new domains so the important thing is to be patient. It can take weeks or even months. You can speed the process up by getting quality, relevant links to your site. How do you do that? Well, that’s a big topic in its own right and perhaps I’ll tackle that another time…

I hope that sheds some light on the matter. If you need help getting your website on Google call me on 07843 483 078 or get a free quote online.

 
Click here to start your web project
Texelate - the Leeds Web Design / Web Design Leeds Studio Site Map © 2010 Texelate