Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

#781 Tweak - Change URL with new website URL #1151

Merged
merged 2 commits into from
Aug 24, 2023
Merged

#781 Tweak - Change URL with new website URL #1151

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5c4bd7d
Tweak - Old URL changed with new website URL
dipuchaudhary Aug 17, 2023
c627ef2
Resolve Merge conflict
deepench Aug 24, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
164 changes: 82 additions & 82 deletions .github/CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,82 +1,82 @@
# Contributing to Everest Forms ✨
There are many ways to contribute to the Everest Forms project!
- Translating strings into your language.
- Answering questions on GitHub and within the various Everest Forms communities.
- Submitting fixes, improvements, and enhancements.
Your help making Everest Forms even more awesome will be greatly appreciated :)
If you think something can be improved and you wish to contribute code,
[fork](https://help.github.com/articles/fork-a-repo/) Everest Forms, commit your changes,
and [send a pull request](https://help.github.com/articles/using-pull-requests/). We'll be happy to review your changes!
## Feature Requests
Feature requests can be [submitted to our issue tracker](https://github.com/wpeverest/everest-forms/issues/new?template=Feature_request.md). Be sure to include a description of the expected behavior and use case, and before submitting a request, please search for similar ones in the closed issues.
Feature request issues will remain closed until we see sufficient interest via comments and [👍 reactions](https://help.github.com/articles/about-discussions-in-issues-and-pull-requests/) from the community.
You can see a [list of current feature requests which require votes here](https://github.com/wpeverest/everest-forms/issues?q=label%3A%22votes+needed%22+label%3Aenhancement+sort%3Areactions-%2B1-desc+is%3Aclosed).
## Technical Support / Questions
We don't offer technical support on GitHub so we recommend using the following:
**Reading our documentation**
Usage docs can be found here: https://docs.wpeverest.com/docs/everest-forms/
If you have a problem, you may want to start with the self help guide here: https://docs.wpeverest.com/docs/everest-forms/self-service-guide/
**Technical support for premium addons or if you're a WPEverest.com customer**
from a human being - submit a ticket via the helpdesk
https://wpeverest.com/contact/
**General usage and development questions**
- WordPress.org Forums: https://wordpress.org/support/plugin/everest-forms
## Code of conduct
Everest Forms has adopted a Code of Conduct that we expect project participants to adhere to. Please read [the full text](.github/CODE_OF_CONDUCT.md) so that you can understand what actions will and will not be tolerated.
## Coding Guidelines
- **Ensure you stick to the [WordPress Coding Standards](https://make.wordpress.org/core/handbook/best-practices/coding-standards/php/)**
- Install our pre-commit hook using composer. It'll help with the Coding Standards. To install run `composer install` from the command line within the everest-forms plugin directory.
- Ensure you use LF line endings in your code editor. Use [EditorConfig](http://editorconfig.org/) if your editor supports it so that indentation, line endings and other settings are auto configured.
- When committing, reference your issue number (#1234) and include a note about the fix.
- Ensure that your code is compatible with PHP 5.4+.
- Push the changes to your fork and submit a pull request on the master branch of the Everest Forms repository. Existing maintenance branches will be maintained by Everest Forms developers.
Please **don't** modify the changelog or update the .pot files. These will be maintained by the Everest Forms team.
## Translating Everest Forms
We have a [project on translate.wordpress.org](https://translate.wordpress.org/projects/wp-plugins/everest-forms). You can join the localization team of your language and help by translating Everest Forms. [Find more about using joining a language team and using GlotPress](https://make.wordpress.org/polyglots/handbook/tools/glotpress-translate-wordpress-org/).
If Everest Forms is already 100% translated for your language, join the team anyway! We regularly update our language files and there will definitely be need of your help soon.
### Glossary & Style Guide
Please refer to this page on the [Translator Handbook](https://make.wordpress.org/polyglots/handbook/translating/glossary-style-guide/) for information about the glossary and the style guide.
We maintain the Everest Forms glossary [on this shared Google Sheet](https://docs.google.com/spreadsheets/d/1LlTmZLSuAyrJD_rHCsPY0ofCB1h1OT45SXFNU_a8ki8/edit?usp=sharing). You can use it as a template for creating your own glossary.
Please download the file by going to **File > Download as > Comma-separated values (.csv, current sheet)** and save it on your computer/Mac. Open it with your favourite CSV editor (or re-upload it on your own Google Drive) and edit it.
Make sure to edit the second column’s header by using your own language’s code (eg. for Italian you would use `it`, for Portuguese (Brazil) you would use `pt-BR`).
Write the translated entry in this column and translate the entry description as well.
Don’t change other columns headers and value, but feel free to add new entries.
When your CSV is ready, import it on GlotPress.
_**Warning**: Importing a CSV does not replace existing items, they will be created again. We suggest to import them only when first creating the glossary._
Each translation editor will take care of updating the glossary on GlotPress by editing/adding items when needed.
_**Note**: Only editors can create/import and edit glossaries and glossary items on GlotPress. Anyone can suggest new items to add to the glossary or translate them._
**Style Guides Available**
We don’t have a Style Guide template available, so feel free to create your own. If you created a style guide for your language, please let us know so we can add it in the list above. You can also add it by yourself by submitting a PR for this file.
# Contributing to Everest Forms ✨

There are many ways to contribute to the Everest Forms project!

- Translating strings into your language.
- Answering questions on GitHub and within the various Everest Forms communities.
- Submitting fixes, improvements, and enhancements.

Your help making Everest Forms even more awesome will be greatly appreciated :)

If you think something can be improved and you wish to contribute code,
[fork](https://help.github.com/articles/fork-a-repo/) Everest Forms, commit your changes,
and [send a pull request](https://help.github.com/articles/using-pull-requests/). We'll be happy to review your changes!

## Feature Requests

Feature requests can be [submitted to our issue tracker](https://github.com/wpeverest/everest-forms/issues/new?template=Feature_request.md). Be sure to include a description of the expected behavior and use case, and before submitting a request, please search for similar ones in the closed issues.

Feature request issues will remain closed until we see sufficient interest via comments and [👍 reactions](https://help.github.com/articles/about-discussions-in-issues-and-pull-requests/) from the community.

You can see a [list of current feature requests which require votes here](https://github.com/wpeverest/everest-forms/issues?q=label%3A%22votes+needed%22+label%3Aenhancement+sort%3Areactions-%2B1-desc+is%3Aclosed).

## Technical Support / Questions

We don't offer technical support on GitHub so we recommend using the following:

**Reading our documentation**
Usage docs can be found here: https://docs.everestforms.net/

If you have a problem, you may want to start with the self help guide here: https://docs.wpeverest.com/docs/everest-forms/self-service-guide/

**Technical support for premium addons or if you're a WPEverest.com customer**
from a human being - submit a ticket via the helpdesk
https://everestforms.net/contact/

**General usage and development questions**
- WordPress.org Forums: https://wordpress.org/support/plugin/everest-forms

## Code of conduct

Everest Forms has adopted a Code of Conduct that we expect project participants to adhere to. Please read [the full text](.github/CODE_OF_CONDUCT.md) so that you can understand what actions will and will not be tolerated.

## Coding Guidelines

- **Ensure you stick to the [WordPress Coding Standards](https://make.wordpress.org/core/handbook/best-practices/coding-standards/php/)**
- Install our pre-commit hook using composer. It'll help with the Coding Standards. To install run `composer install` from the command line within the everest-forms plugin directory.
- Ensure you use LF line endings in your code editor. Use [EditorConfig](http://editorconfig.org/) if your editor supports it so that indentation, line endings and other settings are auto configured.
- When committing, reference your issue number (#1234) and include a note about the fix.
- Ensure that your code is compatible with PHP 5.4+.
- Push the changes to your fork and submit a pull request on the master branch of the Everest Forms repository. Existing maintenance branches will be maintained by Everest Forms developers.

Please **don't** modify the changelog or update the .pot files. These will be maintained by the Everest Forms team.

## Translating Everest Forms

We have a [project on translate.wordpress.org](https://translate.wordpress.org/projects/wp-plugins/everest-forms). You can join the localization team of your language and help by translating Everest Forms. [Find more about using joining a language team and using GlotPress](https://make.wordpress.org/polyglots/handbook/tools/glotpress-translate-wordpress-org/).

If Everest Forms is already 100% translated for your language, join the team anyway! We regularly update our language files and there will definitely be need of your help soon.

### Glossary & Style Guide

Please refer to this page on the [Translator Handbook](https://make.wordpress.org/polyglots/handbook/translating/glossary-style-guide/) for information about the glossary and the style guide.

We maintain the Everest Forms glossary [on this shared Google Sheet](https://docs.google.com/spreadsheets/d/1LlTmZLSuAyrJD_rHCsPY0ofCB1h1OT45SXFNU_a8ki8/edit?usp=sharing). You can use it as a template for creating your own glossary.
Please download the file by going to **File > Download as > Comma-separated values (.csv, current sheet)** and save it on your computer/Mac. Open it with your favourite CSV editor (or re-upload it on your own Google Drive) and edit it.

Make sure to edit the second column’s header by using your own language’s code (eg. for Italian you would use `it`, for Portuguese (Brazil) you would use `pt-BR`).

Write the translated entry in this column and translate the entry description as well.
Don’t change other columns headers and value, but feel free to add new entries.

When your CSV is ready, import it on GlotPress.

_**Warning**: Importing a CSV does not replace existing items, they will be created again. We suggest to import them only when first creating the glossary._

Each translation editor will take care of updating the glossary on GlotPress by editing/adding items when needed.

_**Note**: Only editors can create/import and edit glossaries and glossary items on GlotPress. Anyone can suggest new items to add to the glossary or translate them._

**Style Guides Available**

We don’t have a Style Guide template available, so feel free to create your own. If you created a style guide for your language, please let us know so we can add it in the list above. You can also add it by yourself by submitting a PR for this file.
56 changes: 28 additions & 28 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,28 +1,28 @@
<p align="center"><a href="https://everestforms.net/"><img src=".github/logo.png" alt="Everest Forms"></a></p>
<p align="center">
<a href="https://renovateapp.com/"><img src="https://img.shields.io/badge/renovate-enabled-brightgreen.svg" alt="Renovate enabled"></a>
<a href="https://www.gnu.org/licenses/gpl-3.0.html"><img src="https://img.shields.io/badge/license-GPL--3.0%2B-orange.svg" alt="License"></a>
<a href="https://wordpress.org/plugins/everest-forms/"><img src="https://img.shields.io/wordpress/plugin/v/everest-forms.svg" alt="Latest Stable Version"></a>
<a href="https://wordpress.org/plugins/everest-forms/advanced/"><img src="https://img.shields.io/wordpress/plugin/dt/everest-forms.svg" alt="WordPress.org downloads"></a>
<a href="https://wordpress.org/support/plugin/everest-forms/reviews/"><img src="https://img.shields.io/wordpress/plugin/r/everest-forms.svg" alt="WordPress.org rating"></a>
<a href="https://wordpress.org/plugins/everest-forms/"><img src="https://img.shields.io/wordpress/plugin/tested/everest-forms.svg" alt="WordPress.org compatibility"></a>
</p>
Welcome to the Everest Forms repository on GitHub. Here you can browse the source, look at open issues and keep track of development. We recommend all developers to follow the [WPEverest blog](https://wpeverest.com/blog/) to stay up to date about everything happening in the project.
If you are not a developer, please use the [Everest Forms plugin page](https://wordpress.org/plugins/everest-forms/) on WordPress.org.
## Documentation
* [Everest Forms Documentation](https://docs.everestforms.net/docs/)
## Support
This repository is not suitable for support. Please don't use our issue tracker for support requests, but for core Everest Forms issues only. Support can take place through the appropriate channels:
* The [WPEverest free support portal](https://everestforms.net/support/) for customers who have purchased addon plans.
* [Our community forum on wp.org](https://wordpress.org/support/plugin/everest-forms) which is available for all Everest Forms users.
Support requests in issues on this repository will be closed on sight.
## Contributing to Everest Forms
If you have a patch or have stumbled upon an issue with Everest Forms core, you can contribute this back to the code. Please read our [contributor guidelines](.github/CONTRIBUTING.md) for more information how you can do this.
<p align="center"><a href="https://everestforms.net/"><img src=".github/logo.png" alt="Everest Forms"></a></p>

<p align="center">
<a href="https://renovateapp.com/"><img src="https://img.shields.io/badge/renovate-enabled-brightgreen.svg" alt="Renovate enabled"></a>
<a href="https://www.gnu.org/licenses/gpl-3.0.html"><img src="https://img.shields.io/badge/license-GPL--3.0%2B-orange.svg" alt="License"></a>
<a href="https://wordpress.org/plugins/everest-forms/"><img src="https://img.shields.io/wordpress/plugin/v/everest-forms.svg" alt="Latest Stable Version"></a>
<a href="https://wordpress.org/plugins/everest-forms/advanced/"><img src="https://img.shields.io/wordpress/plugin/dt/everest-forms.svg" alt="WordPress.org downloads"></a>
<a href="https://wordpress.org/support/plugin/everest-forms/reviews/"><img src="https://img.shields.io/wordpress/plugin/r/everest-forms.svg" alt="WordPress.org rating"></a>
<a href="https://wordpress.org/plugins/everest-forms/"><img src="https://img.shields.io/wordpress/plugin/tested/everest-forms.svg" alt="WordPress.org compatibility"></a>
</p>

Welcome to the Everest Forms repository on GitHub. Here you can browse the source, look at open issues and keep track of development. We recommend all developers to follow the [WPEverest blog](https://wpeverest.com/blog/) to stay up to date about everything happening in the project.

If you are not a developer, please use the [Everest Forms plugin page](https://wordpress.org/plugins/everest-forms/) on WordPress.org.

## Documentation
* [Everest Forms Documentation](https://docs.everestforms.net/docs/)

## Support
This repository is not suitable for support. Please don't use our issue tracker for support requests, but for core Everest Forms issues only. Support can take place through the appropriate channels:

* The [WPEverest free support portal](https://everestforms.net/support/) for customers who have purchased addon plans.
* [Our community forum on wp.org](https://wordpress.org/support/plugin/everest-forms) which is available for all Everest Forms users.

Support requests in issues on this repository will be closed on sight.

## Contributing to Everest Forms
If you have a patch or have stumbled upon an issue with Everest Forms core, you can contribute this back to the code. Please read our [contributor guidelines](.github/CONTRIBUTING.md) for more information how you can do this.
Loading
Loading