|
1 | 1 | # GraphQL
|
2 | 2 |
|
3 |
| -This is a Working Draft of the Specification for GraphQL, a query language |
4 |
| -created by Facebook for describing data requirements on complex application |
5 |
| -data models. |
| 3 | +This is a Working Draft of the Specification for GraphQL, a query language for APIs created by Facebook. |
6 | 4 |
|
7 |
| -[Slack](https://graphql-slack.herokuapp.com/) |
8 |
| -[#graphql on Reactiflux](http://www.reactiflux.com/) |
9 |
| - |
10 |
| -## Technical Preview Contents |
11 |
| - |
12 |
| -This technical preview contains a draft specification for GraphQL and a reference |
13 |
| -implementation in JavaScript that implements that draft, |
14 |
| -[GraphQL.js](https://github.com/graphql/graphql-js). |
15 |
| - |
16 |
| -The reference implementation provides base libraries in JavaScript that would |
17 |
| -provide the basis for full GraphQL implementations and tools. It is not a fully |
18 |
| -standalone GraphQL server that a client developer could use to start |
19 |
| -manipulating and querying data. Most importantly it provides no mapping to a |
20 |
| -functioning, production-ready backend. The only “backend” that we have targeted for |
21 |
| -this early preview, are in-memory stubs in test cases. |
22 |
| - |
23 |
| -We are releasing this now, because after GraphQL was first discussed publicly, |
24 |
| -many engineers used this information to implement the parts of the system that |
25 |
| -we discussed publicly. We want to support those engineers by providing both a |
26 |
| -formal specification and a reference implementation for the system as a whole. |
27 |
| - |
28 |
| -To that end the target audience is not the client developer, but those who have, |
| 5 | +The target audience for this specification is not the client developer, but those who have, |
29 | 6 | or are actively interested in, building their own GraphQL implementations and
|
30 |
| -tools. Critically we also want feedback on the system and to incorporate that |
31 |
| -feedback in our final release. |
| 7 | +tools. |
32 | 8 |
|
33 | 9 | In order to be broadly adopted, GraphQL will have to target a wide
|
34 | 10 | variety of backends, frameworks, and languages, which will necessitate a
|
35 |
| -collaborative effort across projects and organizations. This technical preview |
36 |
| -marks the beginning of that process. |
| 11 | +collaborative effort across projects and organizations. This specification serves as a point of coordination for this effort. |
| 12 | + |
| 13 | +[Slack](https://graphql-slack.herokuapp.com/) |
| 14 | +[#graphql on Reactiflux](http://www.reactiflux.com/) |
37 | 15 |
|
38 | 16 | ## Getting Started
|
39 | 17 |
|
|
0 commit comments