Golden is a copy of Carte project
it was what i was looking for.
The simplest API documentation template based on jekyll.
But it was not maintained for past 2 years.
So i just fork it & fixed a few things.
It' Jekyll god dammit:
- Clone this repository on your local,
- Install Jekyll,
- Go at the root of the repository and run
jekyll serve --watch
, - Go to http://localhost:4000,
- Great success! High five!
You can add a new API call by simply adding a new post in the _posts
folder. Jekyll by default forces you to specify a date in the file uri: it makes us sad pandas too, but you'll have to stick to this format. You can use dates to control the order in which API calls are displayed in the interface.
Each API call can define a few values in its YAML header:
Variable | Mandatory | Default | Description |
---|---|---|---|
title |
Y | - | A short description of what that calls does. |
path |
N | - | The URL for the API call, including potential parameters. |
type |
N | - | Set it to PUT , GET , POST , DELETE or nothing (for parts of your documentation that do not relate to an actual API call). |
A typical header:
---
uri: '/stuff/:id'
title: 'Delete a thing'
type: 'DELETE'
layout: null
---
We then describe the request and response (or whatever else you wish to talk about) in the body of our post. Check the placeholders present in the _posts
folder to get an idea of what it can look like.
Adding a category to your YAML header will allows you to group methods in the navigation. It is particularly helpful as you start having a lot of methods and need to organize them. For example:
---
category: Stuff
uri: '/stuff/:id'
title: 'Delete a thing'
type: 'DELETE'
layout: null
---
The default UI is mostly described through the css/style.css
file and a couple short jQuery scripts in the /_layouts/default.html
layout. Hack it to oblivion.