GitBook: [2.0.0] 151 pages modified

Author: jonasjabari

docs/README.md

@@ -659,7 +659,7 @@ We reworked the form components quite a bit:
 * options passed as hashes in to `form_select`, `form_radio` and `form_checkbox` are now expected to be { label\_value: input\_value } and thus the other way around. Until 0.7.6 it was { input\_value: label\_value }
 * and added a lot of new features, such as customizing the error rendering.
 
-We invested a lot of time to improve the `form` API docs found [here](docs/api/100-components/form.md).
+We invested a lot of time to improve the `form` API docs found [here](wip/docs/api/100-components/form.md).
 
 * [ ] Please make sure to read through the docs and migrate your forms accordingly!
 

docs/SUMMARY.md

@@ -0,0 +1,2 @@
+# .github
+

docs/changelog.md

@@ -0,0 +1,10 @@
+# issue\_template
+
+**What is the current behavior?**
+
+**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug might get fixed faster if we can run your code and it doesn't have extra dependencies. Add a link to a sample repo and/or any relevant code below:**
+
+**What is the expected behavior?**
+
+**Which versions of Matestack, and which browser/OS are affected by this issue? Did this work in previous versions of Matestack?**
+

docs/wip/.github/README.md

@@ -0,0 +1,14 @@
+# pull\_request\_template
+
+**Note:** If you submit a feature or bugfix PR, pick **develop** as target branch \(and delete this line afterwards\).
+
+## Issue [https://github.com/matestack/matestack-ui-core/issues/XXX](https://github.com/matestack/matestack-ui-core/issues/XXX): Short description here
+
+### Changes
+
+* [ ] Describe the changes in one or more bulletpoints
+
+### Notes
+
+* Let the reviewers know something special
+

docs/wip/.github/issue_template.md

@@ -0,0 +1,54 @@
+# 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, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, 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 pascal@matestack.io. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and 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](https://www.contributor-covenant.org), version 1.4, available at [https://www.contributor-covenant.org/version/1/4/code-of-conduct.html](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html)
+
+For answers to common questions about this code of conduct, see [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq)
+

docs/wip/.github/pull_request_template.md

@@ -0,0 +1,2 @@
+# docs
+

docs/wip/code_of_conduct.md

@@ -0,0 +1,6 @@
+# Core Components
+
+Matestack provides you with a wide set of core components that enable you to easily build your UI.
+
+Please use the sidebar to navigate to the component documentations.
+

docs/wip/docs/README.md

@@ -0,0 +1,48 @@
+# Matestack Core Component: Abbr
+
+The HTML `<abbr>` tag, implemented in Ruby.
+
+## Parameters
+
+This component expects 1 required param and various optional configuration params and can either yield content or display what gets passed to the `text` configuration param.
+
+### Title - required
+
+Expects a string with the meaning of the abbreviation contained within the tag.
+
+### Text \(optional\)
+
+Expects a string which will be displayed as the content inside the `<abbr>` tag. If this is not passed, a block must be passed instead.
+
+### HMTL attributes \(optional\)
+
+This component accepts all the canonical [HTML global attributes](https://www.w3schools.com/tags/ref_standardattributes.asp) like `id` or `class`.
+
+## Examples
+
+### Example 1 - render options\[:text\] param
+
+```ruby
+abbr title: 'Hypertext Markup Language', text: 'HTML'
+```
+
+returns
+
+```markup
+<abbr title="Hypertext Markup Language">HTML</abbr>
+```
+
+### Example 2 - yield a given block
+
+```ruby
+abbr title: 'Cascading Style Sheets' do
+  span text: 'CSS'
+end
+```
+
+returns
+
+```markup
+<abbr title="Cascading Style Sheets"><span>CSS</span></abbr>
+```
+