Have Plugin Description and Release tab read a markdown or txt file inside zip, so plugin developer doesn't have to update via the web interface.

Add a page for error handling to the documentation covering but not limited to error emailing and customizing the error page.

we should have a job board on the main wheels site. don't know if you want to charge for posting the job ot not, might be a good way to cover some of the costs of the evangelist teams expenses?

it would be static html pages of the documentation section for someone to drop into their webroot and have local access to the docs.

http://www.technoclasm.com/2010/02/coldfusion-on-wheels-our-first-journey-together

page for donations

Clarify the user controller mentioned in the database tutorial, here are some suggestions http://groups.google.com/group/cfwheels/browse_thread/thread/55f9cc3bcc1b762b

Ability to request plugins for the community to implement.

For example, on the belongsTo() reference page, it would be nice to have "See Also: hasMany(), hasOne()".

That info is available with a few clicks, but it would be nice to have the links on each page.

Thanks for the great docs!

A place in the Community section for people to submit projects. This section would list open source projects like Spash CMS, commercial projects like Reservoir CMS, and other projects like MARC and FuseGrid SDK.

I don't think the issue of var scoping is touched upon enough using Wheels. My understanding is that there is no need to var scope anything at the Controller level. But any custom functions or UDFs in the model must be var scoped. While it's common to use the "this" scope of UDFs in the model, it's not clarified why the var scope isn't used.

I'd like to see some more information on creating and accessing custom queries and other things that may not be "best practice" in the cfwheels world, yet necessary in some cases or helpful to newbies that are easing their way in.

Add Instructions for Tomcat to URL Rewriting page http://cfwheels.org/docs/chapter/url-rewriting

The reloadPassword() needs to be set on public sites, and the docs about that setting seem to be getting skimmed over by new developers.

I'd vote moving/making a page specifically for this setting and/or putting a message in the debug output next to the reload links when the reloadPassword isn't set, but something needs to be done to make it more prominent and less likely to get skimmed over.

I tried to upload a plugin without an index.cfm and received a convoluted error message.

Zip archive is missing a required file
Latestversion can't be empty
Filesize can't be empty
Filename can't be empty

Could it be cleaned up to be more clear? Something like -
You are missing a required file:
index.cfm

Add a wallpaper page to show community created wallpaper

Add these fields:

* GitHub username
* Biography
* Company Name
* Company URL

Others?

Comments on video tutorials, so we can get some discussion, questions & answers going about the video tutorials.

Right now, clicking the Feedback button on the website gives you issues posted to this UserVoice forum. Some people are thinking that this is a place to submit ideas for the framework itself.

What I propose is that the box that pops up after clicking Feedback shows links to the Google Code issue tracker, the UserVoice forum, and the Google Group. That way you can more easily distinguish between the 3 options.

Add a repository like coldbox where there are full-scale demo applications that can be downloaded and tweaked. Open source frameworks need open source apps!!

Feeds for newly created plugins, recently updated plugins, and update feeds for individual plugins.