Merge pull request GrapesJS#1 from artf/dev

fork

.editorconfig

@@ -0,0 +1,10 @@
+root = true
+
+[*]
+end_of_line = lf
+insert_final_newline = true
+
+[*.js]
+charset = utf-8
+indent_style = space
+indent_size = 2

.eslintrc

@@ -0,0 +1,19 @@
+{
+  "env": {
+    "browser": true,
+    "node": true
+  },
+  "parserOptions": {
+    "sourceType": "module",
+    "ecmaFeatures": {
+      "experimentalObjectRestSpread": true
+    }
+  },
+  "rules": {
+    "strict": 0,
+    "quotes": [0, "single"],
+    "eol-last": [0],
+    "no-mixed-requires": [0],
+    "no-underscore-dangle": [0]
+  }
+}

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,26 @@
+## WARNING
+READ and FOLLOW next 5 steps, then REMOVE them before posting the issue
+
+1. Follow CONTRIBUTING Guidelines https://github.com/artf/grapesjs/blob/master/CONTRIBUTING.md
+2. Use the GitHub Issues EXCLUSIVELY for BUGS, FEATURE REQUESTS or QUESTIONS. Prefix the title of the issue with its context, eg. `[Bug]: ....`
+3. Do a quick SEARCH first, to see if someone else didn't open the same issue
+4. DON'T ASK to create examples/code for you, read DOCS and APIs first, then you can post what you have tried (we'd like to see your code) and what you're unable to achieve
+5. All relative statements/questions have to be filled/answered, otherwise, the issue might be CLOSED
+
+## You're submitting a BUG
+  1. Are you using the latest release (older versions are NOT supported)?
+      1. If you're not sure, type `grapesjs.version` in console and press ENTER
+  1. Are you facing the bug with your local copy of GrapesJS or with the current demo?
+  1. If a local copy
+      1. Indicate all informations about your OS, browser and GrapesJS version.
+      1. Are you able to reproduce the bug from the demo?
+  1. What is the expected behavior?
+  1. What happens instead?
+  1. If you're able to reproduce the bug indicate all the necessary steps
+  1. Attach screenshots (using KAP/LICEcap), screencasts or live demo
+     1. JSFiddle Starter template https://jsfiddle.net/szLp8h4n
+     1. CodeSandbox Starter template https://codesandbox.io/s/1r0w2pk1vl
+
+## You're submitting a FEATURE REQUEST
+  1. Be sure to work on the latest version, as the feature might be already there
+  1. Keep in mind that the feature should be considered valid to use for everyone, not only for your case

.github/no-response.yml

@@ -0,0 +1,13 @@
+# Configuration for probot-no-response - https://github.com/probot/no-response
+
+# Number of days of inactivity before an Issue is closed for lack of response
+daysUntilClose: 10
+# Label requiring a response
+responseRequiredLabel: more-information-needed
+# Comment to post when closing an Issue for lack of response. Set to `false` to disable
+closeComment: >
+  This issue has been automatically closed because there has been no response
+  to our request for more information from the original author. With only the
+  information that is currently in the issue, we don't have enough information
+  to take action. Please reach out if you have or find the answers we need so
+  that we can investigate further.

.gitignore

@@ -2,15 +2,20 @@
 .settings/
 .sass-cache/
 .project
-.eslintrc
-npm-debug.log
+.idea
+npm-debug.log*
+yarn-error.log
+yarn.lock
 style/.sass-cache/
+stats.json
 
 img/
 images/
 private/
-docs/
 vendor/
 coverage/
 node_modules/
 bower_components/
+grapesjs-*.tgz
+_index.html
+docs/.vuepress/dist

.travis.yml

@@ -1,5 +1,3 @@
 language: node_js
 node_js:
-  - "5.6"
-before_script:
-  - npm run build
+  - "7.6"

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,52 @@
+# Contribute
+
+## Introduction
+
+First of all, thank you for considering contributing to GrapesJS!
+
+We welcome any type of contribution, not only code. Like for example:
+- **QA**: file bug reports, the more details you can give the better (e.g. screenshots with the console open)
+- **Marketing**: writing blog posts, howto's, tutorials, etc.
+- **Community**: presenting the project at meetups, organizing a dedicated meetup for the local community, etc.
+- **Money**: We welcome financial contributions in full transparency on our [Open Collective].
+
+
+## Your First Contribution
+
+Working on your first Pull Request? You can learn how from this **free** series, [How to Contribute to an Open Source Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github).
+
+
+## Submitting code
+
+Any code change should be submitted as a pull request. Before start working on something make always a search in opened issues and pull requests, this might help you to avoid waisting time.
+
+A pull request could be a bug fix, new feature and much more, but in all cases, **open a new issue** and talk about what you want to do. Often happens to work on something already fixed (ready to release) or in progress.
+
+The title should be brief but comprehensive, the description contains a link to the opened issue and the proposed solution. The pull request should contain tests whenever possible. Keep in mind that the bigger is the pull request, the longer it will take to review and merge. Try to break down large pull requests in smaller chunks that are easier to review and merge.
+
+
+## Styleguide
+
+The code is auto formatted with [prettier](https://github.com/prettier/prettier) on any commit, therefore you can write in any style you prefer
+
+
+## Expenses
+
+Anyone can file an expense (code, marketing, etc.) via our [Open Collective]. If the expense makes sense for the development of the community, it will be "merged" in the ledger of our open collective by the core contributors and the person who filed the expense will be reimbursed.
+
+Before submitting an expense contact core contributors via the current active chat room ([Discord](https://discord.gg/QAbgGXq)) and explain your intents
+
+
+## Questions
+
+If you have any questions, create an [issue](https://github.com/artf/grapesjs/issues) (protip: do a quick search first to see if someone else didn't ask the same question before!).
+
+
+
+## Credits
+
+Thank you to all the people who have already contributed to GrapesJS!
+<a href="/artf/grapesjs/graphs/contributors"><img src="https://opencollective.com/grapesjs/contributors.svg?width=890" /></a>
+
+
+[Open Collective]: <https://opencollective.com/grapesjs>