Create an API-reference website

[quicksketch]

We should create an API website matching api.drupal.org, leveraging the API module to index our fork of the code.

Unlike Drupal's API website, I'd like to see the API website be the conical location for all API documentation, including:

• Doctrine-based documentation (api.module).
• The topic-based documentation (https://drupal.org/developing/api)
• API change log (https://drupal.org/list-changes?to_branch=8.x)

So rather than being a read-only site, the API website actually is actually where documentation for Backdrop is created and stored.

I've already made an issue specifically for changelogs here: #14

[matt2000]

Setting up an api module site is easy enough; I've done it before. Do you want it hosted on your infrastructure? Otherwise, I can put it on a server of my own and you can just point the sub-domain at my IP.

[quicksketch]

@matt2000, that would be great if you're interested in setting it up! I'd like to keep our servers in a single place for management purposes. I'll get a box ready for you. You already have my e-mail, could you send me your public key? I'll add it to the utility server and we can set the API site up there.

[quicksketch]

OK! @matt2000 I've set up a new repository and domain for you:

Repository: https://github.com/backdrop/api.backdropcms.org
Site: http://api.backdropcms.org/

You can connect to the box via:
ssh [email protected]

The web directory is already set up, MySQL credentials are in a file called "matt-MYSQL_LOGIN_INFORMATION.txt" ;)

Ideally, you'll push the code up into the Github repository, and make a clone of the repository on the server so we can update the site using Git.

[jenlampton]

Since we now have an API site with it's own issue queue (https://github.com/backdrop/api.backdropcms.org/issues) I'm going to close this issue.