Add user workflow for documenting bugs

[Shulammite-Aso]

Fixes #509
The button before the ple-footer is a link that takes a user to the editor-bug-report template here https://publiclab.org/post?n=23853&title=Give%20this%20bug%20a%20title%20here

Make sure these boxes are checked before your pull request (PR) is ready to be reviewed and merged. Thanks!

• tests pass -- look for a green checkbox ✔️ a few minutes after opening your PR -- or run tests locally with grunt jasmine
• code is in uniquely-named feature branch and has no merge conflicts
• PR is descriptively titled
• PR body includes fixes #0000-style reference to original issue #
• ask @publiclab/reviewers for help, in a comment below

We're happy to help you get this ready -- don't be afraid to ask for help, and don't be discouraged if your tests fail at first!

If tests do fail, click on the red X to learn why by reading the logs.

Please be sure you've reviewed our contribution guidelines at https://publiclab.org/contributing-to-public-lab-software

We have a loose schedule of reviewing and pulling in changes every Tuesday and Friday, and publishing changes on Fridays.

Thanks!

[Shulammite-Aso]

@jywarren @emilyashley @shreyaa-sharmaa @keshav234156 @NitinBhasneria please take a look at this.

[jywarren]

Thanks for repointing this at the main branch! Just a couple small tweaks, thanks!

[Shulammite-Aso]

Have made the changes @jywarren

[govindgoel]

Looks Fine!
@jywarren please review this

[jywarren]

This looks perfect. Thank you so much @Shulammite-Aso !!!

Just checking if you saw this post on the release schedule: #532 (comment)

just want to be sure you're in sync, thank you!

[jywarren]

Done! Great! So, i think we need to be sure this gets reflected not just in the example but in the plots2 usage as well. The corresponding file in the plots2 integration is here:

https://github.com/publiclab/plots2/blob/master/app/views/editor/rich.html.erb

Can you open a new PR on plots2 making the same change (probably the CSS won't be needed if we ensure that a new release of the Editor is merged before this change is added? Or we can just redundantly add the CSS change to plots2 but leave a comment that it can be removed after the next version of the Editor.

Thank you @Shulammite-Aso ! It'll be great to see this in production!

[Shulammite-Aso]

Done! Great! So, i think we need to be sure this gets reflected not just in the example but in the plots2 usage as well. The corresponding file in the plots2 integration is here:

https://github.com/publiclab/plots2/blob/master/app/views/editor/rich.html.erb

Can you open a new PR on plots2 making the same change (probably the CSS won't be needed if we ensure that a new release of the Editor is merged before this change is added? Or we can just redundantly add the CSS change to plots2 but leave a comment that it can be removed after the next version of the Editor.

Thank you @Shulammite-Aso ! It'll be great to see this in production!

Oh yeah, will certainly do this.
Thanks!!