Update templates

This commit is contained in:
Jeremy Thomas 2017-01-15 21:14:27 +00:00
parent 486369ba7c
commit 58eff365b7
5 changed files with 39 additions and 49 deletions

View File

@ -1,38 +1,36 @@
### PLEASE READ THE FOLLOWING INSTRUCTIONS <!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->
Tag your issue accordingly: <!-- Is it about Bulma or about the Docs? -->
<!-- Is it a bug/feature/question or do you need help? -->
<!-- If it's a bug, is it a browser bug? -->
* is it about Bulma or about the Docs? ### Overview of the problem
* is it a bug/feature/question or do you need help?
* if it's a bug, is it a browser bug?
Thanks for helping out! 😇 <!-- UNCOMMENT THE APPROPRIATE LINES -->
Please remove any unused content (including these instructions) before submitting your issue. <!-- This is about the Bulma **CSS framework** -->
<!-- This is about the Bulma **Docs** -->
### Checklist <!-- I'm using Bulma **version** [x.x.x] -->
<!-- My **browser** is: -->
* [ ] This is about the Bulma **CSS framework** <!-- This is a **Sass** issue: I'm using version [x.x.x] -->
* [ ] This is about the Bulma **Docs** <!-- I am sure this issue is **not a duplicate**? -->
* [ ] I'm using Bulma **version** [x.x.x]
* [ ] My **browser** is:
* [ ] This is a **Sass** issue: I'm using version [x.x.x]
* [ ] I am sure this issue is **not a duplicate**?
### Description ### Description
_[Description of the bug, enhancement, or question]_ <!-- Description of the bug, enhancement, or question -->
### Steps to Reproduce ### Steps to Reproduce
1. _[First Step]_ <!--
2. _[Second Step]_ 1. First Step
3. _[and so on...]_ 2. Second Step
3. and so on...
-->
### Expected behavior ### Expected behavior
_[What you expected to happen]_ <!-- What you expected to happen -->
### Actual behavior ### Actual behavior
_[What actually happened]_ <!-- What actually happened -->

View File

@ -1,23 +1,21 @@
### PLEASE READ THE FOLLOWING INSTRUCTIONS <!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->
Thanks for helping out! 😇 ### Proposed solution
<!-- Which specific problem does this PR solve and how? -->
<!-- If it fixes a particular Issue, add "Fixes #ISSUE_NUMBER" in your title -->
* Pull the latest `master` branch ### Tradeoffs
* Run `npm install` to install all Bulma dependencies <!-- What are the drawbacks of this solution? Are there alternative ones? -->
* Make sure your Sass code is compliant with the [Bulma Sass styleguide](https://github.com/jgthms/bulma/blob/master/.github/CONTRIBUTING.md#bulma-sass-styleguide) <!-- Think of performance, build time, usability, complexity, coupling…) -->
* If your PR fixes an issue, reference that issue
* If your PR has lots of commits, **rebase** first
* Run `npm run build` and `npm run docs` before submitting your PR
Please remove any unused content (including these instructions) before submitting your issue.
### Pull Request ### Testing Done
<!-- How have you confirmed this feature works? -->
Fixes # <!-- BEFORE SUBMITTING YOUR PR, MAKE SURE TO FOLLOW THESE STEPS: -->
<!-- 1. Pull the latest `master` branch -->
Changes proposed: <!-- 2. Run `npm install` to install all Bulma dependencies -->
<!-- 3. Make sure your Sass code is compliant with the [Bulma Sass styleguide](https://github.com/jgthms/bulma/blob/master/.github/CONTRIBUTING.md#bulma-sass-styleguide) -->
* [ ] Add <!-- 4. If your PR fixes an issue, reference that issue -->
* [ ] Fix <!-- 5. If your PR has lots of commits, **rebase** first -->
* [ ] Remove <!-- 6. Run `npm run deploy` before submitting your PR -->
* [ ] Update

View File

@ -1,6 +1,6 @@
The MIT License (MIT) The MIT License (MIT)
Copyright (c) 2016 Jeremy Thomas Copyright (c) 2017 Jeremy Thomas
Permission is hereby granted, free of charge, to any person obtaining a copy Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal of this software and associated documentation files (the "Software"), to deal

View File

@ -38,12 +38,6 @@ You can either use that file, "out of the box", or download the Sass source file
There is **no** JavaScript included. People generally want to use their own JS implementation (and usually already have one). Bulma can be considered "environment agnostic": it's just the style layer on top of the logic. There is **no** JavaScript included. People generally want to use their own JS implementation (and usually already have one). Bulma can be considered "environment agnostic": it's just the style layer on top of the logic.
## Roadmap
Bulma keeps track of the upcoming fixes and features on Trello: [Bulma roadmap](https://trello.com/b/5Lzqejo3/bulma-roadmap)
It's more a tasklist than a roadmap, but it will give you an overview of where things are going!
## Browser Support ## Browser Support
Bulma uses [autoprefixer](https://github.com/postcss/autoprefixer) to make (most) Flexbox features compatible with earlier browser versions. According to [Can I use](http://caniuse.com/#feat=flexbox), Bulma is compatible with: Bulma uses [autoprefixer](https://github.com/postcss/autoprefixer) to make (most) Flexbox features compatible with earlier browser versions. According to [Can I use](http://caniuse.com/#feat=flexbox), Bulma is compatible with:
@ -64,4 +58,4 @@ Bulma uses [autoprefixer](https://github.com/postcss/autoprefixer) to make (most
## Copyright and license ## Copyright and license
Code copyright 2016 Jeremy Thomas. Code released under [the MIT license](https://github.com/jgthms/bulma/blob/master/LICENSE). Code copyright 2017 Jeremy Thomas. Code released under [the MIT license](https://github.com/jgthms/bulma/blob/master/LICENSE).

View File

@ -1,6 +1,6 @@
The MIT License (MIT) The MIT License (MIT)
Copyright (c) 2016 Jeremy Thomas Copyright (c) 2017 Jeremy Thomas
Permission is hereby granted, free of charge, to any person obtaining a copy Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal of this software and associated documentation files (the "Software"), to deal