Archive for January 16, 2009

Ideas for Further Development

I have a few ideas that I will potentially implement in the near future, but this depends entirely on my direction. Throughout this project I was sorely tempted to move over to WordPress, but due to the amount of work I had already done, I felt it would be a waste. So I stuck with Ruby on Rails, and although I see its huge potential, I would only really be trying to replicate the functionality and brilliance of WordPress as a content management system.

The Blog

But before completely shunning the idea of continuing along the tracks with Rails (pun intended), I could list a great deal of possibilities in building on the current system. The blog interface could be improved further by using an enhanced GUI allowing users to format their posts with basic HTML or BB code, limiting them to simple formatting options such as inserting images up to a certain size, formatting text, etc. This would be achieved using another plug-in for Rails called RedCloth. This particular enhancement is a more complex formatting engine that allows you to implement simple mark-up such as *bold*  and _italic_.

RSS would be a useful feature to include on the blog so that users do not have to go out of their way to revisit the site for updates. Although Jonathan has a Twitter account where he would post details of his updates, not everyone makes use of this service. RSS and email subscription would be a good way to fill this gap.

The Gallery

The blog aside, I would also like to use a dynamic gallery that allows greater control through a friendly user interface. The gallery I am currently using in the portfolio section, although dynamic, does not allow the user to add captions, or additional information. It does however allow an administrator to add more images to an existing gallery by dropping them into the relevant folder.

Easier Updates

It may also be beneficial to the client to be able to update every page of the website through a user interface similar to that used by WordPress to add a dynamic twist to the entire site. For example, Jonathan’s contact details may change suddenly, and he needs to let his audience know about this.

The reasons I would opt for WordPress:

  • It’s already there, and it works very well.
  • It is open source and fully-customisable.
  • Huge array of useful plugins.
  • Great amount of community support.
  • Very user friendly from the get-go.
  • Not as dependant on hosting capabilities as Ruby on Rails.

The list goes on.

Conclusion

Overall, though I think moving in favour of WordPress would be the best option as it requires less effort on the part of myself and the client in the long-run and would instantly give him more control.

 

Employability

The value of a developer to prospective employers relies quite heavily on the ability to embrace change as standards shift and technologies evolve. I believe an open-minded approach to web development is essential especially with the amount of new platforms emerging on a yearly basis. Two years ago we weren’t aware how big mobile Safari would be or mobile internet in general. The developers behind the apps available for the iPhone have had to adapt their skills in order to become successful in this arena. Objective C isn’t a language that many people are familiar with, however due to its similarity to C++, it has been studied and more importantly, embraced. The same goes for Ruby on Rails. Ruby is said to have quite strong similarities to Perl which is a fairly widely used programming language. After being coupled with Rails, its potential has grown tenfold, now being used in web applications where previously, developers would be using PHP.

On a personal level, the fact I chose to throw myself in at the deep end with a language I have never even SEEN before is perhaps testament to my ability to accept change and force the development of my skills.

On a client-developer level, I feel I have done the project justice, allowing Jonathan access to a wider audience and a platform for self-promotion. He is now able to display his work to anyone who visits the site and is provided with a tool with which to document his professional activity.

Usability

Navigation

I have tried to make my project as usable as possible by sticking to the conventional standards of website navigation. The main tool in achieving this is the ever-present navigation bar on the right of the page. Users do not have to scroll around too much to find the navigation buttons which makes the process much quicker. I have also kept my levels to a minimum. The users never find themselves in a deep structure having to go up several levels before they find another area of the site. The deepest they go is in the portfolio section where they are just two levels in (portfolio > collection).

 

index page

index page

 

 

Buttons in the portfolio galleries are very intuitive, displayed merely as forward and backwards arrows which flick between images – a common navigational signifier which I think users are familiar with.

Functions

The blog features some familiar controls also with edit and destroy options at the foot of every post. This only appears when the user is logged-in of course. The login function is hidden from plain sight and accessed by appending the URL with ‘/login’. As there will only ever be a maximum of two different people logging into the site: myself and the client, there is no need for there to be a ‘login’ button on the blog. This would only confuse users into thinking they are able to register for user accounts, which at the moment, they are not.

Forms within the blog are again very standard in format. To go to the ‘new post’ form, the user merely has to find the appropriate link at the very bottom of the page. When creating a new blog post, the user is confronted with only two text fields: ‘Subject’ and ‘Body’. Below this is a ‘Submit’ button. Again, because there will only be two users of this blog, the controls do not have to be terribly obvious as long as they are positioned in a sensible and consistent manner for quick recognition and use.

 

New Post

New Post

 

 

Accessibility

I designed my site with a view to simplicity and functionality, and with this comes accessibility. The fact I have used high contrast colouring (black on white) throughout the site means the text is highly readable. I have successfully tested the site using larger font-sizes by adjusting the browser settings and all appears perfectly readable. All of my images include alt tags which means screen readers are able to pick-up the content of the images and navigation links and relay it to disabled users. I have also used appropriate header and paragraph tags to ensure that the textual content conforms to the correct hierarchy. I have seen sites that offer reversed-contrast view which makes the background black and the text yellow to cater for certain types of visual impairment; however there are limits to how far one should go given the purpose of the project.

Follow

Get every new post delivered to your Inbox.