Twenty-four hours ago, I was deploying applications from development to production environments in about 5-6 steps. Today, tomorrow and every day in the future, I'm doing it in 1 step, with Fabric.
We use Zope related software throughout our day at GateHouse Media. Specifically, we run a hosted solution, Zope4Media provided by Zope Corporation. Our level of involvement with the software on the development end of things is strictly limited to template development in ZPT.
There's a growing concern of mine revolving around the desire to use JavaScript in conjunction with, or in replacement of, XHTML-based navigation on websites. There are a lot of resources out there investigating the use of JavaScript with regards to search engine performance, web accessibility, and web interoperability. I'm going to try and summarize my thoughts here, and establish general guidelines to a healthy use of JavaScript with website navigations.
I have a bunch of divs throughout a page, and I don't control where the content comes from. I want to be sure those divs contain no XHTML, except for <p> tags.
Yeah, the title is pretty long. I really couldn't come up with anything better. Anyways, after the recent switch to Media Temple for all of my sites as a result of this debachle, I needed some peace of mind with regards to file changes and database backups for each of my sites.
We at GateHouse Media have lots of bloggers. We also have lots of newspapers. Naturally, we like to drive traffic in full-duplex. Unfortunately, because we have so many data 'sources' and 'destinations' always changing, it often becomes difficult for us to keep up with the massive amount of new blogs on a daily basis. We sought out to find a more dynamic process by which we can transport 'teases' of our blogs to our sites.
