summaryrefslogtreecommitdiff
path: root/build/html/_sources/introduction.rst.txt
diff options
context:
space:
mode:
authorKen <kenny@madgloryint.com>2017-11-01 13:27:17 -0400
committerKen <kenny@madgloryint.com>2017-11-01 13:27:17 -0400
commit1385a3cefc7312a3f18e8d78a854411b53c75e67 (patch)
treef27292fc20215f68c25ab09830947da56fb732a9 /build/html/_sources/introduction.rst.txt
parent0f19a09673be2bb79426e21a6460d5095f43287a (diff)
downloadvainglory-docs-1385a3cefc7312a3f18e8d78a854411b53c75e67.tar.gz
vainglory-docs-1385a3cefc7312a3f18e8d78a854411b53c75e67.zip
Initial commit of the new logs.
Diffstat (limited to 'build/html/_sources/introduction.rst.txt')
-rw-r--r--build/html/_sources/introduction.rst.txt23
1 files changed, 23 insertions, 0 deletions
diff --git a/build/html/_sources/introduction.rst.txt b/build/html/_sources/introduction.rst.txt
new file mode 100644
index 0000000..b8904cc
--- /dev/null
+++ b/build/html/_sources/introduction.rst.txt
@@ -0,0 +1,23 @@
+Introduction
+============
+
+The first version of the Vainglory Game Data Service is an exciting step forward towards making it easier for users to have open access to in-game data.
+
+Build something great!
+
+At the moment this Service is in Alpha Preview mode. You can see sample data, test the interface, and provide feedback to our development team.
+
+While we initially took a different approach, based on community feedback the Server now makes every attempt to implement the required features of the `JSON-API <http://jsonapi.org/>`_. specification.
+
+We show example language bindings using CURL and plan to add libraries for Ruby, NodeJS, Java, Python and more. Community contributions are welcome and rewarded with good karma (and swag!) You can view code examples in the dark area to the right, and you can switch the programming language of the examples with the tabs in the top right.
+
+
+Versioning
+---------------------------
+
+We following `SEMVER <http://semver.org/>`_. standards, using a MAJOR.MINOR.PATCH versioning scheme. This means that we will increment versioning in the following way:
+
+MAJOR version when we make incompatible API changes,
+MINOR version when we add functionality in a backwards-compatible manner,
+PATCH version when we make backwards-compatible bug fixes.
+You can see the current version and deploy date by viewing the Status endpoint.