Live!

The big day has finally arrived... my website is now live!

Although there may be a lack of content on there at present, rest assured that there will be over the coming months. I also need to start creating some themes for the site, a nice content management system, and get that important Web Accessibility Guidelines "AAA" recommendation.

Here's the link: http://www.aaronallport.co.uk.

Please feel free to look around, and let me know your feedback. I allow anonymous comments on this blog now.

Cheers,

Aaron

Fraud tackling

As mentioned yesterday, I had successfully signed up for hosting. Trouble is, the hosting company I used get rather serious when it comes to ge-referencing your IP address when you sign up, in an effort to tackle fraud (which is a good thing).

My work computer goes through a proxy in the US, so instantly there is a problem as my home address is in the UK. On top of this, my working address is Switzerland, so I have had to write two rather lengthly emails already to clarify the situation.

This puts a bit of a hiccup in my pushing live plan, but hopefully it will get sorted soon.

Hosting Secured!

I finally got my hosting secured today. Very cheap and secured for 2 years. As soon as my setup details are through I can finally push my website! It seems a long time in the making, but I have probably spent more time sorting out hosting than actually doing the site.

I'll post the web address as soon as it's live, then its time to re-engineer the engine behind the site, validate xhtml/css/acessibility.... the list grows!

Ta ta for now..

Hosting...

Website front end is now fully complete. I am going to get the site "as is" up on the net soon, whilst I concentrate on the back end stuff to enable me to publish blog entries, CMS, etc. I am also stratching my head trying to get the site WAG certified. Its a mammoth document, but hopefully I'll get through it.

I aim to push next week once I have sorted out some hosting.

Bis dann...

Website almost done!

Its nearly done and its looking good so far, with fully valid XHTML 1.1 Strict and CSS 2.1. W3C Accessibility is in there too, and its all shaping up nicely with the XML/XSLT content management system I have developed.

Hopefully I will be able to push next week to let some of you see what I'm about!

Ciao

Tackling non-standards compliance in asp.net 1.1

A lot of large organisations still use .net 1.1 and subsequently asp.net 1.1 because of processes, software packaging etc.

In these rock 'n' roll standards compliant days of the web, a fundamental problem remains. Asp.net 1.1 likes to use proprietry attributes (such as script language="javascript" as opposed to type="text/javascript"). This means your asp.net 1.1 web application fails in some standards compliancy isuues, namely proprietry attributes in your markup.

Using some fancy DOM Scripting may be one way of removing unwanted attributes and inserting the right ones, but surely that's just holding your hand up and saying "I know its dirty markup, so I'm going to brush the dirt under the rug and pretend it was ok all along". Trouble is, with a little searching, clients can uncover the "dirt from beneath the rug".

How else are you going to remove the proprietry "language" attribute from the postback event?

Holiday Snaps

I have finally got some pictures from my holiday off my camera, and I thought I would share a few for your viewing pleasure...

This is Mark, clearing the beach as soon as he took his top off!














This is a view of our beach at sunset. The water was freezing, but nice and clear.













This is a view of the sea at sunset. You can just about make out Mark's head from the top of the rock.






Ciao for now...

XmlDocument woes

I have been making extensive use of .net's XmlDocument object within an asp.net application I am developing to generate XML files. I do love the ease of this object, but it takes such a large amount of code to do anything complex.

Maybe that's an idea for something to add to my framework library...

The website is nearly done, content being added all the time. Any time now...

Moving along, and why I still hate full-on CMS

The website is starting to move along nicely now. I have had time to finish all of the "vanilla" design, plus all basic behavior is there. I need to add that content now, and I can see this taking up a lot of my time.

This is where a CMS or Content Management System may prove useful. I ended up making a very basic version of a content management system for a customer website once, as the only functionality they needed was to alter the content, not alter the design or behavior.

The reason I made my own basic CMS for their website was because many CMS systems allows to user to create and manage complete websites. I designed a complete website for them, and used a "tag replacement" system with resource files that are used to replace the tag with the appropriate content. This is all managed from a secure part of the site, acessible only by the administrator of that site.

I see the benefit of CMS systems, but I still think they should be left to Content Management only, a web designer should be responsible for the web design.