Can I suggest API Blueprint [1]? It is much more human friendly and easier to work on API design. Apiary has tools for complete API lifecycle management.

Disclaimer: I work on making API Blueprint better.

[1]: https://apiblueprint.org

This is such a cool move from google. Doing material design in HTML/CSS/JS is pure win.

I am working on React.js components for this. I have already did half of them. Check out https://github.com/pksunkara/react-mdl. I welcome any contributions.

EDIT: Components can be seen at https://github.com/pksunkara/react-mdl/tree/master/src

Thankyou. Until I saw your comment, I had no idea this came from Google. The domain is http://www.getmdl.io/, the site doesn't mention it, and a "lite" version sounds unofficial. The only clue is the Github icon links to https://github.com/google/material-design-lite link.

I also started the same thing a few weeks ago but I chose a different approach. I decided to use their `upgradeElement` function to upgrade the component, instead of re-writing everything. https://github.com/tleunen/react-mdl

> I am working on React.js components for this.

Can you just use polymer though?

You can but I didn't like it and wanted to use react.js

you can use both together if you don't care about server side rendering.

Apiary (http://apiary.io) - FULL TIME - San Fransisco, CA or Prague, Czech Republic

TECHNOLOGY: Node.js, Backbone, Coffeescript

Visit https://apiary.io/company#jobs for more details on the jobs.

==========================================

Fullstack Developer (Core Application Team)

===========================================

As a member of the Application team, you are going to be responsible for crafting, delivering and maintaining the main apiary.io application (including the Apiary for Teams feature set).

In this vertical team, you are going to collaborate with your fellow team members on providing the best tooling and platform for designing, developing, and maintaining APIs worldwide.

Building great APIs is all about effective collaboration, be the one building the tools (teams, managing a team, user roles, access control, ...).

You'll be developing one of the most-used API Documentation worldwide. Documentation including interactive Console, documentation that has to run smoothly on mobile and touch-based devices, has to support plenty of customization options, and on top of that has to be super fast.

Don't forget about Mock Server and Debugging Proxy. Mock Server is all about speed and pairing responses defined in an API blueprint (choosing what response is the best fit). Debugging Proxy is a tough one. (...). Don't leave out payments (trials, subscriptions, ...).

You'll be responsible for the most visible part of our product suite that defines how Apiary is perceived.

You can try using API Blueprint (https://apiblueprint.org) which is based on Markdown can host your API docs at http://apiary.io

Disclaimer: I work at Apiary

For our corporate API, we the Apiary markdown with aglio to convert into nice documentation. I've tried RAML (I didn't like the giant YAML file) and apidoc (I didn't like to put 100 lines of user documentation next to 20 lines of implementation). I use protagonist to convert the md file to JSON which my Python code can load and compare with the decorated API endpoints -- I can then verify they and all their parameters are properly documented. I don't use the fancy Apiary features yet.

Better golang package management.

Better erlang package management? (:

Disclaimer: I work for Apiary.

API Blueprint [1] is an open source API description format which can be used to intuitively describe an API.

MSON [2] is a recent addition to the above format which makes it easy to describe all kinds of complex requests and responses in the spec.

You can email me at pavan [at] apiary [dot] io if you have any more questions.

[1]: http://apiblueprint.org

[2]: http://github.com/apiaryio/mson

Currently Reading:

Good Strategy, Bad Strategy https://www.goodreads.com/book/show/11721966-good-strategy-b...

I think https://github.com/pksunkara/alpaca is a good starting point. Given a web API, it generates client libraries in ruby, python, php and node.js

Are there any other alternatives to alpaca? How is the quality of the generate client code?

No, as far as I know, alpaca is the first of its type. As the author of the code, I can guarantee good quality of the generated client code. I have written the templates such that they follow their respective language conventions and ecosystems.

God and Luck both doesn't exist.