I’m going through the Project list and deciding which things have to be done before “shipping” and which can happen after we ship.
I don’t want to rush to have to write docs when we have a user who is asking for a complicated and yet-undocumented feature. This happened the other day with Reading Lists. There are almost no docs for that. So docs review and new docs goes before shipping.
Imagine a line, on one side of the line are things that must be done, and on the other side things that can wait and be part of the normal shipping of features to an active user base.
Things that can wait till after shipping
-
rssCloud for reading lists
-
WordPress integration
-
Overriding titles
-
News products tools
Things that can’t wait
-
Docs review
-
Starter feeds
-
WordPress signup
News product tools can wait
For now think of News Products as something we use the way the concierge people at A8C use their tools to create unique experiences for people and orgs we work with. We’ll use that process to get a really good, polished set of development tools to share with users. But let’s give it a bit of time to mature.
WordPress integration — depends
It might be very little work.
I’m going to share a browser-based JS page that displays a river from feedland.com. Nothing else.
Can we get this code to run in a WordPress page?
How easy that is to do will determine whether it’s pre or post-shipping.
Plan
We’ll have this list fleshed out by the Thursday meeting (Nov 16).