|
1 | | -<p align="center"> |
2 | | - <img src="https://raw.githubusercontent.com/lord/img/master/logo-slate.png" alt="Slate: API Documentation Generator" width="226"> |
3 | | - <br> |
4 | | - <a href="https://travis-ci.org/lord/slate"><img src="https://travis-ci.org/lord/slate.svg?branch=master" alt="Build Status"></a> |
5 | | -</p> |
6 | | - |
7 | | -<p align="center">Slate helps you create beautiful, intelligent, responsive API documentation.</p> |
8 | | - |
9 | | -<p align="center"><img src="https://raw.githubusercontent.com/lord/img/master/screenshot-slate.png" width=700 alt="Screenshot of Example Documentation created with Slate"></p> |
10 | | - |
11 | | -<p align="center"><em>The example above was created with Slate. Check it out at <a href="https://lord.github.io/slate">lord.github.io/slate</a>.</em></p> |
12 | | - |
13 | | -Features |
14 | | ------------- |
15 | | - |
16 | | -* **Clean, intuitive design** — With Slate, the description of your API is on the left side of your documentation, and all the code examples are on the right side. Inspired by [Stripe's](https://stripe.com/docs/api) and [PayPal's](https://developer.paypal.com/webapps/developer/docs/api/) API docs. Slate is responsive, so it looks great on tablets, phones, and even in print. |
17 | | - |
18 | | -* **Everything on a single page** — Gone are the days when your users had to search through a million pages to find what they wanted. Slate puts the entire documentation on a single page. We haven't sacrificed linkability, though. As you scroll, your browser's hash will update to the nearest header, so linking to a particular point in the documentation is still natural and easy. |
19 | | - |
20 | | -* **Slate is just Markdown** — When you write docs with Slate, you're just writing Markdown, which makes it simple to edit and understand. Everything is written in Markdown — even the code samples are just Markdown code blocks. |
21 | | - |
22 | | -* **Write code samples in multiple languages** — If your API has bindings in multiple programming languages, you can easily put in tabs to switch between them. In your document, you'll distinguish different languages by specifying the language name at the top of each code block, just like with GitHub Flavored Markdown. |
23 | | - |
24 | | -* **Out-of-the-box syntax highlighting** for [over 100 languages](https://github.com/jneen/rouge/wiki/List-of-supported-languages-and-lexers), no configuration required. |
25 | | - |
26 | | -* **Automatic, smoothly scrolling table of contents** on the far left of the page. As you scroll, it displays your current position in the document. It's fast, too. We're using Slate at TripIt to build documentation for our new API, where our table of contents has over 180 entries. We've made sure that the performance remains excellent, even for larger documents. |
27 | | - |
28 | | -* **Let your users update your documentation for you** — By default, your Slate-generated documentation is hosted in a public GitHub repository. Not only does this mean you get free hosting for your docs with GitHub Pages, but it also makes it simple for other developers to make pull requests to your docs if they find typos or other problems. Of course, if you don't want to use GitHub, you're also welcome to host your docs elsewhere. |
29 | | - |
30 | | -* **RTL Support** Full right-to-left layout for RTL languages such as Arabic, Persian (Farsi), Hebrew etc. |
31 | | - |
32 | | -Getting started with Slate is super easy! Simply fork this repository and follow the instructions below. Or, if you'd like to check out what Slate is capable of, take a look at the [sample docs](http://lord.github.io/slate). |
33 | | - |
34 | | -Getting Started with Slate |
35 | | ------------------------------- |
36 | | - |
37 | | -### Prerequisites |
38 | | - |
39 | | -You're going to need: |
40 | | - |
41 | | - - **Linux or macOS** — Windows may work, but is unsupported. |
42 | | - - **Ruby, version 2.3.1 or newer** |
43 | | - - **Bundler** — If Ruby is already installed, but the `bundle` command doesn't work, just run `gem install bundler` in a terminal. |
44 | | - |
45 | | -### Getting Set Up |
46 | | - |
47 | | -1. Fork this repository on GitHub. |
48 | | -2. Clone *your forked repository* (not our original one) to your hard drive with `git clone https://github.com/YOURUSERNAME/slate.git` |
49 | | -3. `cd slate` |
50 | | -4. Initialize and start Slate. You can either do this locally, or with Vagrant: |
51 | | - |
52 | | -```shell |
53 | | -# either run this to run locally |
54 | | -bundle install |
55 | | -bundle exec middleman server |
56 | | - |
57 | | -# OR run this to run with vagrant |
58 | | -vagrant up |
59 | | -``` |
60 | | - |
61 | | -You can now see the docs at http://localhost:4567. Whoa! That was fast! |
62 | | - |
63 | | -Now that Slate is all set up on your machine, you'll probably want to learn more about [editing Slate markdown](https://github.com/lord/slate/wiki/Markdown-Syntax), or [how to publish your docs](https://github.com/lord/slate/wiki/Deploying-Slate). |
64 | | - |
65 | | -If you'd prefer to use Docker, instructions are available [in the wiki](https://github.com/lord/slate/wiki/Docker). |
66 | | - |
67 | | -### Note on JavaScript Runtime |
68 | | - |
69 | | -For those who don't have JavaScript runtime or are experiencing JavaScript runtime issues with ExecJS, it is recommended to add the [rubyracer gem](https://github.com/cowboyd/therubyracer) to your gemfile and run `bundle` again. |
70 | | - |
71 | | -Companies Using Slate |
72 | | ---------------------------------- |
73 | | - |
74 | | -* [NASA](https://api.nasa.gov) |
75 | | -* [Sony](http://developers.cimediacloud.com) |
76 | | -* [Best Buy](https://bestbuyapis.github.io/api-documentation/) |
77 | | -* [Travis-CI](https://docs.travis-ci.com/api/) |
78 | | -* [Greenhouse](https://developers.greenhouse.io/harvest.html) |
79 | | -* [Woocommerce](http://woocommerce.github.io/woocommerce-rest-api-docs/) |
80 | | -* [Dwolla](https://docs.dwolla.com/) |
81 | | -* [Clearbit](https://clearbit.com/docs) |
82 | | -* [Coinbase](https://developers.coinbase.com/api) |
83 | | -* [Parrot Drones](http://developer.parrot.com/docs/bebop/) |
84 | | -* [Scale](https://docs.scaleapi.com/) |
85 | | - |
86 | | -You can view more in [the list on the wiki](https://github.com/lord/slate/wiki/Slate-in-the-Wild). |
87 | | - |
88 | | -Questions? Need Help? Found a bug? |
89 | | --------------------- |
90 | | - |
91 | | -If you've got questions about setup, deploying, special feature implementation in your fork, or just want to chat with the developer, please feel free to [start a thread in our Spectrum community](https://spectrum.chat/slate)! |
92 | | - |
93 | | -Found a bug with upstream Slate? Go ahead and [submit an issue](https://github.com/lord/slate/issues). And, of course, feel free to submit pull requests with bug fixes or changes to the `dev` branch. |
94 | | - |
95 | | -Contributors |
96 | | --------------------- |
97 | | - |
98 | | -Slate was built by [Robert Lord](https://lord.io) while interning at [TripIt](https://www.tripit.com/). |
99 | | - |
100 | | -Thanks to the following people who have submitted major pull requests: |
101 | | - |
102 | | -- [@chrissrogers](https://github.com/chrissrogers) |
103 | | -- [@bootstraponline](https://github.com/bootstraponline) |
104 | | -- [@realityking](https://github.com/realityking) |
105 | | -- [@cvkef](https://github.com/cvkef) |
106 | | - |
107 | | -Also, thanks to [Sauce Labs](http://saucelabs.com) for sponsoring the development of the responsive styles. |
108 | | - |
109 | | -Special Thanks |
110 | | --------------------- |
111 | | -- [Middleman](https://github.com/middleman/middleman) |
112 | | -- [jquery.tocify.js](https://github.com/gfranko/jquery.tocify.js) |
113 | | -- [middleman-syntax](https://github.com/middleman/middleman-syntax) |
114 | | -- [middleman-gh-pages](https://github.com/edgecase/middleman-gh-pages) |
115 | | -- [Font Awesome](http://fortawesome.github.io/Font-Awesome/) |
| 1 | +# Maps4News API Documentation |
0 commit comments