April 2009 – current - http://www.abc.net.au/news/
July 2008 – February 2009 (8 months) - http://ry.com/
Redesign of existing annual report system. Major modification of HTML, CSS, jQuery front-end and some tweaking of the Java back-end.
HTML, CSS and jQuery
Site refresh to match redesign of main site.
Not live yet. Creation of HTML, CSS, and JavaScript templates. Assisting with integration issues into Java CMS back-end
Not live yet. Creation of HTML, CSS, and JavaScript templates. Assisting with integration issues into Sharepoint back-end
Not live yet. Creation of HTML, CSS, and JavaScript templates. Assisting with integration issues into Sharepoint back-end
Not live yet. Creation of HTML, CSS, and JavaScript templates.
July 2007 – June 2008 (1 year) - http://adgistics.com/
Optimising of front-end and adding new content to existing sites. PSD and Flash provided by designer. Creating new themes for existing sites.
Have also gained some experience creating front-ends for Flex web applications.
Most sites useing .NET framework (poor markup). Have tried to strip away as much markup as possible but there were limitations in the back-end.
Adgistics.com
Static site. Cleaned up existing HTML and CSS to validate. Replaced image-based primary navigation with text-based navigation.
AMS for Vodafone built in .NET (restricted access)
January 2007 – March 2007 (3 months)
HTML content creation for government sites. Job requests from internal government clients. Job times varies from 10 minutes to several days. A little bit of CSS, JavaScript, and server-side scripting.
Strong focus on semantic and valid markup. Quality control user scripts were run in Opera to review code to ensure markup met government standards.
…and some small sub sites
September 2004 – December 2006 (2 years, 3 months) - http://aspedia.net/
I would receive a PSD from the designer and slice it into optimised images. The designer also provided any Flash content. I would create a copy of our CMS product to create the new site. I would then modify the CSS and HTML to match the design. I would also configure menus and pages ready for client to add content via a WYSIWYG editor.
My other role was to develop the CMS product (based on PostNuke) and templates (Smarty) that were used to power the sites. Most of the sites were using a shared code backend and their own database.
Short time frames. Small sites being being churned out in a production line situation. Quantity was far more important than quality. This was part of the reason for using a table based layout. Themes for PostNuke CMS.
…and many more that are now redesigned or offline