Skip to content

Commit 586ec13

Browse files
pascalbe-humanizepascalbe-humanize
committed
Initial commit
0 parents  commit 586ec13

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

78 files changed

+20311
-0
lines changed

‎.dependabot/config.yml

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
version: 1
2+
3+
update_configs:
4+
- package_manager: javascript
5+
directory: /
6+
update_schedule: live
7+
allowed_updates:
8+
- match:
9+
update_type: security
10+
automerged_updates:
11+
- match:
12+
dependency_type: all
13+
update_type: in_range
14+
version_requirement_updates: widen_ranges

‎.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
---
11+
name: Bug report
12+
about: Create a report to help us improve
13+
---
14+
15+
<!-- Please don't delete this template because we'll close your issue -->
16+
<!-- Before creating an issue please make sure you are using the latest version of the starter. -->
17+
<!-- This project is starter project using Gatsby and NetlifyCMS in it, if you think the issue can originate from upstream then please report it-->
18+
# Bug report
19+
20+
<!-- Please ask questions on Spectrum for Gatsby questions or the Gitter channel for NetlifyCMS. -->
21+
<!-- https://spectrum.chat/?t=da07ec65-96f9-41be-baf0-0271b5b772ef -->
22+
<!-- https://gitter.im/netlify/NetlifyCMS -->
23+
<!-- Issues which contain questions or support requests will be closed. -->
24+
25+
**What is the current behavior?**
26+
27+
28+
**If the current behavior is a bug, please provide the steps to reproduce.**
29+
30+
31+
<!-- A great way to do this is to provide your configuration via a GitHub repository -->
32+
<!-- The most helpful is a minimal reproduction with instructions on how to reproduce -->
33+
<!-- Please only add small code snippets directly into this issue -->
34+
<!-- https://gist.github.com is a good place for longer code snippets -->
35+
<!-- If your issue is caused by a plugin or loader, please create an issue on the loader/plugin repository instead -->
36+
37+
**What is the expected behavior?**
38+
39+
40+
<!-- "It should work" is not a helpful explanation -->
41+
<!-- Explain exactly how it should behave -->
42+
43+
**Other relevant information:**
44+
45+
<!--Run `gatsby info --clipboard` in your project directory and paste the output here. Not working? You may need to update your global gatsby-cli - `npm install -g gatsby-cli` -->
46+
47+
Node.js version:
48+
NPM/Yarn version
49+
Operating System:
50+
Additional tools:

‎.github/ISSUE_TEMPLATE/custom.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
name: Custom issue template
3+
about: Describe this issue template's purpose here.
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
---
11+
name: Other
12+
about: Something else
13+
14+
---
15+
16+
<!-- Bug reports and Feature requests must use other templates, or will be closed -->
17+
<!-- Please ask questions on the NetlifyCMS Gitter channel (https://gitter.im/netlify/NetlifyCMS). -->
18+
<!-- Issues which contain questions or support requests will be closed. -->

‎.github/ISSUE_TEMPLATE/feature_request.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
---
11+
name: Feature request
12+
about: Suggest an idea for this project
13+
14+
---
15+
16+
<!-- Please don't delete this template or we'll close your issue -->
17+
18+
## Feature request
19+
20+
<!-- Issues which contain questions or support requests will be closed. -->
21+
<!-- Before creating an issue please make sure you are using the latest version of webpack. -->
22+
<!-- Check if this feature need to be implemented in a plugin or loader instead -->
23+
<!-- If yes: file the issue on the plugin/loader repo -->
24+
<!-- Features related to the development server should be filed on this repo instead -->
25+
26+
**What is the expected behavior?**
27+
28+
29+
**What is motivation or use case for adding/changing the behavior?**
30+
31+
32+
**How should this be implemented in your opinion?**
33+
34+
35+
**Are you willing to work on this yourself?**
36+
yes

‎.gitignore

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# Project dependencies
2+
# https://www.npmjs.org/doc/misc/npm-faq.html#should-i-check-my-node_modules-folder-into-git
3+
node_modules
4+
.cache/
5+
# Build directory
6+
public/
7+
static/admin/*.bundle.*
8+
.DS_Store
9+
yarn-error.log

‎CODE_OF_CONDUCT.md

Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
# Contributor Covenant 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, sex characteristics, gender identity and expression,
9+
level of experience, education, socio-economic status, nationality, personal
10+
appearance, race, religion, or sexual identity and 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 [email protected]. All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71+
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72+
73+
[homepage]: https://www.contributor-covenant.org
74+
75+
For answers to common questions about this code of conduct, see
76+
https://www.contributor-covenant.org/faq

‎CONTRIBUTING.md

Lines changed: 103 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,103 @@
1+
# CONTRIBUTING
2+
3+
Contributions are always welcome, no matter how large or small. Before contributing,
4+
please read the [code of conduct](CODE_OF_CONDUCT.md).
5+
6+
## Setup
7+
8+
> Install yarn on your system: [https://yarnpkg.com/en/docs/install](https://yarnpkg.com/en/docs/install)
9+
10+
### Install dependencies
11+
12+
> Only required on the first run, subsequent runs can use `yarn` to both
13+
bootstrap and run the development server using `yarn develop`.
14+
Since this starter using the [netlify-dev](https://www.netlify.com/products/dev/#how-it-works), there could be further issues you, please check the [netlify-dev](https://github.com/netlify/netlify-dev) repository for further information and set up questions.
15+
16+
```sh
17+
$ git clone https://github.com/netlify-templates/gatsby-starter-netlify-cms
18+
$ yarn
19+
```
20+
21+
## Available scripts
22+
23+
24+
### `build`
25+
26+
Build the static files into the `public` folder, turns lambda functions into a deployable form.
27+
28+
#### Usage
29+
30+
```sh
31+
$ yarn build
32+
```
33+
34+
### `clean`
35+
36+
Runs `gatsby clean` command.
37+
38+
#### Usage
39+
40+
```sh
41+
yarn clean
42+
```
43+
44+
### `netlify dev`
45+
46+
Starts the netlify dev environment, including the gatsby dev environment.
47+
For more infor check the [Netlify Dev Docs](https://github.com/netlify/cli/blob/master/docs/netlify-dev.md)
48+
49+
```sh
50+
netlify dev
51+
```
52+
53+
### `develop` or `start`
54+
55+
Runs the `clean` script and starts the gatsby develop server using the command `gatsby develop`. We recomend using this command when you don't need Netlify specific features
56+
57+
#### Usage
58+
59+
```sh
60+
yarn develop
61+
```
62+
### `test`
63+
64+
Not implmented yet
65+
66+
#### Usage
67+
68+
```sh
69+
yarn test
70+
```
71+
72+
### `format`
73+
74+
Formats code and docs according to our style guidelines using `prettier`
75+
76+
#### Usage
77+
78+
```sh
79+
yarn format
80+
```
81+
82+
83+
## Pull Requests
84+
85+
We actively welcome your pull requests!
86+
87+
If you need help with Git or our workflow, please ask on [Gitter.im](https://gitter.im/netlify/NetlifyCMS). We want your contributions even if you're just learning Git. Our maintainers are happy to help!
88+
89+
Netlify CMS uses the [Forking Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/forking-workflow) + [Feature Branches](https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow). Additionally, PR's should be [rebased](https://www.atlassian.com/git/tutorials/merging-vs-rebasing) on master when opened, and again before merging.
90+
91+
1. Fork the repo.
92+
2. Create a branch from `master`. If you're addressing a specific issue, prefix your branch name with the issue number.
93+
2. If you've added code that should be tested, add tests.
94+
3. If you've changed APIs, update the documentation.
95+
4. Run `yarn test` and ensure the test suite passes. (Not applicable yet)
96+
5. Use `yarn format` to format and lint your code.
97+
6. PR's must be rebased before merge (feel free to ask for help).
98+
7. PR should be reviewed by two maintainers prior to merging.
99+
100+
## License
101+
102+
By contributing to the Gatsby - Netlify CMS starter, you agree that your contributions will be licensed
103+
under its [MIT license](LICENSE).

‎LICENSE

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
The MIT License (MIT)
2+
3+
Copyright (c) 2015 gatsbyjs
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+

‎PULL_REQUEST_TEMPLATE.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
<!-- Thanks for submitting a pull request! Please provide enough information so that others can review your pull request. -->
2+
<!-- Explain the **motivation** for making this change. What existing problem does the pull request solve? -->
3+
<!-- Try to link to an open issue for more information. -->
4+
5+
6+
<!-- In addition to that please answer these questions: -->
7+
8+
**What kind of change does this PR introduce?**
9+
10+
<!-- E.g. a bugfix, feature, refactoring, build related change, etc… -->
11+
12+
**Does this PR introduce a breaking change?**
13+
14+
<!-- If this PR introduces a breaking change, please describe the impact and a migration path for existing applications. -->
15+
16+
**What needs to be documented once your changes are merged?**
17+
18+
<!-- List all the information that needs to be added to the documentation after merge -->
19+
<!-- When your changes are merged you will be asked to contribute this to the documentation -->

0 commit comments

Comments
 (0)