Skip to content

Commit a093b0f

Browse files
ExperimentsInHonestyExperimentsInHonesty
authored
Initial commit
0 parents  commit a093b0f

21 files changed

+942
-0
lines changed

‎.github/ISSUE_TEMPLATE/add-project-logo-or-image-to-your-main-repository.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
name: Add project logo or image to your main repository
3+
about: Simple action that will make it possible to add project to hackforla.org website
4+
title: ''
5+
labels: enhancement
6+
assignees: ''
7+
8+
---
9+
10+
### Overview
11+
By adding the project's logo/image to your project's primary repository, we will be able to dynamically deliver up to date information about your project to the hackforla.org website. Also when people add the link to the repository in LinkedIn or Slack, or other social media it will automatically use the image as well as the description, improving the link's chances of getting clicked on.
12+
13+
### Action Items
14+
Add project's logo/image to your primary Github repository using the instructions below. You should use the same image as is on the hackforla.org website, or if another image is desired, please replace both with the same image.
15+
16+
### Resources/Instructions
17+
Tip: Your image should be a PNG, JPG, or GIF file under 1 MB in size. For the best quality rendering, we recommend keeping the image at 640 by 320 pixels.
18+
Read Github's [Customizing your repository's social media preview](https://help.github.com/en/articles/customizing-your-repositorys-social-media-preview)

‎.github/ISSUE_TEMPLATE/blank-issue.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
name: Blank Issue
3+
about: Consistent formatting make Issues concise and easy to navigate
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
### Overview
11+
REPLACE THIS TEXT -Text here that clearly states the purpose of this issue in 2 sentences or less.
12+
13+
### Action Items
14+
REPLACE THIS TEXT -If this is the beginning of the task this is most likely something to be researched and documented.
15+
16+
REPLACE THIS TEXT -If the issue has already been researched, and the course of action is clear, this will describe the steps. However, if the steps can be divided into tasks for more than one person, we recommend dividing it up into separate issues, or assigning it as a pair programming task.
17+
18+
### Resources/Instructions
19+
REPLACE THIS TEXT -If there is a website which has documentation that helps with this issue provide the link(s) here.

‎.github/ISSUE_TEMPLATE/control-what-appears-when-you-paste-your-sites-link-in-social-media-sites.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
name: Control what appears when you paste your sites link in social media sites
3+
about: Add Open Graph Markup tags to header
4+
title: Control what appears when you paste your sites link in social media sites
5+
labels: enhancement, question
6+
assignees: ''
7+
8+
---
9+
10+
### Overview
11+
When your website is shared on slack, facebook, twitter, etc. It should automatically display with an image and title instead of just the URL.
12+
13+
### Action items
14+
Identify what to put in the following fields:
15+
og:url
16+
g:type
17+
og:title
18+
og:description
19+
og:image
20+
og:type (optional)
21+
og:local (option)
22+
using the standards set forth in the instructions.
23+
24+
Add content to header and test with the tool provided in the instructions.
25+
26+
### Instructions
27+
[A Guide to Sharing for Webmasters](https://developers.facebook.com/docs/sharing/webmasters#markup)

‎.github/ISSUE_TEMPLATE/create-agenda.md

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
name: Create Agenda
3+
about: Assign issue to all team members day after meetup in prep for next meetup
4+
title: ''
5+
labels: documentation, help wanted, question
6+
assignees: ''
7+
8+
---
9+
10+
### Overview
11+
This issue tracks the agenda for our weekly meetings
12+
13+
#### Issue Template
14+
```
15+
## [Date ] Meeting Agenda
16+
17+
### Prework to prep for meeting
18+
- [ ] #
19+
20+
### Recurring items: Happens on the ________ meeting
21+
- [ ] review any issues that are in the [new issue approval column]
22+
- [ ] Accountability and Support Check.
23+
- [ ] Review assignments for each Team member
24+
- [ ] [Name of Person]
25+
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
26+
- [ ] review issues with [epic label] and define how to break down further
27+
- [ ] Review to see if there are any members to Onboard or Offboard
28+
- [ ] #
29+
30+
### New Items
31+
- [ ]
32+
- [ ] Carry over Items to next meeting that don't get addressed
33+
34+
### FYIs
35+
-
36+
37+
### Notes from Meeting
38+
39+
### Task Items
40+
```
41+
42+
### Links to other agenda issues for your team
43+
(so that you can easily post on their agendas items that come up at yours)
44+
45+
### Previous Meetings (link to each comment with the date)

‎.github/ISSUE_TEMPLATE/create-project-card-for--project-name-.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
name: Create project card for [project name]
3+
about: Gather information to add this project to HackforLA's website
4+
title: ''
5+
labels: documentation, good first issue, question
6+
assignees: ''
7+
8+
---
9+
10+
### Overview
11+
Provide collateral for the HackforLA website
12+
13+
### Action Items
14+
- [ ] Gather items
15+
- [ ] 600 x 400 image
16+
- [ ] Alt image text
17+
- [ ] 1500 x 700 hero image (please do not put project title on hero image)
18+
- [ ] Alt image text
19+
- [ ] Name of project
20+
- [ ] A blurb about your project
21+
- [ ] Links (github, slack channel url, Testing Site, Live Site, etc.)
22+
- [ ] Any resources for a Getting Started link (a link to a wiki, readme(s) or both)
23+
- [ ] What you are looking for skills wise
24+
- [ ] Partner(s)
25+
- [ ] Location
26+
- [ ] Status
27+
- [ ] Add project Card to website
28+
29+
### Resources/Instructions
30+
See project cards on the hackforla.org website for examples

‎.github/ISSUE_TEMPLATE/custom.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
name: Custom issue template
3+
about: Describe this issue template's purpose here.
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+

‎.github/ISSUE_TEMPLATE/feature_request.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: 'Feature Suggestion: '
5+
labels: documentation, product
6+
assignees: ''
7+
8+
---
9+
10+
### Overview
11+
Please write a user story for this feature suggestion in the following format: As a ______, I want to do X for Y reason and replace this text with it.
12+
13+
### Action Items
14+
- [ ] Define your Feature Suggestion
15+
- [ ] What is the feature you are suggesting?
16+
- [ ] Is this feature urgent
17+
- [ ] if so why?
18+
- [ ] How long do you expect it take to implement this issue?
19+
- [ ] Who is needed to implement this feature (Could you implement it yourself?)
20+
- [ ] Design
21+
- [ ] Front End
22+
- [ ] Back End
23+
- [ ] Database
24+
- [ ] What problem does this feature solve?
25+
- [ ] What technologies are needed for this feature?
26+
27+
### Resources/Instructions
28+
If there is a website which has documentation that helps with this issue provide the link(s) here:
29+
30+
31+
**Additional context**
32+
Add any other context or screenshots about the feature request here.

‎.github/ISSUE_TEMPLATE/lighthouse--accessibility---forms.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: 'Lighthouse: Accessibility - Forms'
3+
about: Instructions for creating or improving forms to make them accessible when visitors
4+
use screen readers AKA Form <input> elements must have labels
5+
title: 'Lighthouse: Accessibility - Forms'
6+
labels: ''
7+
assignees: ''
8+
9+
---
10+
11+
### Overview
12+
In order for your sites form(s) to be usable by visitors using screen readers all the form <input> elements need labels. There are specific details and exceptions, which can be found in the instructions below.
13+
14+
### Action Items
15+
*If your site already has forms* review the instructions and document the changes needed to bring your form(s) into WCAG compliance, by commenting on this issue.
16+
*If your site does not have forms* review the instructions and design new forms using the WCAG standards.
17+
18+
### Instructions
19+
Deque University
20+
https://dequeuniversity.com/rules/axe/3.2/label

‎.github/ISSUE_TEMPLATE/lighthouse--accessibility---links.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
name: 'Lighthouse: Accessibility - Links'
3+
about: AKA Links must have discernible text
4+
title: 'Lighthouse: Accessibility - Links'
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
### Overview
11+
The formatting of links can make them readable or unreadable by screen readers. Which includes creating programmatic events for links without making them device specific (e.g., onfocus() instead of onmouseover(), etc.), and other ways of making sure all links are visible by screen readers.
12+
13+
### Action Items
14+
*If your site already has links* review the instructions and document the changes needed to bring your link(s) into WCAG compliance, by commenting on this issue.
15+
*If your site does not have links yet* review the instructions and design all new links using the WCAG standards.
16+
17+
### Instructions
18+
Deque University
19+
https://dequeuniversity.com/rules/axe/3.2/link-name

‎.github/ISSUE_TEMPLATE/lighthouse--cross-origin-destinations-are-unsafe.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
name: 'Lighthouse: Cross-origin destinations are unsafe'
3+
about: Instructions for addressing the cross-origin linking vulnerabilities
4+
title: 'Lighthouse Issue: Cross-origin destinations are unsafe'
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
### Overview
11+
Links to cross-origin destinations are unsafe both from a security and performance perspective.
12+
13+
### Action Item
14+
Run [Lighthouse](https://developers.google.com/web/tools/lighthouse/) and then follow the instructions in [cross-origin destinations are unsafe]
15+
(https://developers.google.com/web/tools/lighthouse/audits/noopener) .
16+
17+
## Summary of instructions
18+
When using *target=_blank* also adding *rel="noopener"* to the tag ensures that new page runs in a separate process.

0 commit comments

Comments
 (0)