skiFFie Making Drupal Mobile!

Just over a year since my first look as Drupal v5, an article that I accidentally bumped to the front of the tracker pages due to content rendering issues, I decided yesterday to take a real look at Drupal v6. I downloaded the relevant files and the most relevant modules available and made a clean install. The amount of modules available at present is a bit disappointing however.

Further to a request found on available theme files for the accessibility module I have decided to investigate this a bit further. This development can also be tied into a new project that I am working on so I can kill two birds with one stone. Apart from the afore mentioned lack of compatible modules first impressions were pretty favorable.

My development environment at home is currently:

Windows XP
Apache/2.0.54 (Win32)
PHP 5.1.4
MySQL 5.0.21

I created the required database and went to my local sites front page. Installation was a breeze with lots of new dynamic features that are bound to impress. After the initial configuration I was off and running. I installed the following modules:

devel (currently disabled due to this bug: invalid XHTML)
fivestar
flexifilter (might use this with accessibility module)
google_analytics
image
lists
login_security
pathauto
sections
themesettings
token
vocabindex
votingapi

Then I started to delve into the wicked world of templates and am currently analyzing the "garland" theme. Since this seems to have the most features it seemed like the logical starting point. So far so good. There seem to be many things that I can utilize for the next generation of the accessibility module.

My ideas for the accessibility module upgrade include:
1: Combined mobile themes - administrators choice
2: Switch between mobile and full site possibilities
3: Reduce the chances of botched mark-up of pages

If I get the chance I will be investigating further options of
1: Allowing mobile users to post comments
2: Image resizing for mobile devices

There will automatically be a number of bug fixes. These are currently being investigated and should be resolved shortly. Stay tuned for more details and please feel to post feedback, comments etc. here..