> -----Original Message----- > From: David Crossley [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 23 August 2006 3:09 PM > To: dev@forrest.apache.org > Subject: Re: [RT] A new Forrest implementation? > > Ross Gardler wrote: > > David Crossley wrote: > > >Ross Gardler wrote: > > The fact is that they do use Forrest for this. We encourage it with our > > home page too. > > We probably need to change our home page. > > > We have heard from a couple of users who started with Forrest this way, > > attracted by the promise that it is simple to extend then they > > discovered it was not and lost interest. > > One point that i was trying to make, is that we might > need to re-assess who is our target. I, for one, am here > to build a project that handles semi-advanced to advanced > publishing needs. I don't want to appeal to users who > only want "simple websites", especially ones who cannot > be bothered to explore beyond the basics. > > -David
And this has been why my navigation/tabs suggestions have been at odds with yours, going by the wording on the home page and my general impression was That we were always targeting 'users' to use the software, whilst encouraging developers to become a bit more involved and help improve/maintain forrest. I would agree though that this publishing framework should be targeted to a more dev-like audience, those that don't mind getting their hands dirty a bit. The likes of system admins , web developers (as opposed to designers) or those that choose software for their (company's) particular needs, then install for use are a good target, the actual 'users' of the software, those that are the content creators should be going to the system admins for any requirements and so is their problem. How and who we end up targeting, should not sway from the goal of making forrest an easier package to use as well as ease of development. Just on a year a go, a Jira Issue was set up entitled 'Forrest Strategy and direction' - seems appropriate to revisit that issue and see what ideas there have been dealt with, what we still need to deal with and what we can drop. http://issues.apache.org/jira/browse/FOR-630 (Strange how a jira issue of Critical Priority is also unscheduled, just seems a little odd to me) Gav... > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.405 / Virus Database: 268.11.5/425 - Release Date: 8/22/2006
