This is the Vision, it's where I discuss the over-arching strategy and objectives of Morphfolia.  There's also the Product Backlog where I prioritize features (and fixes, etc) and plan (the 'current' and 'next') releases at a lower level; and the Road Map which is a high-level / broad brush look at where I see the product going.

Vision / Goals

• Provide a platform for website development for friends and family.
• Provide a platform that gave me a challenge and scope to explore.
• Provide a platform that suited my style & way of thinking.
• Was enjoyable to work on. (last but most important?  quite possibly)

While the current focus most definately includes 'providing a platform that other like to use', it's also very much about the journey: where it takes me, what I learn from it and enjoying it - the same applies to anyone else who wants to come along for the ride.  This isn't just about WCM / CMS or coding, it's also about architecture ("why did you do it that way?"), putting something "out there" in the wild, business strategy - the whole shooting match.

So, why another CMS in the first place?

Being the family geek I get called on for all manner of technical favours & support, the most demanding of these being websites and strategy.  It quickly got to the point where I needed to decide on a strategy for dealing with requests for website development - not only for friends and family but myself as well.

• The idea of dealing with HTML files and FTP wasn't my idea of a good-time. 
• I'd used PHP at home but worked mainly with MS based technology at work, so my preference was to stay in the MS space.
• Sharepoint?  Hmmm, no thanks.

I tend to like doing things myself - control freak?  Maybe, but I don't think I'm that much of a freak. 

On another tack, you don't always get to do at work what you really want to; I decided that I wanted something semi-serious I could get my teeth into and which would serve as somewhere to explore different things; and so this project was born about 3.5 years ago (sometime during 2005).

A note about "Visions"

I must confess that I wasn't previously a fan of "visions", consigning them to the domain of "corporation-think", however, I'm now a wiser gnome.  Having a vision is crucial to establishing a high-level direction.  It may seem a bit removed in the code-trenches sometimes but it's "the buck-stops-here" place where decisions are made if all else has failed.

You're at the cross-roads: do you build the feature to be robust or fast?  blue or red?  having a vision helps.  Some of the features in Morphfolia aren't there because my father-in-law said he wanted it, but because it was fun to do.