Playing about with some more elements of this site. It’s being designed as a one page site, with additional content being loaded on top… when JavaScript is working. When it’s not users will be directed through to a separate page. This will ensure that content is viewable without reliance on JavaScript.
Carrying on from yesterday’s post, today has me looking at some additional site content. I don’t think I’ve had content fall together for me quite so well before.
I’ve pretty much polished off my other outstanding design projects. Today sees me putting some work into a project that I put on hold to get more time sensitive projects completed for them.
This site is a project that I am currently redesigning for a client. We’ve been doing some work with their hosting and other server related stuff and one of the other parties involved seem to have lost the files that made up the site.
This left my client without a site… with no content and nothing to put up at all, as my design isn’t ready for implementation. Fortunately I am rather paranoid when it comes to trusting other parties with work, and I have been making frequent site backups.
The site linked to is a recreation of the design that they had previously, reproduced in a way that will make a future transition to a new design much easier, produced in (according to my time keeping software) 12 hours and 35 minutes. Not bad all things considered.
Oh, and if you ever see code with blocks of in it, I feel your pain.
Today I have mainly been working to recreate a site for a client that was purged from it’s original hosting rather unexpectedly. Fortunately I had been making regular “clones” of it using an app called SiteSucker so I had something to reference to help recreate it.
I also took the time to go over how some (aka most) of the site’s content was laid out. There are lots of poorly coded elements, some places even had <font> tags in it still. Today’s Daily Design is one piece that I redid using Definition Lists, as Opposed to the approach taken originally, which had a lot of code in it…
Had an idea on my way home from sorting some stuff out today for a possible way to place labels in a form layout I’m working on. Today’s post is a mockup of a few variations.
Today has been spent revisiting some old work. As part of what I do I tend to offer support for the people I produce work for and one of my clients was having some problems in terms of SEO. I’m no wizard when it comes to the stuff, but I know enough about the basics to at least ensure that their home page is ranking well. Turns out that some of the plugins I use to help with SEO had somehow decided to stop working.
In addition to this I also decided to address some other aspects of the site, including limiting some aspects of the site from being indexed by google as well as implementing caching of the site to help increase load time for users. Some of the images used in the design are pretty big, so anything that helps cut down on the amount of loading needing done is a good thing.
I also took some time to prepare one of my recently finished pieces of work for a shift from one server to another. SHould be seeing that come to fruition some time tomorrow.
I dunno if you lot are getting tired of sketches and CSS, but I am. Today has a rough mockup of a control panel interface I sketched up recently, based on the Habari Project.
I make rather extensive use of grid systems, in particular the 960 Grid System. It has always had 12 and 16 column grid layouts available, but it recently also added a 24 column grid to the package. This is a slightly tweaked version of it that I use, simplified slightly and tweaked to make use of 10px gutters instead of 5px ones.
Working on a minimal design for an admin backend for a project I’m playing about with. I really love the way that Habari handles navigation in their Admin Panel, and I’d like to create something similar. This is the starting point for it.