Similar thoughts here.
I could also see the "In the beginning..." prologue being a bit confusing
for new users.

On Sat, Jul 11, 2015 at 3:51 PM, Dylan Millikin <[email protected]>
wrote:

> I can't second this enough. I had been thinking of bringing this up for a
> while now and had compiled a list of what I thought would be "welcome
> requirements" for non-Java developers looking to use the stack. It went a
> bit beyond the scope of just documentation though but it came from the same
> place. I was holding onto it for after GA.
>
> On Saturday, July 11, 2015, Matthias Broecheler <[email protected]> wrote:
>
> > Hi guys,
> >
> > over the last couple of weeks (in particular after presenting on TP3 in
> > Seattle at the end of June) I have gotten some feedback from a number of
> > folks who wanted to try out TP3 but didn't know where to start or what to
> > do.
> > A lot of that comes back to the current homepage:
> > http://tinkerpop.incubator.apache.org/
> >
> > While this page contains all the information experienced TP users would
> > want to find, newbies seem to get lost:
> > - It doesn't really explain what TinkerPop is or does beyond the generic
> > statement "provides graph computing capabilities". Why should somebody
> care
> > about TP3? What does it do specifically? What does it look like in
> > practice?
> > - There is no "Getting Started". While the documentation is a beautifully
> > written and comprehensive document, for a total newcomer it is very
> > overwhelming.
> >
> > Not saying that the website is bad, but that it doesn't serve newcomers
> and
> > interested developers very well.
> > I would suggest that we delegate some information (e.g. 3rd party
> > libraries, how to contribute) to subpages and use the homepage to help
> > newcomers figure out what this is.
> > I think Apache Spark does a reasonable job at this:
> > https://spark.apache.org/
> >
> > Would you guys mind if I took a crack at this with Daniel's help on
> getting
> > started and some examples? If so, how can I get access to the page to
> make
> > some suggested changes?
> >
> > Thanks,
> > Matthias
> >
>

Reply via email to