This is the repository with the source content for the http://neo4j.com developer resources section.
The content is written as textual format in AsciiDoc rendered with asciidoctor using templates to HTML and pushed to the gh-pages branch or to wordpress.
You can render a single document to its index.html by calling render.sh path/to/doc.adoc or all with render.sh
Most of the documents in this developer resources section are organized as a guide.
Those guides come with a consistent structure and similar use of language and assets.
Each of the guides lives in its own directory and is rendered into an index.html file for publication. You can run the rendering process by calling render.sh on the command line.
A guide has this general structure
-
goal for this guide
-
prerequisite with links to relevant sections
-
recommended experience level (Beginner, Intermediate, Advanced)
-
Multiple sections and subsections outlining the content use a welcoming and helpful, not overly complex or eloquent language with examples in code, pictures or videos
-
each top level (
===) section can be followed by a sidebar section which will be rendered on the right side with links to follow up information (internal links, calls to action, external links)
Please see the example guide template file for a blueprint of the document structure needed. And as rendered document.
-
Other developer-resources and neo4j.com pages
-
Manual Pages and Articles
-
Blog Posts (http://neo4j.com/blog, Rik, Max, Mark, Kenny, Michael, Ian, Jim, …)
To explain how to use Neo4j with different programming languages we provide an intro section per language, located in language-guides/<language>/<language>.adoc.
To show how the different drivers for that language would be used/integrated we also provide small example projects/setups in the language-guides/<language>/<driver> directories.
The example application is a simple, single-page movies app based on the Neo4j-Movies dataset that comes with the Neo4j-Server (:play movies in the Neo4j-Browser).
See an example running here on Heroku.
The HTML page uses jQuery ajax requests to query 3 REST-Endpoints in the backend for /search, /movie and /graph
-
/searchlists the movies found by title -
/moviereturns details for a single movie -
/graphrenders the full graph as a basic d3-visualization
This is our current list of projects:
-
java/jdbc
-
java/server-extension
-
python/py2neo (Thanks Nigel & Mark)
-
python/neo4j-rest-client (Thanks Javier)
-
clojure/neocons (Thanks Rohit)
-
go/cq (Thanks Wes)
-
perl/neo4p (Thanks Mark)
-
php/neo4jphp (Thanks Josh)
-
ruby/neo4jrb and ruby/neo4j-core (Thanks Andreas)