Slightly new format and new priorities...
"Anomalies"
- Invite Readers/Authors/Admins
- Fix
- Fix
- Allow publisher to specify that basic HTML (bold, ital, ul and link) should be allowed in comments and replies - the default is "escape html"
- Fix.
- Fix.
"Immediates"
- Community features (top blog, most recent post, newest blogger, most popular, least popular, trackback mesh (like a webring)
These are actually ndividual features that will be prioritized on an "ease of development" basis and banged out on a recurring schedule as TVs that we can implement FCFS into www.
- High.
- High.
- Marketplace (automated permissions expiry)
I love this feature, I want to do it now. We need to get a better sense of the market before we can increase its priority, but the sheer coolness of the idea will at very least set us apart from the dreary competition. If we can get even five or six publishers using this effectively, they will likely be influential and talk about it. Which, at least, is worth something from a publicity perspective.
- High.
- High.
- Mass style change. Allow a reader to change the look and feel of their blog with one click.
- High.
- High.
- Kickin Stats!
We will need to determine what's important and what isn't. Hitcounter doesn't go far enough, analog goes too far.
- High.
- High.
- Flag protected articles with a visual cue to let readers know that the article is protected.
- High
- High
- Allow post article from file manager to photo album or text blog.
- Medium.
- Medium.
- Post via mail
For the moblogging crowd.
- Medium.
- Medium.
- Comment permalinks.
Self-explanatory.
- High.
- High.
- OCS Import/Export
- High.
- High.
- Search my blog
We will need some notion of indexes and keywords dropped into play.
- Medium.
- Medium.
- Last n Entries template (recent posts).
- Medium.
- Medium.
- Keywords for articles
- Low.
- Low.
Futures (unprioritized)
- Restrict users based on username.
- Medium.
- Medium.
Hold (prioritized)
- Blogware Aggregator (inc. Newshub, Blogware native as well as RSS feeds)
The main point of this function will be to allow publishers a quick and easy way to aggregate content, review it, manage it and post the ones that they like directly to their blog in a simple and efficient way. This isn't for readers, that will come next - we need to worry about the post function more than the readers function at this point. ;)
- High.
- High.
- MakaWiki
We could almost turn this into a wait and see while we figurre out what the value proposition is. Its not clear who will be using this or what - but the extra-dimensionality that the feature will add to the typically linear progression of the blog is an interesting development. Let's chat more about this one when we get a chance. Maybe we should install some tools into the sandbox to further explore the what the technology has to offer.
- Hold.
- Hold.
- Post to multiple blogs.
- Hold.
- Hold.
- PhotoRSS
Self-explanatory. We need to allow for this. Absolute links in the RSS pointing back to the original image. Its simple and doesn't break the spec (AFAIK)
- Medium.
- Medium.
- "Mark Comments as Read/Unread" function.
Refer to "More on 'Mark as Read'"
- Low.
- Low.
- Related posts
This can be done manually or programmaticly. (ie - a search which lets you check off titles of previous posts and then go on to post the new article... like related items in a shopping cart.)
- Low.
- Low.
- Rotating entries in a particular template.
This really is MOTD - where "M" equals "media", "message" or "method".
- Low.
- Low.
- templatable RSS
We've talked about this quite extensively. If we can knock it out fairly quickly, then we probably should. If not, then we might want to leave it for a rainy day.
- Low.
- Low.
- URL Templating
Same here. I would love to give users the capability to set their own URLs, but the performance tradeoff might not be worth it.
- Low.
- Low.
- POD
This is a great idea, but its not clear how web hosting companies will be reacting to the offering. If it turns out that we are evil scum villains, then PODs will need to rise quickly to the top of the list - if no one raises any objections, then we can take it off the list. The trick will be figuring out what to do when the reaction occurs (as it should) somewhere within that continuum. My preference is to wait and see what the market has to say while continuing to think about potential features. Note that this is not a feature that has been designed for "HP" and their internal corporate communcations requirements, but instead is conceived as a solution to the "I want to use my disk and space" issue that we might encounter.
- Hold.
- Hold.
I would like to be able to allow notify subscribers to specify a "digest" or "real-time" distribution preference when they subscribe to categories etc.
Need to be able to post text entries within a photoalbum independant of photos. Not sure how this would work.