(@brucebostwick) kudos icon +

Interface/User Experience

Open API based user selectable themes/skins

With a fully open API to the backend data, it would be possible to create multiple GUI themes for users to choose from, as well as easily modify the default front end GUI or, for expert level users, even write their own custom ones (and possibly submit them for use by other site users, if they're popular). This would get around the "there's always a complaint" problem, as well as the "change noise" problem, particularly... more »

Voting

-1 votes
Active
(@brucebostwick) kudos icon +

Interface/User Experience

Combine map info in a layer-selectable map view

I've seen several suggestions for presenting geographically-based info in an easily browseable form. How about a general "Where Is It?" page with selectable layers and/or search options using Google Maps API?

This page could potentially integrate a large amount of information in ways that not only allow it to be easily navigated. Possible layers to consider:

- places of interest
- city resources (police/fire stations,... more »

Voting

1 vote
Active
(@gregoryfoster) kudos icon +

Content/Information Architecture

Subproject: Data Curation Project

On Saturday morning, May 16th, 2009, the City hosted a meeting soliciting input from the community as they re-ignite the CoA website redesign project. It became clear that the technical staff who will be responsible for implementation of the CoA website are enthusiastic fans of making as many data feeds available as possible. However, they are also privy to the realities of the heterogenous and often legacy computing... more »

Voting

4 votes
Active
(@brucebostwick) kudos icon +

Content/Information Architecture

Use WebKit (HTML5) Client Side Databases When Available

HTML5 includes a powerful client side SQL DB capability that hardly any sites use yet. This would be a perfect place to store user prefs and other user-specific data instead of in session variables, if the browser allows it. Could fall back to session variables and cookies for older browsers, but any WebKit based browser should be able to manage its own user data.

Voting

2 votes
Active
(@scottfarnsworth) kudos icon +

Feature Request

See your energy consumption over time, vs neighbors, vs 'average-ness of temp' etc.

People should be able to see their energy consumption graphed over time, e.g. month by month over a number of years. And also as compared to various other pieces of data: residential average, average for similarly sized houses. Also shown in conjunction to monthly deviation from the average temp for that month, for e.g. Things that could allow one to see how one's work to lower personal energy consumption is going (and... more »

Voting

3 votes
Active
(@mike.schoenfelder) kudos icon +

Content/Information Architecture

Socially Organized Meta-Information Portal

Clearly, the CoA website needs to provide access to information and services sourced by CoA. However, there is no need to replicate information that is available elsewhere. The CoA website should serve as a centralized portal, aggregator, rebroadcaster & directory of information sources (not specific external content). Owners of the information sources should be able to self-register. CoA users should be able to tag,... more »

Voting

2 votes
Active
(@brucebostwick) kudos icon +

Interface/User Experience

Embrace the Novice User

One thing to keep in mind for any city website is that it is the online face of the city, and may draw an audience demographic composed of a much larger population of novice or inexperienced users than other types of sites.

Beyond the existing suggestions of making the site's front page as simple as possible, the overall design of the site should be assistive whenever possible. Most novice users find even their own... more »

Voting

1 vote
Active