Currently search only searches posts and does not include pages. It would be nice if the built-in search were able to search through both types as most blogs / websites using Mango will be a mix of pages and blog entries.

I've seen this on various occasions and it's incredibly annoying. See also: http://www.mangoblog.org/forums/messages.cfm?threadid=4E8C7BF0-D59B-6E2D-10C719C2444F9397

How about releasing the skin browser to be open source for clients to look through.

Are essential to link the articles together, and increase the user's reading time on the blog, much appreciated by Google.

Reader much more usable and customizable.

Plugin automatic update notification from admin area. I am not sure such functionality exist or not but I love it.
May be plugin will have update url which return current version and admin periodically check version for plugin.

It would be nice if we could create a standalone page one that is editable in the admin, but not included in the navigation. Selecting None as the parent makes it a top level page. But I would like to see an option to make it not show up at all unless linked directly to.

It would be good if you can add a feature to add multiple blogs in one single instalation. Something simillar to wordpress Mu.

This would be usefull if you would like to offer blog to members of you site.

Improving the documentation would be great. To be quite honest as a new developer trying to add on to Mange blog is pretty hard because of the lack of documentation.

There needs to be documentation outlining all the data that is stored, the order of operations of each page. What each page associates to, A better example of how to write an addon, better example of how to write a theme, ect.

The way that is currently used for adding addons (giving it a url) is nice. But that should have been the second or thrid way to add them. We should be able to place the addon in the folder and the blog recognize the addon and add it to the list. Or be able to browse our local computer for the addon and add it to the blog.

I would like to see the ability to have members only content within a single installation of mango blog. This means page and posts could be set for members only viewing. Users would have to log in to view the post or page.

It would be nice if this feature could allow templates to decide how content is rendered for members only content. For example, Display nothing, title only, title and teaser.
An off the top idea might be <mango:Posts count="5" members="titleOnly">

Ultimately, just having a members section would be a great help.

Pages should be shown as a tree in admin

Would be nice to add google iframe map to posts to quickly refer to a location you may reference in a post.

The new post/page revision history feature is great. However, I find myself making lots of small changes to posts, which can quickly add up to quite a lengthy history!

For instance, I wrote a post today, and just in the process of fine-tuning and publishing it, I racked up 17 revisions!

I propose the ability to remove individual items from the revision history.

-easily assign post to a different author (great for multiple authors but PR firm edits)
-show only certain authors on blog

It would be very cool, if built in (or via plugin), there was a way to strore statistics on RSS feeds, like what reader people are using, number of subscribers, how often people update etc

(I'm actually not that up to date on rss statistics).

It's notoriously difficult to track this stuff without resorting to something like feedburner, which would mean I have to change all my RSS feeds on the blog I'm running. It would be great to have it baked in.

If you have your database server running on a different port the setup doesn't work. Changing the setup.cfm to extract the port number from the string "server:port" and adding dsn.port to the addCFdatasource.cfm template will fix this.

<cfif listLen(form.server_new,":") eq 2>
<cfset dsn.port = listLast(form.server_new,":") />
<cfelse>
<cfset dsn.port = listLast(form.server_new,":") />
</cfif>