2.6 Release

.github/ISSUE_TEMPLATE/Bug_report.md

@@ -0,0 +1,30 @@
+---
+name: 🐛 Bug Report
+about: When something isn't working correctly
+
+---
+
+# Bug Report
+
+<!--
+Title Format
+  [Scope] Summary of what is broken
+-->
+
+## Steps to reproduce
+1.
+2.
+3.
+
+## Expected result
+
+## Actual result
+
+## Testcase
+<!-- Fork https://jsfiddle.net/31d6y7mn -->
+
+## Screenshot (when possible)
+![]()
+
+## Version
+x.x.x

.github/ISSUE_TEMPLATE/Feature_request.md

@@ -0,0 +1,18 @@
+---
+name: 🚀 Feature Request
+about: Suggest a new feature
+
+---
+
+# Feature Request
+
+## Description
+Explain what you want in great detail
+
+## Example
+
+## Testcase (when possible)
+<!-- Fork https://jsfiddle.net/31d6y7mn -->
+
+## Screenshot (when possible)
+![]()

.github/ISSUE_TEMPLATE/Help_wanted.md

@@ -0,0 +1,9 @@
+---
+name: 📓 Support Question
+about: If you have a question or need a helping hand
+---
+
+# Help Wanted
+
+## Problem
+Describe your problem in great detail

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,22 +1,15 @@
-✖ Multiple features in one PR
-✖ New Components Unless Previously Discussed with Maintainers (Consider creating separate repo, I'll link out to you)
+<!--
+  Please read the contibuting guide before you submit a pull request
+  https://github.com/fomantic/Fomantic-UI/blob/master/CONTRIBUTING.md
+-->
 
-✔ Add comments to complex/confusing code in "code" view of PR
-✔ BUGS → This form is required:
-✔ Enhancements → Only specific enhancements with detailed descriptions.
+## Description
 
-### Issue Titles
+## Testcase
+<!-- Fork https://jsfiddle.net/31d6y7mn -->
 
-Use the format: [Component] Adds Support for Thing
+## Screenshot (when possible)
+![]()
 
-For example: [Build Tools] Adds Source Map Support
-Or: [Button] Fixes Inheritance for Red Basic Active State
-
-### Closed Issues
+## Closes
 #222 #333 #444
-
-### Description
-
-### Testcase
-[Fork, update, and replace to show the bug]:
-https://jsfiddle.net/ca0rovs3/

CONTRIBUTING.md

@@ -1,58 +1,47 @@
-# Contributing to Semantic UI
+# Contributing to Fomantic-UI
 
-### Usage Questions
+### :notebook: Support Questions
 
-Questions about usage should be asked in our [Discord](https://discordapp.com/invite/YChxjJ3) or [StackOverflow](http://stackoverflow.com/questions/tagged/semantic-ui).
+Questions regarding usage and support can be asked in [GitHub Issues](https://github.com/fomantic/Fomantic-UI/issues) but if your question starts to become a conversation we will ask you to move it into our [Discord](https://discordapp.com/invite/YChxjJ3). If you are looking for quick support [Discord](https://discordapp.com/invite/YChxjJ3) is the best place to ask.
 
-Examples of usage questions
-* *Why isnt my code working?*
-* *Can Semantic UI do this?*
+After asking your question you may find that it is actually a bug or the feature you wanting doesn't exist. At this point it's a good idea to submit a GitHub issue (if you haven't already) to request/report your issue.
 
-Once you receive feedback through community channels you may find your question is actually a bug. At this point it's a good idea to submit it as a bug report. Just keep in mind the following suggestions.
+### Bugs & Enhancements
 
-### Creating Bug Reports
+#### :bug: Reporting Bugs
 
-[Github Issues Tracker](https://github.com/fomantic/Fomantic-UI/issues) is used to track all upcoming milestones and changes to the project.
+We use [GitHub Issues](https://github.com/fomantic/Fomantic-UI/issues) to track all bugs and enhancements for FUI, before raising a bug please check to see if it has already been raised. If you find it has already been raised add a :thumbsup: to the issue reactions to show you are also having the same issue. Please do not spam "+1", "bump" etc.
 
-**Please create a fork of this [JSFiddle](https://jsfiddle.net/31d6y7mn) to demonstrate bugs.**
+If you find that your issue has not already been raised please create a [new issue](https://github.com/fomantic/Fomantic-UI/issues/new?template=Bug_report.md) please follow and fill in the template provided this helps us gather the correct information we need to triage issues.
 
-When submiting a bug report, include a set of steps to reproduce the issue and any related information, browser, OS etc. If we can't reproduce the issue then it will make solving things much more difficult.
+When creating an issue you will be asked to create a [JSFiddle](https://jsfiddle.net/31d6y7mn) to replicate your issue. You can fork [this template](https://jsfiddle.net/31d6y7mn) which has the latest version of Fomantic ready to use.
 
-If your bug uses a third party framework like Ember, Meteor, or Angular. Be sure to submit the issue to their respective issues boards. If you are confident the bug is part of the 'vanilla' SUI release, keep in mind not all maintainers are familiar with all framework and a simple test case is greatly appreciated.
+#### :crystal_ball: Requesting Features
 
-If your bug is reproduced by a maintainer it will be assigned the [`confirmed bug`](https://github.com/fomantic/Fomantic-UI/issues?q=is%3Aopen+is%3Aissue+label%3A%22Confirmed+Bug%22) tag. Browsing this tag is a good way to keep track of known issues with SUI.
+We also use [GitHub Issues](https://github.com/fomantic/Fomantic-UI/issues) for new feature requests. Before submitting a new issue please check to see if it has already been requested. If you find that your issue has not already been requested feel free create a [new issue](https://github.com/fomantic/Fomantic-UI/issues/new?template=Feature_request.md) please follow and fill in the template provided this helps us gather the correct information we need to triage issues.
 
-#### Naming Issues
+When you create the issue please when possible include pictures or a [JSFiddle](https://jsfiddle.net/31d6y7mn), this can help contributors understand what your asking.
 
-Semantic UI boards use a special naming convention to help tag issue titles by the component the issue is related to.
+##### Naming Issues
 
-##### Bugs
-Please tag titles in the format "[Component] *Sub-type* should do *correct behavior*". Please use standard [title case](http://www.titlecase.com) for titles, including the bracketed tag.
+When you create an issue please follow our naming convention this makes it easy to scan over issues.
 
-For example
-* [Dropdown] Multiple Selection Should Preserve "Set Selected" Order
-* [Validation] - E-mail Validation Should Handle Cyrillic
-* [Button] - Grouped Buttons Should Display Correctly on Mobile
+**Bugs:** [Scope] x does not do y
+**Enhancements:** [Scope] x should do y
 
-##### Enhancements
+The scope is the component which has the issue or enhancement e.g. Segment, Grid, Dropdown etc. when you describe the issue in the summary keep it brief 60 characters max.
 
-For new feature requests, you can use the format "[Component] Add *new feature*"
-
-For example
-* [Dropdown] Add "Clearable" Setting
-* [Validation] Add Rules for Zipcode Validation
-* [API] Add "onProgress" callback setting
-
-
-### Tracking Issue Progress
+##### Tracking Issue Progress
 
 As bugs and features are triaged they will be assigned to milestones. The best indication of when a change will land is to check the date on the  [upcoming milestones](https://github.com/fomantic/Fomantic-UI/milestones) page.
 
-### Creating Pull Requests
+### :pencil: Pull Requests Guide
 
 **All pull requests should be merged into the `beta` branch.**
 
-Anyone can jump on the issues board and grab off bugs to fix. This is probably the best way to become a contributor to Semantic. Be sure to adhere to the style guides when submitting code.
+Anyone can jump on the issues board and grab off bugs to fix. This is probably the best way to become a contributor to Fomantic. We only ask you to stick to these few rules to make it easier to merge/process your pull requests.
 
-* [Create a Pull Request](https://github.com/fomantic/Fomantic-UI/compare)
-* [View Open Issues](https://github.com/fomantic/Fomantic-UI/issues)
+- When you implement a new feature or fix a bug think about backwards compatibility. If your change is backwards compatible it is most likely to be merged sooner since you won't need to wait for a breaking change update.
+- Please commit using the [AngularJS Git Commit Message Convention](https://gist.github.com/stephenparish/9941e89d80e2bc58a153) this is more of a nice to have and isn't required.
+- Please try and stick to a similar code style so everyone can read your code.
+- When you commit don't include your dist files, this add changes when your create your PR which aren't needed.

README.md

@@ -1,44 +1,33 @@
-![Semantic](http://fomantic-ui.com/images/logo.png#128)
 
-# Fomantic UI
+<p align="center">
+  <img src="http://fomantic-ui.com/images/logo.png#128">
+</p>
+<h1 align="center">Fomantic UI</h1>
+<h4 align="center">A community fork of the popular Semantic-UI framework</h4>
 
-
-[![Discord](https://img.shields.io/discord/453127116427493376.svg?label=Discord)](https://discord.gg/YChxjJ3)
-[![npm downloads](https://img.shields.io/npm/dw/fomantic-ui.svg)](https://www.npmjs.com/package/fomantic-ui)
-[![npm version](https://img.shields.io/npm/v/fomantic-ui.svg)](https://www.npmjs.com/package/fomantic-ui)
-[![last commit](https://img.shields.io/github/last-commit/hammy2899/fomantic-ui.svg)](https://github.com/fomantic/Fomantic-UI/commits/master)
-
-[Fomantic](http://fomantic-ui.com) is a community fork of the popular Semantic-UI framework.
+<p align="center">
+  <a href="https://discord.gg/YChxjJ3"><img src="https://img.shields.io/discord/453127116427493376.svg?label=Discord"></a>
+  <a href="https://www.npmjs.com/package/fomantic-ui"><img src="https://img.shields.io/npm/dw/fomantic-ui.svg"></a>
+  <a href="https://www.npmjs.com/package/fomantic-ui"><img src="https://img.shields.io/npm/v/fomantic-ui.svg"></a>
+  <a href="https://github.com/fomantic/Fomantic-UI/commits/master"><img src="https://img.shields.io/github/last-commit/hammy2899/fomantic-ui.svg"></a>
+</p>
 
 *NOTE:* Fomantic was created to continue active development of Semantic-UI and has the intent to be merged back into the master repository once active development can restart. For more info please read the following issues https://github.com/Semantic-Org/Semantic-UI/issues/6109 https://github.com/Semantic-Org/Semantic-UI/issues/6413
 
-Key Features
-* 50+ UI elements
-* 3000 + CSS variables
-* 3 Levels of variable inheritance (similar to SublimeText)
-* Built with EM values for responsive design
-* Flexbox friendly
-
-Semantic allows developers to build beautiful websites fast, with **concise HTML**, **intuitive javascript**, and **simplified debugging**, helping make front-end development a delightful experience. Semantic is responsively designed allowing your website to scale on multiple devices. Semantic is production ready and partnered with frameworks such as **React**, **Angular**, **Meteor**, and **Ember**, which means you can integrate it with any of these frameworks to organize your UI layer alongside your application logic.
-
-## User Support
-
-Please help us keep the issue tracker organized. When creating an issue please complete the issue template and include a test case this helps us solve and label your issues. You can also ask questions on [StackOverflow](http://stackoverflow.com/questions/tagged/semantic-ui) or our [Discord](https://discord.gg/YChxjJ3)
-
-For more info take a look at our [contributing guide](https://github.com/Semantic-Org/Semantic-UI/blob/master/CONTRIBUTING.md).
+Fomantic allows developers to build beautiful websites fast, with **concise HTML**, **intuitive javascript**, and **simplified debugging**, helping make front-end development a delightful experience. Fomantic is responsively designed allowing your website to scale on multiple devices.
 
-## Install
+## :satellite: Installation
 
 ```bash
-npm install fomantic-ui --save
+$ npm install fomantic-ui --save
 ```
 
 Fomantic UI includes an interactive installer to help setup your project.
 
 * For more details on setup visit our [getting started guide](http://fomantic-ui.com/introduction/getting-started.html).
 * To learn more about theming please read our [theming guide](http://fomantic-ui.com/usage/theming.html)
 
-#### Browser Support
+### :computer: Browser Support
 
 * Last 2 Versions FF, Chrome, Safari Mac
 * IE 11+
@@ -48,25 +37,26 @@ Fomantic UI includes an interactive installer to help setup your project.
 
 Although some components will work in IE9, [grids](http://semantic-ui.com/collections/grid.html) and other [flexbox](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Flexible_boxes) components are not supported by IE9 and may not appear correctly.
 
-## Community
+## :speech_balloon: Community
 
-#### Getting Help
+### :bulb: Getting Help
 
-If you have a usage question please **do not post** post it to GitHub Issues. You can ask for usage help via [StackOverflow](http://stackoverflow.com/questions/tagged/semantic-ui) or our [Discord](https://discord.gg/YChxjJ3).
+If you have a usage question please **do not post** post it to GitHub Issues. You can ask for usage help via our [Discord](https://discord.gg/YChxjJ3) server.
 Please only create Github issues for bug's and feature requests or any other related issue.
 
-#### Submitting Bugs and Enhancements
-[GitHub Issues](https://github.com/Semantic-Org/Semantic-UI/issues) is for suggesting enhancements and reporting bugs. Before submiting a bug make sure you do the following:
+### :bug: Submitting Bugs and Enhancements
+[GitHub Issues](https://github.com/fomantic/Fomantic-UI/issues) is for suggesting enhancements and reporting bugs. Before submiting a bug make sure you do the following:
 * Check to see if the issue has already been raised.
-* [Fork this boilerplate JSFiddle](https://jsfiddle.net/ca0rovs3/) to create a test case for your bug. If a bug is apparent in the docs, that's ok as a test case, just make it clear exactly how to reproduce the issue. Only bugs that include a test case can be triaged.
-* If submitting an enhancement try and create it in the [JSFiddle](https://jsfiddle.net/ca0rovs3/) if not it's fine but explain clearly what you want.
+* [Fork this boilerplate JSFiddle](https://jsfiddle.net/31d6y7mn) to create a test case for your bug. If a bug is apparent in the docs, that's ok as a test case, just make it clear exactly how to reproduce the issue. Only bugs that include a test case can be triaged.
+* If submitting an enhancement try and create it in the [JSFiddle](https://jsfiddle.net/31d6y7mn) if not it's fine but explain clearly what you want.
 
+### :memo: Pull Requests
 
-#### Pull Requests
+Before creating a pull request be sure to read the [contributing](CONTRIBUTING.md) guide, this is where we explain everything you need to know about contributing to Fomantic-UI.
 
-When adding pull requests, be sure to merge into the [beta](https://github.com/fomantic/Fomantic-UI/tree/beta) branch.
+## Sponsors
 
-### Cross-browser testing provided by
+#### Cross-browser testing provided by [BrowserStack](https://www.browserstack.com)
 [![BrowserStack](https://cdn.rawgit.com/fomantic/Fomantic-UI-Docs/35180e95/server/raw/images/browserstack.png)](https://www.browserstack.com)
 
 #### Credit

RELEASE-NOTES.md

@@ -1,5 +1,54 @@
 ## RELEASE NOTES
 
+### Version 2.6.0 - September 18, 2018
+
+> Reason behind version jump: The new 2.6 release might look a little funny since we just released 2.5 but we thought it was necessary to bump a minor patch since the new SUI release introducing a new component and we want to stick to the SUI versioning scheme. We also added the new toast component so we didn't have to wait until the next feature release.
+
+**New Components**
+- **Toast** - Added a new toast component **Thanks [@prudho](https://github.com/prudho)** [#122](https://github.com/fomantic/Fomantic-UI/pull/122)
+
+**Bugs**
+- **Header** - Fixed header content not being displayed when in an accordion element **Thanks [@ColinFrick](https://github.com/ColinFrick)** [#103](https://github.com/fomantic/Fomantic-UI/pull/103)
+- **Menu** - Fixed inconsistent icon spacing in dropdown menus **Thanks [@prudho](https://github.com/prudho)** [#111](https://github.com/fomantic/Fomantic-UI/pull/111)
+- **Checkbox** - Fixed `before(Un)Checked` firing on init **Thanks [@ColinFrick](https://github.com/ColinFrick)** [#115](https://github.com/fomantic/Fomantic-UI/pull/115)
+- **Message** - Fixed colored floating messages not having box shadow **Thanks [@ColinFrick](https://github.com/ColinFrick)** [#124](https://github.com/fomantic/Fomantic-UI/pull/124)
+
+**Enhancements**
+- **Calendar** - Added support for `showWeekNumbers` to show the week number on the left of the calendar **Thanks [@lubber-de](https://github.com/lubber-de)** [#113](https://github.com/fomantic/Fomantic-UI/pull/113)
+- **Modal** - Pressing ESC now only closes the currently active modal when multiple are present **Thanks [@prudho](https://github.com/prudho)** [#118](https://github.com/fomantic/Fomantic-UI/pull/118)
+
+The following changes where merged from a new Semantic-UI release
+
+> `2.4.0` includes a new component `placeholder`. To use this component in your existing SUI site, be sure to add `@placeholder: 'default';` to your `theme.config`. You can see an example in `theme.config.example`
+
+**New Components**
+- **Placeholder** - Added `ui placeholder` that can be used to show where content will soon appear.
+
+**New UI Type**
+- **Segment** - Added new `ui placeholder segment` used to reserve space for UI when content is missing or empty.
+
+**Major Enhancements**
+- **Dropdown** - Added `clearable` dropdowns. When `clearable: true` is specified an (X) will appear to clear dropdown selection [#2072](https://github.com/Semantic-Org/Semantic-UI/issues/2072)
+- **Modal/Dimmer** - Modals and dimmers now include a new setting `useFlex` which defaults to `auto`. Modals and dimmers will automatically revert to using non-flex layouts when there may be layout issues with using flexbox. Modals will fall back to JS position when `detachable: false` is used or with IE11/Edge (Absolutely positioned elements inside flex containers in IE behave differently).
+
+**Critical Bugs**
+- **Modal** - Fixed issue where `scrolling modal` would not allow for scrolling with touch devices. [#6449](https://github.com/Semantic-Org/Semantic-UI/issues/6449)
+- **Label** - Fixed issue where `basic label` were appearing incorrectly **Thanks [@lasley](https://github.com/lasley) and [@ColinFrick](https://github.com/ColinFrick)** [#6582](https://github.com/Semantic-Org/Semantic-UI/issues/6582) [#6440](https://github.com/Semantic-Org/Semantic-UI/issues/6440)
+- **Menu/Dropdown** - Fixed `left menu` inside `ui menu` would display horizontally as `flex` [#6359](https://github.com/Semantic-Org/Semantic-UI/issues/6359)
+
+**Bugs**
+- **Dimmer** - Dimmer now sets `variation` at runtime, to support run-time swapping between `top aligned` and `middle aligned` using `.dimmer('setting', 'variation', 'top aligned')`
+- **Dropdown** - Fixed issue where `onChange` when used with `action: hide` would be missing the third param `$item` [#6555](https://github.com/Semantic-Org/Semantic-UI/issues/6555)
+- **Flag** - Add `uk` alias for `united kingdom` **Thanks [@PhilipGarnero](https://github.com/PhilipGarnero)** [#6531](https://github.com/Semantic-Org/Semantic-UI/issues/6531)
+- **Icon** - Fixes missing `disk outline icon` alias [#6556](https://github.com/Semantic-Org/Semantic-UI/issues/6556)
+- **List** - Fixed issue where list `content` would not take up 100% width when used alongside `img` or `icon`
+- **Menu/Dropdown** - Fixes dropdown item margin not obeyed inside `labeled icon menu` [#6557](https://github.com/Semantic-Org/Semantic-UI/issues/6557)
+- **Modal** - Fixes `@mobileTopAlignedMargin` theming variable was not implemented
+- **Modal** - Modal now will remove `blurring` after undimming, to prevent issues with `position: fixed` [#6520](https://github.com/Semantic-Org/Semantic-UI/issues/6520)
+
+**Minor Changes**
+- **Dropdown** - `inline dropdown` `close icon` default right margin default spacing slightly modified.
+
 ### Version 2.5.0 - September 3, 2018
 
 **Major Enhancements**