Set Creative - Creative Services and Education

Log In

User *

Pass *

Web Solutions

Everybody needs a webpage these days. Companies lavish attention on them. Enthusiasts spend all their free time maintaining them. Bands and creative projects are often especially in need of them. If you’re involved in artistic work of any kind, the odds are pretty high that you want some public exposure for what you do. But unless you’re a designer - and a HTML/CSS literate one at that - or you maintain a particularly techie group of friends the odds are that you’ll end up with few choices:

  1. No website
  2. A hideous, ugly website that drives people away, or which is never updated or fixed because your “techie” friend has a girlfriend now.
  3. A pretty, regularly updated website that takes away all your time to work on your art. What’s this website actually for again?

The good news is, I’m not too bad at this and I’m very sympathetic to the cause. Having been in bands previously where I’ve maintained the website, it’s been a royal pain in the backside. Speaking personally, if I’m going to commit to playing music, I want to actually dedicate some time to it, and I would assume this to be true of anybody in any artistic field.

For a fee that’s pretty reasonable by industry standards (actually, it’s jaw-droppingly low) I’ll give you an excellent value site that will allow you to get your vital info out to people, quickly. If you want to announce a gig, you’ll no longer have to worry about messing around with HTML pages to get the info online - just fill out a form. Also, you won’t have to worry about removing the gig after the event - the news page can do that for you automatically. Why waste time on geeky web administration when you have something better to be doing?

Finn Higgins
setcreative.com

Standards-based site, get a standards-based browser > Get Firefox Get Opera

Warning: Unknown(): write failed: Disk quota exceeded (122) in Unknown on line 0

Warning: Unknown(): Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0