1. Problem: Poorly implemented or no RSS. Even if present it is usually useless, hand-generated, out of date or doesn’t pertain to very much of anything.
Solution: Implement RSS or use a CMS that has RSS built in. Even most good programming languages have excellent XML handling built in.

2. Problem: anything.aspx
While aspx is a semi-decent programming language, using it doesn’t encourage you to use some of the great CMSs or Frameworks like Drupal or Django. Not to mention it screams to the world that you are using windows to host your site. Terribly insecure.
Solution: Use different languages that can run on several platforms to have a heterogeneous environment.

3. Problem: IIS
No respectable outfit, ever… EVER uses IIS as their web server. And it leads to using html mangling programs like Adobe Contribute and Front Page.
Solution: Use Linux/BSD/OpenSolaris or if you must, I think SCO is still around right?

4. Problem: www.example.com vs example.com
Every good website since 1996 has fixed this problem, one redirects to the other. When I go to a government site and I see “Under Construction” because IIS is misconfigured I think less of politicians.
Solution: Correct configuration of IIS or switch to Apache.

5. Problem: streaming WMV etc.
While I believe that governments should disseminate content in open and non-patent encumbered formats(I’m a believer that people shouldn’t have to have a license to read a word document or play an mp3), and even though (most) browsers support HTML5 elements that allow for embedding video, I realize that using flash is the most realistic option. Most government sites don’t even do that, They stream video in wmv and audio in wma. Using this is a bit jenk on a Mac and technically possible(but practically impossible) on Linux. Also transcriptions should be available for every video(for people using text browsers) or captioned.
Solution: Use Flash or open formats like ogg, or better yet use both.

6. Problem: Intelligible URL structure
I am a believer that I should be able to navigate 90% of a website by typing plain English words into a URL. Call me old fashioned but it is just the way that I feel. HINT: It also keeps the site easier to maintain. If the URL structure is a mess, the code is probably a mess.
Solution: Use a language like python or frameworks that encourage or require clean URLs.

7. Problem: English or French?
Every Time that you go to a Canadian Government site for the first time, the site will ask you what language you would like to view the site in. Every browser that has been made in many years has been able to send information about your language preferences. Most English speakers don’t realize this because they are too dominant to ever run into the problem. But if that is too difficult to implement for the government, then enable a checkbox that says “Remember my selection whenever I visit a Government of Canada Website.”
Solution: Learn about cookies.

8. Problem: Colour Scheme
No one worries about the 216-256 “web-safe” colours anymore. NO ONE USES 8-BIT DISPLAYS ANYMORE. But if you had been to a government website even today it seams that they are still subscribing to this philosophy. The design of the sites could be so much more appealing with better colours.
Solution: Use colours.

9. Problem: “What’s New”, “Top of Page” and other similarly useless links.
“What’s new” is a throw back to when site were smaller, they quickly become out of date and are made redundant by things like RSS feeds. Top of page is a throwback to when browsers did not have scroll bars. Guess what? They do now. “A-Z Index” this is an interesting one. Some usability experts believe that “you should be able to access all of a site’s content within X number of clicks”. I would append one thing to this “you should be able to access all of a site’s content within X number of clicks and in under 1-2 hours”. An (A-Z Index) is useful when you approach $items>26. However, there is an upper limit to this.
Solution: Top of page might be useful for accessibility, or text browsers. Do browser detection. If the user is using a browser that would benefit from this show it, if not hide it with Javascript.

10. Problem: Open Data.
I have issues with Crown Copyright. I believe that, in most cases, works that a government create should be owned by the people and not by “The Monarch”. I am sure the queen could care less that she has all the rights to the 2006 Ministry of fisheries report on salmon populations. I was amazed, when during a recent copyright consultation roundtable, Minister of Industry, Tony Clement did not understand why it mattered that Canadians should hold the rights to government works. A good compromise to this would be to make both the crown and Canadians both rights holders. It doesn’t have to be mutually exclusive.
Also government Data should be made available to the public as easily as possible. Either by dumping the raw data on the internet or creating open databases with APIs to access the data. NOTE: It is important that crown copyright be fixed before this happens. I should not have to pay money to get at government data, nor waste paper in the process. All I should need is an internet connection and the desire to find out.
Solution: Create a mechanism and reform copyright so that this information can be disseminated more easily. Embrace Creative Commons. Follow the lead of the Americans.

The other thing that has helped is WordPress 2.7. The biggest thing I had trouble with was staying up to date. I would find myself in an endless circle of not updating and so not posting. It now auto updates. This also extends to plugins. Themes do not yet update automatically but I think this is coming. The new admin backend is a lot more logical. There are things in WordPress that I couldn’t figure out with the old backend. It just makes more sense.

Well jQuery does a good job of abstracting all the browser stuff away and once you get everything figured out it is pretty awesome. It is not really Ajax(although it has some Ajax handling) it is more of a merger of javascript and CSS. They also have an awesome plugin community.

The biggest problem I found was that the code is so minimalistic that it is sometimes hard to figure out what is doing what.