All Projects → IIIF → Api

IIIF / Api

Source for API and model specifications documents (api and model)

Projects that are alternatives of or similar to Api

Graphql Voyager
🛰️ Represent any GraphQL API as an interactive graph
Stars: ✭ 6,481 (+7436.05%)
Mutual labels:  api-documentation
Pandora Apidoc
pandora.com API documentation
Stars: ✭ 46 (-46.51%)
Mutual labels:  api-documentation
Rest Client
A tool for automated testing REST API, generating exquisite testing report and REST API documentation.
Stars: ✭ 1,181 (+1273.26%)
Mutual labels:  api-documentation
Platform Documentation
Core Platform API Documentation & Tutorials
Stars: ✭ 25 (-70.93%)
Mutual labels:  api-documentation
Slate
Beautiful static documentation for your API
Stars: ✭ 33,447 (+38791.86%)
Mutual labels:  api-documentation
Molten Boilerplate
A boilerplate for the molten framework by Bogdanp https://github.com/Bogdanp/molten
Stars: ✭ 50 (-41.86%)
Mutual labels:  api-documentation
Pdoc
🐍 ➡️ 📜 Auto-generate API documentation for Python projects
Stars: ✭ 604 (+602.33%)
Mutual labels:  api-documentation
Openapi Viewer
Browse and test a REST API described with the OpenAPI 3.0 Specification
Stars: ✭ 82 (-4.65%)
Mutual labels:  api-documentation
Whatpulse
WhatPulse reverse engineered
Stars: ✭ 30 (-65.12%)
Mutual labels:  api-documentation
Spring Boot Webflux Swagger Starter
An example project to illustrate how to document Spring Boot Webflux with Swagger2
Stars: ✭ 62 (-27.91%)
Mutual labels:  api-documentation
Api Docs
API documentation for Kolonial.no
Stars: ✭ 26 (-69.77%)
Mutual labels:  api-documentation
Chn Eolinker Ams Lite 4.0 For Php
中国最大的在线API管理平台EOLINKER 旗下API管理系统开源精简版,适合个人以及微型团队使用。
Stars: ✭ 869 (+910.47%)
Mutual labels:  api-documentation
Rest Layer
REST Layer, Go (golang) REST API framework
Stars: ✭ 1,068 (+1141.86%)
Mutual labels:  api-documentation
Nei Toolkit
NEI 接口文档管理平台配套自动化工具
Stars: ✭ 781 (+808.14%)
Mutual labels:  api-documentation
Zeal
Offline documentation browser inspired by Dash
Stars: ✭ 9,164 (+10555.81%)
Mutual labels:  api-documentation
Devdocs
API Documentation Browser
Stars: ✭ 27,208 (+31537.21%)
Mutual labels:  api-documentation
Mvp Template
Template for a minimum viable API developer portal, based in Jekyll
Stars: ✭ 48 (-44.19%)
Mutual labels:  api-documentation
Drf Autodocs
Ultimately automated DRF documentation rendering(UNMAINTAINED)
Stars: ✭ 82 (-4.65%)
Mutual labels:  api-documentation
Jsdoc To Markdown
Generate markdown documentation from jsdoc-annotated javascript
Stars: ✭ 1,199 (+1294.19%)
Mutual labels:  api-documentation
Ember Api Docs
Ember API Docs viewer
Stars: ✭ 55 (-36.05%)
Mutual labels:  api-documentation

Build Status

Specifications

Markdown Source of specifications documents

To Debug the Site

  1. bundle install

  2. Run rake dev to compile the site and run a dev server on http://localhost:4000.

To Run the Tests

  1. bundle install
  2. Install grunt npm install -g grunt-cli
  3. Install grunt dependencies npm install
  4. Run rake ci

To Publish the Site to iiif.io

Branches are available at http://preview.iiif.io/api/[branch_name]/api/index.html. The master branch is automatically loaded to the iiif.io website.

Some Things to Note

  • Much of the site data is in the YAML files in _data/ (e.g. member institutions, server impls, demos, etc.) make edits there.
  • The latest versions of the APIs are set in _config.yml. Change there will get pushed to .htaccess, technical-details/, and any other links.
  • The website is now split with the specification website living here and the main website living in IIIF/website. Links internal and external should be in the following forms:
    • Internal relative link inside the API website [hyperlink text]({{ site.url }}{{ site.baseurl }}/end/point)
    • link from the API website to the main website (not relative to this repo) [hyperlink text]({{ page.webprefix }}/end/point)
    • External link [anchor-text](http://example.com/end/point)
    • Reference link [text][link_name] where link_name is expanded at the bottom of the page.
  • If this branch has a domain name associated with it e.g. prezi3.iiif.io then add the name of the branch to the ROOT_BRANCHES variable in the .travis.yml. Note branch names are sperated by a space.

Contributions

Participation in the IIIF community is welcome in all forms, from any individual or organization. Please see the community page for more details about how to join in discussions.

Contributions to the text of the specifications and the content of the website are welcome in the form of pull requests, or by comments with proposed text on issues. By making such a contribution, the contributor asserts that they have the right to license the contribution such that content may be published under the CC-BY license by the IIIF Consortium, per the license statement on all documents.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].