The Anchor Website: .py in the Sky: PART 4

There have been a lot of ideas presented in this series so far, we've spoken about database dependency resolution, touched on applying the emitter design pattern to HTML generation and made a lot of bad jokes. We've not really pointed you at any kind of resource you could use to build a similar system yourself. My reasoning in this has been that we're hoping to just go ahead and give you the code we're using to do all this. When? soon.

This final part in the series is intended to point you at some tools we're using extremely effectively in managing the more mundane parts of keeping a website running. The two problems we solve here are:

• "Argh! you IDIOT! you saved your STUPID programmer NONSENSE over my BEAUTIFUL DESIGN!"
• "Umm, so yeah, now just upload it and we click here an.. oh. Maybe you should have pushed that launch date back a week.

So, the first problem, where programmers over-write changes from the designer when they upload their code is a common one that developers grappled with for some time (only back then there was no "web" and there were certainly no "web designers"). Good news is that "they" came up with a solution.