docs: some thoughts

[ajoslin]

The point of this is to spark a discussion about making simpler defaults for this project.

These wording changes assume that we make angular the default and rename it to standard or something similar.

Why should there be an opinionated default? Because this project's current defaults just give you a formatted and sorted version of git log, which isn't very helpful.

Why should angular be the default? Because angular's conventions make the most sense and are easy for people to adopt (if we document them well).

Why rename the angular presets to standard? Because lots of people in the npm community hate AngularJS. But whether you like angular or not, the conventions are worth using.

I don't intend this to be merged yet.

[ajoslin]

There are two options named transform. I deleted one, but I'm not really sure what's up there.

[stevemao]

Yeah they do different things (bad name). The one under pkg is to tweak the parsed package.json a bit. It is used by conventional-github-releaser where you need to prepend a leading 'v' in version.

[stevemao]

The reason I didn't make angular as default are:

1. I don't want to be opinionated.
2. Like you said some people "hate" angular's conventions (hate is probably not accurate).
3. I checked a lot of other projects' conventions and I think they work nicely too. For example: jQuery's convention is also used widely and there are certain nice things about it.

I don't mind making angular as standard. I suggest that we should make it a vote? While this PR addresses other issues too so I'll open another one.

[stevemao]

In the docs, I think it's good if we ask user to alias the command. and put the changelog script in package.json.

[ajoslin]

Nice. The new README is a huge step in the right direction.

[stevemao]

Thanks for the suggestion @ajoslin :)