Earlier today I decided to have a little think about what makes a business website great and what, well, really doesn’t! The very first thing I thought was it’s, making a wonderful looking website, so wonderful infact that all your clients will immediately be like woah these guys really have talent, I want my site designed by them. Essentially this is a good way of thinking or at least the correct mindset. I’m sure that, I’m not alone in thinking this! However, there’s a little more to a wonderful website than it’s cover. As the sayings go “beauty is only skin deep” & “you cant judge a book by its cover”.
So what really does make a wonderful, purpose serving business website? Good question.
Here are some Do’s and Do Not’s from my own personal experience and view.
- Do make your new site look really eye catching, but more importantly remember the user experience. Don’t make it so eye catching and out there that the average client or onlooker is immediately put off, and won’t bother to find the information they want. Make sure navigation remains simple, nice menus rather than hidden buttons and links. Remember if you look at alot of the most successful websites used by the biggest base of users out there, most of them won’t have any massively out there or exciting UI. They will all have basic, easy to remember, easy to use UI and thats important to remember! Users are thickle and generally make there mind up about a site in the first minute of being on it.
- Do make sure you don’t hide important information behind too many pages of link depth, users will not want to siv through to much stuff to get to what they want.
- Do make your unique selling points readily available.
Over the last year I’ve been constantly if not more than constantly trying to ask myself, are we doing things the right way?
There are a million and one different ways to accomplish some of the tasks we undertake on a day to day basis.
Preferences are always going to change and perhaps there is not one best method of practise at all.
Im trying to open myself up here to ask anyone in the context of my company and I, what the next step could be.
We build lots of text based games, driven by simple php and mysql, php = mixture of functions and classes. I generally don’t like the idea of php frameworks for use with game design of this type, as games quickly grow code base hugely and you get the annoyingness of extra overheads in load time. However im very much open to new ideas as to how we could improve code. Maybe a new language, or maybe a different approach.
I wondered really if anyone out there has built a complex game on anything other than there own custom php code and mysql (obviously in the context of text based, browser based games and improving on php).
Also we do alot of client work, nice designs, baskets and checkouts all the usual stuff. Does anyone use a particular framework for similar things and found its really good? We spend far too much time repetitively coding things like checkouts and baskets for each customer.
Ideally its all about taking things up a notch and what could improve what we do.
I’d also like to know if anyone uses any particularly good checkout bundles or companies, to manage all there payments really easily. Ours is very disjointed atm. With payments for different sources ie mobile, card etc all being taken by different companies.
Quick and dirty tutorial to connecting to a remote server with ssh keys and putty.
Firstly you need to download putty and puttygen which can be found:-
Here – Putty Client
Here – PuTTYgen
Yes they are both the same page, you will find the download links for both here.
Once you have downloaded both the clients you will need to first generate yourself a key using the puttygen and then save it out to a file in a location you will easily be able to remember. Remember you need to generate a public and private key, but the private is the one of most use to you.
Im going to largely breeze over adding your ssh key to the server, as you should really know how to do this already before attempting to use putty with ssh keys and port forwarding.
Open up putty, enter the host as whatever it needs to be either an ip address or a host name like google.access.me.com and specify the port as 22 if it isn’t already.
Then head down on the left hand menu to the SSH list which will probably be shut, click the plus to expand the list and head to the AUTH tab. Here enter the user you want to auto login with and specify the path to your key using the browse file function.
If all is correct head back to the “session” tab and move to the right hand side, and save your settings under any name you like, this is to ensure that you can pick up where you left off when returning to the same connection again.
Now you have done that hit open and you should with any luck either be presented with a enter passphrase for key authorisation, enter that and youll be in.
Port Forwarding Mysql From Remote To Local
Should you like us sometimes want to dev locally to a remote database, Putty can be used to tunnel a mysql connection from a remote server to your local mysql port. To do this in most cases simply forward the following or well at least for me.
Navigate to the following.
Connection -> SSH -> Tunnels -> Options Controlling Port Forwarding
L 3307 port destination to
the remote database.
Add that in, head back to session save it and then open it and wollah you should now be able to dev locally to the remote database, by forwarding mysql to your local ports.
This is just a quick and dirty tutorial and not meant to be a fully comprehensive guide, however if theres something you want to know I may be able to help, so leave a comment.
To deny access to a folder or directory, simply create a new .htaccess file inside that directory.
Then depending on the authorisation type you want to use you can make rules to allow or deny access.
View some examples below.
Allow by Ip
allow from 188.8.131.52
deny from all
This denys anyone not on ip 184.108.40.206 access to your folder.
Lately I have been considering PHP frameworks and using them to speed up development of small projects, whilst also considering the MVC (Model, View, Control) approach. Most people looking for a PHP framework seem to stick with CodeIgniter, Zend or Symfony. Each with there own advantages and disadvantages. Which one is best is all down to personal taste and its very difficult to make an educated selection of the framework thats best for you. Its baffled me infact, that I can’t put my finger on the framework that I think works for me the best.
So I plan to try and develop a small project in each of these frameworks and decide after that which one I think is the best for me.
For more complex sites, I will continue to use my own custom framework as it helps to keep down page load speeds and ease of understanding.
Check back here over the next month or so, to see what I get up too. As I will be posting all about my experiences with the frameworks.