├── README.md ├── FUNDING.yml ├── .gitignore ├── .github ├── pull_request_template.md └── ISSUE_TEMPLATE │ ├── support_request.md │ ├── bug_report.md │ └── feature_request.md ├── SUPPORT.md ├── CONTRIBUTING.md ├── SECURITY.md └── CODE_OF_CONDUCT.md /README.md: -------------------------------------------------------------------------------- 1 | # .github -------------------------------------------------------------------------------- /FUNDING.yml: -------------------------------------------------------------------------------- 1 | github: [khalwat] 2 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | .DS_Store 2 | .idea 3 | -------------------------------------------------------------------------------- /.github/pull_request_template.md: -------------------------------------------------------------------------------- 1 | ### Description 2 | 3 | 4 | 5 | ### Related issues 6 | -------------------------------------------------------------------------------- /SUPPORT.md: -------------------------------------------------------------------------------- 1 | # Getting Support 2 | 3 | Creating a new GitHub Issue is the best way to start the support process. Include any applicable files, information, and screenshots. 4 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/support_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Support request 3 | about: Ask a question about this plugin. 4 | title: '' 5 | labels: question 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Question 11 | A question about the plugin or how it works. We are diligent about documentation so please check the plugin docs before submitting your question. 12 | 13 | ### Additional context 14 | Add any other context or screenshots about the support request here. 15 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a bug report for this plugin. 4 | title: '' 5 | labels: bug 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Describe the bug 11 | A clear and concise description of what the bug is. 12 | 13 | ### To reproduce 14 | Steps to reproduce the behaviour: 15 | 1. Go to "..." 16 | 2. Click on "..." 17 | 3. See error message "..." 18 | 19 | ### Expected behaviour 20 | A clear and concise description of what you expected to happen. 21 | 22 | ### Screenshots 23 | If applicable, add screenshots to help explain your problem. 24 | 25 | ### Versions 26 | - Plugin version: 27 | - Craft version: 28 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing 2 | 3 | When contributing to this repository, please first discuss the change you wish to make via issue, 4 | email, or any other method with the owners of this repository before making a change. 5 | 6 | Please note we have a code of conduct, please follow it in all your interactions with the project. 7 | 8 | ## Pull Request Process 9 | 10 | 1. Ensure any install or build dependencies are removed before the end of the layer when doing a 11 | build. 12 | 2. Update the `CHANGELOG.md` with details of changes to the project. 13 | 3. If applicable, update the `README.md` or associated documentation to cover the changes to the project. 14 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest a feature for this plugin. 4 | title: '' 5 | labels: enhancement 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Is your feature request related to a problem? Please describe. 11 | A clear and concise description of what the problem is. 12 | 13 | ### Describe the solution you would like 14 | A clear and concise description of what you would like to have happen. 15 | 16 | ### Describe alternatives you have considered 17 | A clear and concise description of any alternative solutions or features you have considered. 18 | 19 | ### Additional context 20 | Add any other context or screenshots about the feature request here. 21 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | ### Reporting vulnerabilities 2 | 3 | Please email reports about any security related issues you find to 4 | `info@nystudio107.com`. Your email will be acknowledged within one business day, and you'll receive a more detailed response to your email within 7 days indicating the next steps in handling your report. 5 | 6 | Please use a descriptive subject line for your report email. After the initial reply to your report, we will endeavor to keep you informed of the progress being made towards a fix and announcement. 7 | 8 | In addition, please include the following information along with your report: 9 | 10 | * Your name and affiliation (if any). 11 | * A description of the technical details of the vulnerabilities. It is very 12 | important to let us know how we can reproduce your findings. 13 | * An explanation who can exploit this vulnerability, and what they gain when 14 | doing so -- write an attack scenario. This will help us evaluate your report 15 | quickly, especially if the issue is complex. 16 | * Whether this vulnerability public or known to third parties. If it is, please 17 | provide details. 18 | 19 | If you believe that an existing (public) issue is security-related, please send 20 | an email to `info@nystudio107.com`. The email should include the issue ID and 21 | a short description of why it should be handled according to this security 22 | policy. 23 | 24 | Once an issue is reported, nystudio107 uses the following disclosure process: 25 | 26 | * When a report is received, we confirm the issue and determine its severity. 27 | * Wherever possible, fixes are prepared for the last minor release of the two 28 | latest major releases, as well as the master branch. We will attempt to 29 | commit these fixes as soon as possible, and as close together as 30 | possible. 31 | 32 | We credit reporters for identifying security issues, although we keep your name confidential if you request it. 33 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 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 info@nystudio107.com. 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 77 | --------------------------------------------------------------------------------