New UI

.github/ISSUE_TEMPLATE/--bug-report.md

@@ -0,0 +1,44 @@
+---
+name: "\U0001F41B Bug report"
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+<!-- 
+Please fill out as much of the below template as you can.
+Consider providing any applicable: code, screenshots, or gifs.
+-->
+
+### Please describe the problem (or idea)
+
+> What happened just before the problem occurred? Or what problem could this idea solve?
+
+
+
+> What did you expect to see that you didn't?
+
+
+
+### Please show us where to look
+
+https://infragram.org/sandbox/ ...
+
+
+
+### Browser, version, and operating system
+
+> Many bugs are related to these -- please help us track it down and reproduce what you're seeing!
+
+
+****
+
+## Thank you!
+
+Your help makes Infragram better! We *deeply* appreciate your helping refine and improve this site. 
+
+To learn how to write really great issues, which increases the chances they'll be resolved, see:
+
+https://publiclab.org/wiki/developers#Contributing+for+non-coders

.github/ISSUE_TEMPLATE/--feature-request.md

@@ -0,0 +1,30 @@
+---
+name: "\U0001F9E8 Feature request"
+about: Suggest an idea for this project
+title: ''
+labels: feature
+assignees: ''
+
+---
+
+<!-- Please fill out as much of the template as you can -->
+
+<!-- Start below this comment. -->
+
+
+**Please describe the desired behavior.**
+Describe the solution you'd like.
+
+
+**Additional context (optional)**
+Feel free to include any applicable: code, screenshots, or gifs.
+
+
+<!-- End. -->
+
+<!--
+Thank you! Your help makes Infragram better. We *deeply* appreciate you helping refine and improve the site.
+
+To learn how to write really great issues, which increases the chances they'll be resolved, see:
+https://publiclab.org/wiki/developers#Contributing+for+non-coders
+-->

.github/first-timers-issue-template.md → .github/ISSUE_TEMPLATE/--first-timers-only.md

@@ -1,10 +1,24 @@
-Hi, this is a [first-timers-only issue](https://code.publiclab.org/#r=all). This means we've worked to make it more legible to folks who either **haven't contributed to our codebase before, or even folks who haven't contributed to open source before**. 
+---
+name: "\U00002728 First Timers Only issue"
+about: Open a First Timers Only issue for someone
+title: ''
+labels: fto-candidate
+assignees: ''
+
+---
+
+### 💡Format this Issue Into a First Timers Issue
+This has been marked as a good candidate for becoming a [first-timers-only issue](https://code.publiclab.org/#r=all) like these, meaning that it's **simple, self-contained**, and with some extra formatting✍️, could be a great entry point for a new contributor. If you're familiar enough with this code, please consider **reformatting it as a first-timers-only issue**, and then ping @publiclab/reviewers to get it labelled🏷. Or, if this is not your first time, **try to solve it yourself**🧑‍💻!
+
+****
+
+Hi, this is a [first-timers-only issue](https://code.publiclab.org/#r=all). This means we've worked to make it more legible to folks who either **haven't contributed to our codebase before, or even folks who haven't contributed to open source before**.
 
 If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especially interested in contributions from people from groups underrepresented in free and open source software!
 
 We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝
 
-If you have contributed before, **consider leaving this one for someone new**, and looking through our general [help wanted](https://github.com/publiclab/plots2/labels/help-wanted) issues. Thanks!
+If you have contributed before, **consider leaving this one for someone new** and looking through our general [help wanted](https://github.com/publiclab/plots2/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22) issues. Thanks!
 
 ### 🤔 What you will need to know.
 
@@ -20,7 +34,7 @@ Nothing. This issue is meant to welcome you to Open Source :) We are happy to wa
   <p>And open one early if possible - even before you've completed it with additional commits - and others can help you figure out any issues you may face.</p>
 </details>
 
-- [ ] 📝 **Update** the file [$FILENAME]($BRANCH_URL) in the `$REPO` repository (press the little pen Icon) and edit the line as shown below. 
+- [ ] 📝 **Update** the file [$FILENAME]($BRANCH_URL) in the `$REPO` repository (press the little pen Icon) and edit the line as shown below.
 
 [See this page](https://code.publiclab.org/#r=all) for some help in taking your first steps!
 
@@ -30,30 +44,28 @@ Below is a "diff" showing in red (and a `-`) which lines to remove, and in green
 $DIFF
 ```
 
-
 - [ ] 💾 **Commit** your changes
 
 - [ ] 🔀 **Start a Pull Request**. There are two ways how you can start a pull request:
-1. If you are not familiar with GitHub or the pull request model, [here is a guide you can follow](https://guides.github.com/activities/hello-world/) on how GitHub works.
-2. If you are familiar with the terminal or would like to learn to use it, [here is a great tutorial](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github) on how to send a pull request using the terminal.
 
-3. You can also [edit files directly in your browser](https://help.github.com/articles/editing-files-in-your-repository/) and open a pull request from there. 
+1. If you are familiar with the terminal or would like to learn it, [here is a great tutorial](https://app.egghead.io/playlists/how-to-contribute-to-an-open-source-project-on-github) on how to send a pull request using the terminal.
+
+2. You can also [edit files directly in your browser](https://help.github.com/articles/editing-files-in-your-repository/) and open a pull request from there.
 
 - [ ] 🏁 **Done** Ask in comments for a review :)
 
 ### Please keep us updated
 
-💬⏰ - We encourage contributors to be respectful to the community and provide an update **within a week** of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance! 
+💬⏰ - We encourage contributors to be respectful to the community and provide an update **within a week** of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!
 
 If this happens to you, don't sweat it! Grab another open issue.
 
 ### Is someone else already working on this?
 
-🔗- We encourage contributors to link to the original issue in their pull request so all users can easily see if someone's already started on it. 
+🔗- We encourage contributors to link to the original issue in their pull request so all users can easily see if someone's already started on it.
 
 👥- **If someone seems stuck, offer them some help!** Otherwise, [take a look at some other issues you can help with](https://code.publiclab.org/#r=all). Thanks!
 
 ### 🤔❓ Questions?
 
-Leave a comment below!
-
+Leave a comment below, and [reach out in our chatroom](https://publiclab.org/chat)!

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,19 @@
+<!-- Add a short description about your changes here-->
+
+Fixes #0000 <!--(<=== Add issue number here)-->
+
+Make sure these boxes are checked before your pull request (PR) is ready to be reviewed and merged. Thanks!
+
+* [ ] PR is descriptively titled 📑 and links the original issue above 🔗
+* [ ] tests pass -- look for a green checkbox ✔️ a few minutes after opening your PR
+* [ ] code is in uniquely-named feature branch and has no merge conflicts 📁
+* [ ] screenshots/GIFs are attached 📎 in case of UI updation
+* [ ] 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 -->
+
+<!--Thanks!-->

CODE_OF_CONDUCT.md

@@ -1,4 +1,7 @@
-Public Lab, 55 Cromwell Street, 1C, Providence, RI 02907
+# Public Lab Code of Conduct
+
+_Public Lab, 55 Cromwell Street, 1C, Providence, RI 02907_
+
 We are coming together with an intent to care for ourselves and one another as we produce knowledge in pursuit of environmental justice. For this to work for everybody, individual decisions will not be allowed to run counter to the welfare of other people. We—visitors, community members, community moderators, staff, organizers, sponsors, and all others—hold ourselves accountable to the same values regardless of position or experience. This community aspires to be a respectful place both during online and in-person interactions so that all people are able to fully participate with their dignity intact. This document is a piece of the culture we're creating.
 
 This code of conduct applies to all spaces managed by the Public Lab community and non-profit, both online and in person. It provides a clear set of practical guidelines for events led by organizers and community members, multi-day events such as Barnraisings, and online venues such as the website, comment threads on software platforms, chatrooms, our mailing lists, the issue tracker, and any other forums created by Public Lab which the community uses for communication. For interactions with additional groups, see our Partnership Guidelines at https://publiclab.org/partners.