Andy Seaborne wrote:
On 15/02/11 10:57, Dave Reynolds wrote:
On Tue, 2011-02-15 at 00:30 +0000, Ian Dickinson wrote:
[Great job summarizing the current structure and possible goals!]
The final attachment sketches a possible solution. The first level of
the hierarchy roughly corresponds to groups of suggested user goals.
I think there's a missing top level goal in there, "get Jena" :)
(should include the license link as well as download and maven).
The difference between learn/guide/indepth isn't completely clear to me,
suggest relabelling to something like:
- Getting started
- Tutorials
- In Depth (or Documentation or Reference)
+1
Also "Getting Started" might be task-focused.
The "getting started" I tend to like more are the shortest ones:
1 page, 5 minutes and I am up-and-running.
Random (but good IMHO) examples are:
- http://rubyonrails.org/download
- http://hbase.apache.org/quickstart.html
- http://incubator.apache.org/whirr/quick-start-guide.html
- http://code.google.com/p/google-refine/wiki/InstallationInstructions
- ...
From a "getting started" for Jena (since it is a library used mainly
by Java developers) I would expect to quickly download an "Hello RDF
World" example (already configured as an Eclipse project) which shows
me how to read an RDF file in any of the RDF serialization, perform
some minimal inference over it and write results back to a file. It
should not be longer than 1 page and it should not take me more than
5 minutes to complete.
For Jena, also, we probably need more "getting started" pages:
- Getting started with Joseki
- Getting started with Fuseki
- Getting started with SDB
- Getting started with TDB
- Getting started with Inference
- Getting started with ...
- ...
"1 page, 5 minutes" mantra is still a valid one for those, IMHO.
If the "getting started" page is task-focused, I'd like us to chose
one task as "the getting started" page and point to the others at the
end of that page, as next steps.
The last thing I want to do when I want to quickly get started with
something is to chose what I should pick to get started with. ;-)
Paolo
What about a (user) wiki? We have a project wiki - we could have that
for notes/FAQs/... whereas the main site is the definitive documentation.
Andy
