Website Update: Complete!

Finally my revised website is now up and running, and I would like to review some of the lessons which I learned during the process of revising a genealogy site with some 7000 - 8000 pages. This was the first major rewrite for 5 years, during which time coding techniques have changed, and visitors are looking for increasingly greater interaction and usability.

I started thinking about the design in November 2009, with the major changes being to the index pages and applying a common theme throughout the site. The headers for the Pedigree pages and some others I decided to leave, except for colour changes. I have said before, but I will repeat, design is not one of my strengths, so it took two or three weeks before I decided to use a scheme based on the colours of nature, mainly blue, green and brown, with an index page design to suit.

To write and verify the coding took another two months of work (actually three months but one was lost through illness and holidays). I like to work to dead lines, so in November I settled on 1st March for the launch, revised to 1st April, and it actually went on-line on 2nd April.

Relaxation

I recommend taking regular breaks! In the early hours of one morning I was working away trying to get rid of a bug, and nothing which I did seemed to make any difference. I simply could not understand it! Only after a short break did I realise that the screen I was looking at was on-line and not the one I was working on using my PC.

Tools used

The Pedigree pages were created using Legacy modified to CSS with the excellent LTools designed for use with Legacy. For my text (HTML, PHP and CSS) editor I use PSPad which allows batch search and replace. Because I have inserted some PHP in all my Pedigree pages I have to change all the file extensions from .HTML to .PHP using Ken Rename, and, finally, I also have to insert some script into the coding. This can only be done after the previous processing and hence requires the use of Regular Expressions to locate the point of insertion. To batch process I use Actual Search and Replace, but note that it cannot write the search and replace the strings for you!

Testing

Arguably this is the most important bit, it is certainly the most time consuming! Because of the use of PHP, I cannot test the Pedigree pages in IE unless it is actually on the web, which is something of a pain. I do, of course, have a folder on the server which I only use for testing purposes, but there always seems to be a difference between how something behaves in that folder and real life!

Links can be tested on-line using the W3C Link Checker, and do remember that for a 404 Error Page all links have to comprise the full URL ie. "http://www...."otherwise even your CSS won't work. This will not quite be the end of it, though, as you, or your visitors, will probably find a few missed bugs for a few days afterwards - make sure they can readily find a way of contacting you!

Finally

Ensure a plentiful supply of coffee, and enjoy!

Genealogy Website, New, Improved, & How 2

Everything had been going swimmingly with my new site, until I received from Dennis of Ltools a sneak preview of his forthcoming program update. He has made a couple of alterations to this program which changes the Legacy Pedigree web page output into validating CSS.

One of the functions of this program enables your own custom HTML, which Legacy allows you to incorporate into their code, to be exempted from processing by Ltools. I use this twice on a Pedigree page, for the header and footer. The changes which Dennis has made improve the logic behind the program, but in so doing tighten the way way in which we must write our code. I have detailed the couple of restrictions involved in my tutorial.

Naturally, my coding didn't comply, and since I work on the principle of "only as a last resort read the instructions", it took me a while to sort out what was going on! Basically they are that the start and end tags of an HTML section eg. a <DIV> must both be either inside or outside the custom section, and nesting of comments when using Javascript should be avoided.

The race to get my site update completed by the end of March is now definitely on!

Genealogy Websites: New, Improved, Updated & How

My current site Fergy's Website has been in its current form for over a year, except for the Pedigree pages having been converted to CSS. I commenced work on the new site in November 2009 with a view to launch on 1 March 2010, although this was pushed back to 1 April 2010 mainly due to illness.

What I hope to do over my next few Blogs is to illustrate the objectives and problems and how these were overcome. Please do not think that this is going to be so technical it will over your head, some of it perhaps, but most can be applied with little knowledge of programming.

It is essential to draw up the criteria which need to be met for the revised site, mine are:

• It must be based on the Legacy Pedigree Web creation function, for no other reason that I really like this layout. I have looked at formats such as The Next Generation, and others, most of which require a GEDCOM upload, but, for me, Legacy was the one.
• To maximise the use of CSS to separate out the design from the HTML data.
• To replace the Javascript navigation with CSS, and in general, minimise the use of Javascript.
• Where possible apply the most modern CSS and HTML standards.
• To ensure cross-browser compliance, including IE6 - which continues to be used by a surprisingly high percentage of genealogists!
• To redesign the Index page, which given that I do not pretend to be a designer is no mean feat!
• To ensure W3C standards are met.

Some of the above aims obviously conflict with each other, so compromises have to be made. These will be described later.

The first problem is that the Legacy Pedigree web pages are not W3C compliant and are written exclusively in HTML. Whilst I had converted the major design components to CSS, to convert all would have meant writing a program to automate this, or using a program which would use Regular Expressions to convert each tag individually - ugh! Unfortunately the first alternative I thought to be beyond my VB.Net programming skills.

However, in 2009 Ltools released a program for Legacy users which validates the HTML and converts all to CSS, and it was this which I used last year to overcome this main stumbling block to achieving a major aim. Some information on the use of this tool is also given in my tutorial here.

The other items will be considered in future Blogs, so watch this space!