Document `compile*` api and format readme

[tunnckoCore]

It not includes *client* methods, cuz i dont know exactly what's the idea behind them. Also normalize render* documentation.

[ForbesLindesay]

@tunnckoCore

It's uglier. It's logical enough that it is method, because it is in the fucking API section.

I want to make this perfectly clear, as this is not the first time I've reached out to you about this:

• This organisation does not tolerate swearing in any form. For example, "fucking" is never an appropriate word to use in this projects issue tracker, documentation, source code or commits. The words you use when you are talking to friends in private are entirely up to you but, in this community, such language will not be tolerated.
• This organisation will not tolerate you (or anyone else) treating other people's opinions as stupid or insignificant. If you receive feedback on a pull request or issue that you disagree with, you should start by understanding that they are probably just as smart as you, and probably have very good reasons for disagreeing with you. If you are willing to try and understand their point of view, and calmly explain your point of view, then you can have reasonable discourse. This will be far more productive and is far more likely to your pull requests ultimately being accepted.

For the time being, I have removed you from the owners group on GitHub and npm. You are still more than welcome to fork projects and submit pull requests. If you continue to contribute to the project, and show more respect to the other people working on this, you may be re-added to the owners group. If you continue to abuse the patience of other members of this organisation, you will be banned.

[tunnckoCore]

I want to make this perfectly clear, as this is not the first time I've reached out to you about this:

Yea, second. And yea, you are right, i'm agree. I just have my ups and downs.

But I also want to point that only I and @RobLoach doing something on that Org everyday and week, and of course you for the initial and stable job on the jstransformer/jstransformer. No one joins on the discussions, PRs and issues. You and @TimothyGu comes one time in month or two, put 2 comments somewhere and that's it. And okey, that's why we are team - that is the idea of teams, anyone to help and join when he can. But @hemanth and @stoeffel does nothing. @stoeffel did the logo and that's great, I'm (we are) appreciated, but nothing more.

We can't do anything if we waiting someone that comes one time in year and the project moves nowhere. We can't do everything alone. Actually we can, we did it successfully to now and if we was waiting someone (which would be normal, because we are "team") this org would be with 30 repos, not with 130+ repos. We put a lot of work here.

But don't understand me wrong, I don't sue you for your decisions (who to join, who to left, or whatever). But @jstransformers is what is now, because of us, not because of the team, or because @hemanth or because @stoeffel.

We can't do anything, and this project won't move somewhere if you (and others) just coming to comment some semicolon or period in the sea of code (in the sea of transformers) - and all that to be just against the others.

Usually, I'm creating some transformer as side work, usually in the night or in the morning with cup of coffee for relaxing. I can't help if i should waiting you or some other of the "active" members of the org to come in december and say me "oo no, no, i dont like this semicolon" or something.

Removing me from the org - okey, but not from the npm. I can't agree with that.