├── .env.example
├── .gitignore
├── .travis.yml
├── CODE_OF_CONDUCT.md
├── CONTRIBUTE.md
├── LICENSE
├── README.md
├── package-lock.json
├── package.json
├── public
├── favicon.ico
├── index.html
├── logo192.png
├── logo512.png
├── manifest.json
└── robots.txt
├── src
├── __tests__
│ ├── App.test.js
│ ├── CoderCard.test.js
│ └── DominicansWhoCodesList.test.js
├── components
│ ├── CoderCard.js
│ └── layout
│ │ ├── Footer.js
│ │ ├── Header.js
│ │ └── PageInfo.js
├── containers
│ ├── App.js
│ └── DominicansWhoCodesList.js
├── hooks
│ └── useDominicanCoders.js
├── index.js
├── sass
│ ├── base
│ │ ├── _base.scss
│ │ ├── _variables.scss
│ │ └── index.scss
│ ├── components
│ │ ├── _app.scss
│ │ ├── _dev.scss
│ │ └── index.scss
│ ├── helpers
│ │ ├── _animations.scss
│ │ └── index.scss
│ └── index.scss
├── setupTests.js
└── utils
│ ├── data.js
│ └── index.js
└── yarn.lock
/.env.example:
--------------------------------------------------------------------------------
1 | REACT_APP_API_URL=https://raw.githubusercontent.com/AngelGarcia13/DominicanWhoCodes/master/DominicanWhoCodes.Blazor/wwwroot/data/developers.json
2 | REACT_APP_ROOT_URL=https://raw.githubusercontent.com/AngelGarcia13/DominicanWhoCodes/master/DominicanWhoCodes.Blazor/wwwroot/
3 | REACT_APP_PROJECT_NAME="Dominicans Who Codes"
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
2 |
3 | # dependencies
4 | /node_modules
5 | /.pnp
6 | .pnp.js
7 |
8 | # testing
9 | /coverage
10 | */__tests__/__snapshots__
11 |
12 | # production
13 | /build
14 |
15 | # misc
16 | .DS_Store
17 | .env.local
18 | .env.development.local
19 | .env.test.local
20 | .env.production.local
21 |
22 | npm-debug.log*
23 | yarn-debug.log*
24 | yarn-error.log*
25 | .env
26 |
--------------------------------------------------------------------------------
/.travis.yml:
--------------------------------------------------------------------------------
1 | language: node_js
2 | node_js:
3 | - "stable"
4 | cache:
5 | directories:
6 | - node_modules
7 | install:
8 | - yarn install
9 | script:
10 | - yarn test
11 | - yarn build
12 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | In the interest of fostering an open and welcoming environment, we as
6 | contributors and maintainers pledge to making participation in our project and
7 | our community a harassment-free experience for everyone, regardless of age, body
8 | size, disability, ethnicity, gender identity and expression, level of experience,
9 | nationality, personal appearance, race, religion, or sexual identity and
10 | orientation.
11 |
12 | ## Our Standards
13 |
14 | Examples of behavior that contributes to creating a positive environment
15 | include:
16 |
17 | * Using welcoming and inclusive language
18 | * Being respectful of differing viewpoints and experiences
19 | * Gracefully accepting constructive criticism
20 | * Focusing on what is best for the community
21 | * Showing empathy towards other community members
22 |
23 | Examples of unacceptable behavior by participants include:
24 |
25 | * The use of sexualized language or imagery and unwelcome sexual attention or
26 | advances
27 | * Trolling, insulting/derogatory comments, and personal or political attacks
28 | * Public or private harassment
29 | * Publishing others' private information, such as a physical or electronic
30 | address, without explicit permission
31 | * Other conduct which could reasonably be considered inappropriate in a
32 | professional setting
33 |
34 | ## Our Responsibilities
35 |
36 | Project maintainers are responsible for clarifying the standards of acceptable
37 | behavior and are expected to take appropriate and fair corrective action in
38 | response to any instances of unacceptable behavior.
39 |
40 | Project maintainers have the right and responsibility to remove, edit, or
41 | reject comments, commits, code, wiki edits, issues, and other contributions
42 | that are not aligned to this Code of Conduct, or to ban temporarily or
43 | permanently any contributor for other behaviors that they deem inappropriate,
44 | threatening, offensive, or harmful.
45 |
46 | ## Scope
47 |
48 | This Code of Conduct applies both within project spaces and in public spaces
49 | when an individual is representing the project or its community. Examples of
50 | representing a project or community include using an official project e-mail
51 | address, posting via an official social media account, or acting as an appointed
52 | representative at an online or offline event. Representation of a project may be
53 | further defined and clarified by project maintainers.
54 |
55 | ## Enforcement
56 |
57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
58 | reported by contacting the project team at
59 | [React Dominicana - Whatsapp Group](https://chat.whatsapp.com/ErGzklqgz8Q1Wjj9BaJTvk). All
60 | complaints will be reviewed and investigated and will result in a response that
61 | is deemed necessary and appropriate to the circumstances. The project team is
62 | obligated to maintain confidentiality with regard to the reporter of an incident.
63 | Further details of specific enforcement policies may be posted separately.
64 |
65 | Project maintainers who do not follow or enforce the Code of Conduct in good
66 | faith may face temporary or permanent repercussions as determined by other
67 | members of the project's leadership.
68 |
69 | ## Attribution
70 |
71 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
72 | available at [http://contributor-covenant.org/version/1/4][version]
73 |
74 | [homepage]: http://contributor-covenant.org
75 | [version]: http://contributor-covenant.org/version/1/4/
--------------------------------------------------------------------------------
/CONTRIBUTE.md:
--------------------------------------------------------------------------------
1 | # Contributing
2 |
3 | 👍🎉 First off all, thanks for taking the time to contribute! 🎉👍
4 |
5 | When contributing to this repository, please first discuss the change you wish to make via issue,
6 | email, or any other method with the owners of this repository before making a change.
7 |
8 | Please note we have a code of conduct, please follow it in all your interactions with the project.
9 |
10 | ## How can I Contribute?
11 |
12 | ### Reporting Bugs
13 |
14 | Bugs are tracker as [GitHub issues](https://github.com/React-Dominicana/dominicans-who-code-react/issues).
15 | Explain the problem and include additional details to help maintainers reproduce the proble:
16 |
17 | - **Use a clear and descriptive title** for the issue to identify the problem.
18 | - **Describe the exact steps which reproduce the problem** in as many details as possible.
19 | For example, start by explaining how you started the project, e.g. which command exactly you used
20 | in the terminal, or how you started the project otherwise.
21 | - **Provide specific examples to demonstrate the steps**. Include links to files, or copy/paste snippets,
22 | which you use in those examples. If you're providing snippets in the issue, use [Markdown code blocks](https://help.github.com/en/articles/getting-started-with-writing-and-formatting-on-github#multiple-lines).
23 | - **Describe the behavior you observed after following the steps** and point out what exactly is the problem with that behavior.
24 | - **Explain which behavior you expected** to see instead and why.
25 | - **Include screenshots and animated GIFs** which show you following the described steps and clearly demonstrate the problem.
26 |
27 | ### Suggesting Enhancements
28 |
29 | Before creating enhancement suggestions, please check this
30 | [list](https://github.com/React-Dominicana/dominicans-who-code-react/issues?q=is%3Aopen+is%3Aissue+label%3Aenhancement)
31 | as you might find out that you don't need to create one. When you are creating an enhancement suggestion,
32 | please include as many details as possible.
33 |
34 | - **Use a clear and descriptive title** for the issue to indentify the suggestion.
35 | - **Provide a step-by-step description of the suggested enhancement** in as many details as possible.
36 | - **Provide specific examples to demonstrate the steps**. Include copy/pasteable snippets which you use
37 | in those examples, as [Markdown code blocks](https://help.github.com/en/articles/getting-started-with-writing-and-formatting-on-github#multiple-lines).
38 | - **Describe the current behavior** and explain which behavior you expected to see instead and why.
39 | - **Include screenshots and animated GIFs** which help you demonstrate the steps or point out the part
40 | of Atom which the suggestion is related to.
41 |
42 | ### Pull Request Process
43 |
44 | 1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
45 | 2. Update the README.md with details of changes to the interface, this includes new environment variables,
46 | exposed ports, useful file locations and container parameters.
47 | 3. After you submit your Pull Request, verify that all
48 | [status checks](https://help.github.com/en/articles/about-status-checks) are passing.
49 | 4. You may merge the Pull Request in once you have the sign-off of at least of one developer, or
50 | if you do not have permission to do that, you may request the reviewer to merge it for you.
51 |
52 | ## Styleguides
53 |
54 | ### Git Commit Messages
55 |
56 | - Use the present tense ("Add feature" not "Added feature")
57 | - Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
58 | - Limit the first line to 72 characters or less
59 | - Reference issues and pull requests liberally after the first line
60 | - When only changing documentation, include [ci skip] in the commit title
61 | - Consider starting the commit message with an applicable emoji:
62 | - 🎨 :art: when improving the format/structure of the code
63 | - 🐎 :racehorse: when improving performance
64 | - 🚱 :non-potable_water: when plugging memory leaks
65 | - 📝 :memo: when writing docs
66 | - 🐧 :penguin: when fixing something on Linux
67 | - 🍎 :apple: when fixing something on macOS
68 | - 🏁 :checkered_flag: when fixing something on Windows
69 | - 🐛 :bug: when fixing a bug
70 | - 🔥 :fire: when removing code or files
71 | - 💚 :green_heart: when fixing the CI build
72 | - ✅ :white_check_mark: when adding tests
73 | - 🔒 :lock: when dealing with security
74 | - ⬆️ :arrow_up: when upgrading dependencies
75 | - ⬇️ :arrow_down: when downgrading dependencies
76 | - 👕 :shirt: when removing linter warnings
77 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2020 React Dominicana
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # DominicanWhoCodes - React
2 |
3 | Open source project inspired in [IndiansWhoDesign](http://indianswhodesign.in), made to expose all the developers from the Dominican Republic with their skills and contacts.
4 |
5 | ### Prerequisites
6 |
7 | - Node
8 | - Yarn
9 |
10 | ### Installation
11 |
12 | #### Yarn
13 |
14 | ```
15 | yarn install
16 | ```
17 |
18 | ### Development
19 |
20 | > *NOTE*: rename the `.env.example` to `.env`.
21 |
22 | #### Yarn
23 |
24 | ```
25 | yarn start
26 | ```
27 |
28 | ### Tests
29 |
30 | #### Yarn
31 |
32 | To run the tests.
33 |
34 | ```
35 | yarn test
36 | ```
37 |
38 | To run the tests with `watch`.
39 |
40 | ```
41 | yarn test:watch
42 | ```
43 |
44 | To run the tests with `watch` and `coverage`.
45 |
46 | ```
47 | yarn test:coverage
48 | ```
49 |
50 | ### Deployment
51 |
52 | Automatically deployed into [Netlify](https://www.netlify.com/) when the `master` branch is updated.
53 |
54 | ### Acknowledgments
55 |
56 | - [DominicanWhoCodes](https://github.com/AngelGarcia13/DominicanWhoCodes)
57 | - [IndiansWhoDesign](http://indianswhodesign.in)
58 |
59 | ### License
60 |
61 | This project uses the following license: [MIT]()
62 |
63 |