Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rollback file and add a link of Bahasa Indonesia translation
- Loading branch information
Wisnu Adi Nurcahyo
committed
Jun 15, 2017
1 parent
3e94a1a
commit aed87fe
Showing
3 changed files
with
210 additions
and
385 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,29 @@ | ||
# Berkontribusi | ||
# Contributing | ||
|
||
Proyek ini berkembang seiring dengan berkembangnya konten dari | ||
[_Functional Programming Jargon_](https://github.com/hemanth/functional-programming-jargon/) | ||
milik [hemanth](https://github.com/hemanth/). Maka dari itu sebaiknya Anda | ||
berkontribusi langsung ke _repository_ tersebut. Akan tetapi, kontribusi dalam | ||
bentuk apapun ke _repository_ ini sangat dipersilakan. | ||
This project is a work in progress. Contributions are very welcome. | ||
|
||
## Hard rules | ||
* Run `npm test` to lint the code examples. Your changes must pass. | ||
* If you add a new definition or reorder them run `npm run toc` to regenerate the table of contents. | ||
|
||
That said, we'd like to maintain some consistency across the document. | ||
|
||
## Style guide | ||
1. Every definition should include at least one JavaScript code example. | ||
1. Definitions should be written using the simplest language possible. Every word should tell. | ||
1. Target programmers that have no functional programming experience. | ||
1. We value understandability more than accuracy. e.g. It's okay to describe a functor as a container. | ||
1. Don't overuse jargon even if defined elsewhere in the document. | ||
1. Link to terms defined in the document when you use them in a definition. | ||
1. Avoid big walls of text | ||
|
||
## Code conventions | ||
[![JavaScript Style Guide](https://cdn.rawgit.com/feross/standard/master/badge.svg)](https://github.com/feross/standard) | ||
|
||
* Be consistent with other examples | ||
* Prefer arrow functions | ||
* Parenthesis around function arguments | ||
* Put output values in comments | ||
* Keep it short and simple | ||
|
||
This styleguide is a WIP too! Send PRs :) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.