Skip to content

Commit 16588bd

Browse files
committed
Remove sections from 1.x docs
who's using, other resources and license sections from intro
1 parent 5b73b9c commit 16588bd

File tree

1 file changed

+4
-47
lines changed

1 file changed

+4
-47
lines changed

docs/asciidoc/introduction.asciidoc

Lines changed: 4 additions & 47 deletions
Original file line numberDiff line numberDiff line change
@@ -5,58 +5,15 @@
55
[[introduction]]
66
== Introduction
77

8-
You've reached the documentation page for `Elasticsearch.Net` and `NEST`. The two official .NET clients for Elasticsearch. So why two clients I hear you say?
8+
You've reached the documentation page for `Elasticsearch.Net` and `NEST`. The two official .NET clients for Elasticsearch.
9+
10+
=== Why two clients?
911

1012
`Elasticsearch.Net` is a very low level, dependency free, client that has no opinions about how you build and represent your requests and responses. It has abstracted
1113
enough so that **all** the Elasticsearch API endpoints are represented as methods but not too much to get in the way of how you want to build your json/request/response objects. It also comes with builtin, configurable/overridable, cluster failover retry mechanisms. Elasticsearch is elastic so why not your client?
1214

1315
`NEST` is a high level client that has the advantage of having mapped all the request and response objects, comes with a strongly typed query DSL that maps 1 to 1 with the Elasticsearch query DSL, and takes advantage of specific .NET features such as covariant results. NEST internally uses, and still exposes, the low level `Elasticsearch.Net` client.
1416

15-
Please read the getting started guide for both.
16-
17-
=== Who's using Nest
18-
19-
* {stackoverflow}[stackoverflow.com] (and the rest of the stackexchange family).
20-
21-
* http://www.7digital.com[7digital.com] (run NEST on mono).
22-
23-
* https://www.rijksmuseum.nl/en[rijksmuseum.nl] (Elasticsearch is the only datastorage hit for each page).
24-
25-
* http://www.fogcreek.com/kiln/[Kiln] FogCreek's version control & code review tooling.
26-
They are so pleased with Elasticsearch that http://blog.fogcreek.com/kiln-powered-by-elasticsearch/[they made a video about how pleased they are!]
27-
28-
=== Other resources
29-
30-
http://twitter.com/joelabrahamsson[@joelabrahamsson] wrote a great http://joelabrahamsson.com/entry/extending-aspnet-mvc-music-store-with-elasticsearch[intro into elasticsearch on .NET]
31-
using NEST.
32-
33-
Also checkout the https://searchbox.io/[searchbox.io guys] rocking NEST http://blog.appharbor.com/2012/06/19/searchbox-elasticsearch-is-now-an-add-on[on AppHarbor]
34-
with their https://github.com/searchbox-io/.net-sample[demo project]
35-
36-
=== Questions, bugs, comments, requests
37-
38-
All of these are more then welcome on the {github}/issues[github issues pages]! We try to at least reply within the same day.
39-
40-
We also monitor question tagged with {stackoverflow}/questions/tagged/nest['nest' on stackoverflow] or
41-
{stackoverflow}/questions/tagged/elasticsearch-net['elasticsearch-net' on stackoverflow], as well as https://discuss.elastic.co[discussions on our discourse site]
42-
43-
=== License
44-
45-
....
46-
This software is licensed under the Apache 2 license, quoted below.
47-
48-
Copyright (c) 2014 Elasticsearch <http://www.elasticsearch.org>
49-
50-
Licensed under the Apache License, Version 2.0 (the "License");
51-
you may not use this file except in compliance with the License.
52-
You may obtain a copy of the License at
53-
54-
http://www.apache.org/licenses/LICENSE-2.0
17+
Please read the getting started guide for both <<elasticsearch-net-quick-start, Elasticsearch.Net>> and <<nest-quick-start, NEST>>.
5518

56-
Unless required by applicable law or agreed to in writing, software
57-
distributed under the License is distributed on an "AS IS" BASIS,
58-
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
59-
See the License for the specific language governing permissions and
60-
limitations under the License.
61-
....
6219

0 commit comments

Comments
 (0)