New: First commit

.editorconfig

@@ -0,0 +1,28 @@
+# http://EditorConfig.org
+
+# top-most EditorConfig file
+root = true
+
+# Default
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+indent_style = space
+indent_size = 4
+
+# Exceptions
+[*.yaml]
+indent_size = 2
+
+[*.js]
+max_line_length = 120
+
+[*.md]
+trim_trailing_whitespace = false
+max_line_length = 80
+indent_size = 2
+
+[Makefile]
+indent_style = tab

.gitattributes

@@ -0,0 +1,12 @@
+/.editorconfig export-ignore
+/.gitattributes export-ignore
+/.github export-ignore
+/.gitignore export-ignore
+/.nvmrc export-ignore
+/.prettierrc export-ignore
+/build.mjs export-ignore
+/CODE_OF_CONDUCT.md export-ignore
+/LICENSE export-ignore
+/Makefile
+/package.json export-ignore
+/pnpm-lock.yaml

.github/CONTRIBUTING.md

@@ -0,0 +1,35 @@
+# How to contribute
+
+I love to welcome your contributions. There are several ways to help out:
+
+- Create an [issue](../../../issues) on GitHub, if you have found a bug
+- Write test cases or provide examples for open bug issues
+- Write patches for open bug/feature issues, preferably with test cases included
+
+There are a few guidelines that I need contributors to follow so that I have a
+chance of keeping on top of things.
+
+## Getting Started
+
+- Make sure you have a [GitHub account](https://github.com/signup/free).
+- Submit an [issue](../../../issues), assuming one does not already exist.
+  - Clearly describe the issue including steps to reproduce when it is a bug.
+  - Make sure you fill in the earliest version that you know has the issue.
+- Fork the repository on GitHub.
+
+## Making Changes
+
+- Create a topic branch from where you want to base your work.
+  - This is usually the main branch.
+  - Only target release branches if you are certain your fix must be on that
+    branch.
+  - To quickly create a topic branch based on main; `git branch main/my_contribution main` then checkout the new branch with `git checkout main/my_contribution`. Better avoid working directly on the
+    `main` branch, to avoid conflicts if you pull in updates from origin.
+- Make commits of logical units.
+- Check for unnecessary whitespace with `git diff --check` before committing.
+- Use descriptive commit messages and reference the #issue number.
+
+## Submitting Changes
+
+- Push your changes to a topic branch in your fork of the repository.
+- Submit a pull request to the repository

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+github: jonnitto
+custom: https://www.paypal.me/Jonnitto/20eur

.github/ISSUE_TEMPLATE/Bug_report.yml

@@ -0,0 +1,57 @@
+name: 🐛 Bug report
+description: Create a report to help us improve
+labels:
+  - bug
+assignees: jonnitto
+body:
+  - type: markdown
+    attributes:
+      value: Thank you for taking the time to complete this bug report!
+  - type: markdown
+    attributes:
+      value: Please make sure to provide the information we ask for. This will allow us to help you better.
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: Describe the bug
+      description: A clear and concise description of the current behaviour.
+      placeholder: A bug happened!
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behaviour
+      description: A description of what you expect to happen.
+      placeholder: I expect to see X or Y
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Steps to reproduce
+      description: Please add a link to a repository with a minimal reproduction. Or describe accurately how we can reproduce/verify the bug.
+      placeholder: |
+        Example steps (replace with your own):
+        1. Clone my repo at https://github.com/<myuser>/example
+        2. pnpm build
+        3. You should see the error come up
+    validations:
+      required: true
+  - type: textarea
+    id: composerminfo
+    attributes:
+      label: PHP Package details
+      description: |
+        Please paste the output of running `composer info carbon/rangeeditor`.
+        This will be automatically formatted as a code block, so no need for backticks.
+      render: shell
+    validations:
+      required: true
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Anything else that might be relevant
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/Feature_request.yml

@@ -0,0 +1,47 @@
+name: ✨ Feature request
+description: Suggest an idea for this project
+labels:
+  - enhancement
+assignees: jonnitto
+body:
+  - type: markdown
+    attributes:
+      value: Thank you for taking the time to suggest a new feature!
+  - type: markdown
+    attributes:
+      value: Please describe the feature in detail. Why would it would be a good addition to Carbon.Pipeline?
+  - type: textarea
+    id: description
+    attributes:
+      label: What should be improved?
+      description: Is your feature request related to a problem? Please describe it.
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Describe the solution you would like
+      description: A clear and concise description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Possible alternatives
+      description: Describe any alternatives you have considered.
+    validations:
+      required: false
+  - type: textarea
+    id: extra
+    attributes:
+      label: Additional context
+      description: Add any other relevant information.
+    validations:
+      required: false
+  - type: checkboxes
+    id: can-work
+    attributes:
+      label: Are you willing to work on this?
+      description: Are you willing to help us add this feature? If you are not sure how, feel free to ask for guidance.
+      options:
+        - label: Yes, I would like to help

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: 🗣️ Ask question
+    url: https://github.com/CarbonPackages/Carbon.RangeEditor/discussions/category_choices
+    about: Please ask and answer questions in discussions

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,5 @@
+Describe the big picture of your changes here to communicate to the maintainers why I should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
+
+The best way to propose a feature is to open an issue first and discuss your ideas there before implementing them.
+
+Always follow the [contribution guidelines](.github/CONTRIBUTING.md) when submitting a pull request.

.github/release.yml

@@ -0,0 +1,20 @@
+changelog:
+  exclude:
+    labels:
+      - ignore-for-releasenotes
+  categories:
+    - title: 💥 Breaking changes
+      labels:
+        - breaking
+    - title: ✨ Exciting new features
+      labels:
+        - enhancement
+    - title: 🐛 Found and fixed bugs
+      labels:
+        - bug
+    - title: 📝 Added documentation
+      labels:
+        - documentation
+    - title: 🩹 Other changes
+      labels:
+        - "*"

.gitignore

@@ -0,0 +1,7 @@
+._*
+*.example
+.thumbs
+.idea
+.vscode
+.DS_Store
+node_modules

.nvmrc

@@ -0,0 +1 @@
+18

.prettierrc

@@ -0,0 +1,10 @@
+{
+  "overrides": [
+    {
+      "files": ["*.yaml", "*.yml"],
+      "options": {
+        "singleQuote": true
+      }
+    }
+  ]
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,52 @@
+# 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/

Configuration/Settings.yaml

@@ -0,0 +1,10 @@
+Neos:
+  Neos:
+    Ui:
+      resources:
+        javascript:
+          Carbon.RangeEditor:Plugin:
+            resource: resource://Carbon.RangeEditor/Public/Plugin.js
+        stylesheets:
+          Carbon.RangeEditor:Plugin:
+            resource: resource://Carbon.RangeEditor/Public/Plugin.css