|
1 | 1 | # GraphQL.js |
2 | 2 |
|
3 | | -This is a technical preview of the JavaScript reference implementation for |
4 | | -GraphQL, a query language created by Facebook for describing data requirements |
5 | | -on complex application data models. |
| 3 | +The JavaScript reference implementation for GraphQL, a query language for APIs created by Facebook. |
6 | 4 |
|
7 | 5 | [](http://badge.fury.io/js/graphql) |
8 | 6 | [](https://travis-ci.org/graphql/graphql-js?branch=master) |
9 | 7 | [](https://coveralls.io/r/graphql/graphql-js?branch=master) |
10 | 8 |
|
11 | 9 | See more complete documentation at http://graphql.org/ and |
12 | | -http://graphql.org/docs/api-reference-graphql/. |
| 10 | +http://graphql.org/graphql-js/. |
13 | 11 |
|
14 | 12 | For questions, ask [Stack Overflow](http://stackoverflow.com/questions/tagged/graphql). |
15 | 13 |
|
16 | 14 | For discussion, join [#graphql on Discord](http://join.reactiflux.com/). |
17 | 15 |
|
18 | | -## Technical Preview Contents |
19 | | - |
20 | | -This technical preview contains a [draft specification for GraphQL] |
21 | | -(https://github.com/facebook/graphql) and a reference implementation in |
22 | | -JavaScript that implements that draft, GraphQL.js. |
23 | | - |
24 | | -The reference implementation provides base libraries in JavaScript that would |
25 | | -provide the basis for full GraphQL implementations and tools. It is not a fully |
26 | | -standalone GraphQL server that a client developer could use to start |
27 | | -manipulating and querying data. Most importantly, it provides no mapping to a |
28 | | -functioning, production-ready backend. The only "backend" we have targeted for |
29 | | -this early preview are in-memory stubs in test cases. |
30 | | - |
31 | | -We are releasing this now because after GraphQL was first discussed publicly, |
32 | | -many engineers used this information to implement the parts of the system that |
33 | | -we discussed publicly. We want to support those engineers by providing both a |
34 | | -formal specification and a reference implementation for the system as a whole. |
35 | | - |
36 | | -To that end, the target audience is not the client developer, but those who have |
37 | | -built or are actively interested in building their own GraphQL implementations and |
38 | | -tools. Critically, we also want feedback on the system and to incorporate that |
39 | | -feedback in our final release. |
40 | | - |
41 | | -In order to be broadly adopted, GraphQL will have to target a wide |
42 | | -variety of backends, frameworks, and languages, which will necessitate a |
43 | | -collaborative effort across projects and organizations. This technical preview |
44 | | -marks the beginning of that process. |
45 | 16 |
|
46 | 17 | ## Getting Started |
47 | 18 |
|
|
0 commit comments