I updated a customer's site today from 2.6.3 to 2.7, in preparation of handing it off to our customer. I will be training them today, and one of 2.7's touted improvements is usability. I don't weigh in on this aspect but I'm trusting the wordpress community at their word. There's a number of interesting business model questions associated with developing customer sites with Wordpress but that's for another post. Here's some background on the upgrade: Plugins:
I wish ubuntu had a great text editor like BBEdit, TextMate, Coda, or UltraEdit. I use (and like) Quanta Plus but its development has been very slow as the package maintainer readily admits. I don't doubt I can modify vim to better emulate these applications, but it is time-expensive.
Drupal, the open source CMS environment, can be formidable in its complexity. I stumbled across the Zen Theme while researching themeing and I am pleasantly surprised by what it provides. If you know CSS well (and a web designer is remiss in not knowing CSS) then check out creating themes with the Zen theme. Now, onto CCK, views and node templating.
I don't intend this post to be comprehensive (nor introductory) but it will address what worked for me after much googling and finding many contradictory pages on the matter. For Drupal to use "Clean" URLs, you must enable server URL rewriting. On apache, this is a trivial task. On lighttpd, much less so. Here's what I did to enable a Drupal directory specific rewrite capability while staying within what appears to be a best practice approach to extending my lighttpd configuration:
I was experiencing a deep apache headache (php5 wouldn't load into apache2 via apt-get) on my ubuntu 8.10 desktop, after much fruitless searching, led me to a "plan b" answer: lighttpd. It's faster, more svelte on the resources, and one of my favorite programmers swears by it, so I'm open to trying it.
Sometimes git can be as dark and mysterious as Dan Brown's popularity as a novelist. I was struggling with retrieving a newly created remote branch: git checkout --track -b screensizes origin/screensizes Which rendered: fatal: git checkout: updating paths is incompatible with switching branches/forcing Which is as clear as mud. Googling was fruitless until I found this suggestion: [Switch to the root directory that your tracking]
Outlining is a very effective way of brainstorming — capturing a lot of information randomly and then ordering the information in a more coherent manner. I find outlining indispensable at the start of projects, such as scope definition, quoting, task identification and sorting, and so on. I've used Microsoft Word's outlining feature for some time now. It is easy to use, but the canned style sheets are overkill and I invariably turn them off. Additionally, keeping Word up to date has costs and it consumes a lot of computer resources.