It's so sad to see that things have finally come to an end. But as they say, all good things must come to it. The site is out of our hands now, now that we are finished with the class. As it stands, it's workable and with some minor help, the client can get it up and running to how he wants it. It's not 100% done however, and we were not given enough time to get it up to that point. At best, it is at around 80-85% completed. If we had maybe a few more weeks or so, we could've had it all ready to go.

In the final week of working on this project the frontend coder team were dazed and confused most of the time. It’s been a very interesting week to say the least about the events that occurred.

We started off the week trying to get everything set into the skeletons we had, by making all the navigation links, filling the content, and creating a tree chart for the centers. The tree chart turned out to be a failure as when a new page was loaded the tree would be reset to closed. We thought we could overcome this by the back end implementing a single page layout, but it still reloads the page and would cause the tree chart to fail. We gave the back-end all the content.

Thus far, we've made pretty big advances in the site, yet there's still a lot to do. As it stands, we have the template down for the basic pages, and now it's a matter of getting the content into the pages, as well as getting the links working, and all of next week can be finishing touches. It's going to be a close scrape, but I think we just might be able to finish it in time.

This week we made a lot of progress on the front end work. After getting some much needed info on CSS layouts, the web page quickly came together on Monday. We got together with the back end and the designers and made a lot of progress on Monday. We got the colors to appear correct and got the text boxes in the right placement according to the design the client picked.

Week 15 proved to be a very challenging week for the frontend coders and I. While implementing our code with the design layout, there seems to be a new problems lurking. As the deadline of a rough working website on Monday approaches we find ourselves buried with problems. Without the growing problems the home index page is completed (minus the working links to each corresponding site).

Awww, I'm only partially sad that my wonderful image-based design didn't work out.

Monday we decided to switch the entire layout from our planned use of tables to pure a CSS layout. Danny had come up with a image based layout, but that is not a good way of laying out a website. I was given a quick tutorial on CSS driven layout. And now I will contact Danny and Gary about helping create this CSS based website, and upload it to the servers for the other teams. With an external CSS page, it will be easy to create the rest of the pages because of the forced styles.

While working on the project this week, I was able to accomplish some goals that were set each day. Unfortunately, it was slow start for frontend coders this week. The waiting game on the client’s decision on certain aspect of the website, held back production for a few days. It was really difficult to start the structure of the website without any of the client’s decision on the design layout. In addition to the absent of the clients decision, the frontend coders and I were unable to retain any information because their website was temperately down.

Yeah, I know it's late. It's not the first time. Let's move on.

Well, so far we've managed to back up the entire site on our own, so Gary and I have half of the site backed up. Now that we know what exactly we're dealing with, we're going to move forward with the project, finally. It's too bad though, since I liked design #5, and doing tabs would've been pretty neat, but we are assigned the grunt work.