Skip to content

Commit

Permalink
Initial commit
Browse files Browse the repository at this point in the history
  • Loading branch information
ExperimentsInHonesty authored Jun 18, 2024
0 parents commit fc32f41
Show file tree
Hide file tree
Showing 16 changed files with 837 additions and 0 deletions.
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
name: Add project logo or image to your main repository
about: Simple action that will make it possible to add project to hackforla.org website
title: ''
labels: enhancement
assignees: ''

---

### Overview
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.

### Action Items
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.

### Resources/Instructions
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.
Read Github's [Customizing your repository's social media preview](https://help.github.com/en/articles/customizing-your-repositorys-social-media-preview)
19 changes: 19 additions & 0 deletions .github/ISSUE_TEMPLATE/blank-issue.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
name: Blank Issue
about: Consistent formatting make Issues concise and easy to navigate
title: ''
labels: ''
assignees: ''

---

### Overview
REPLACE THIS TEXT -Text here that clearly states the purpose of this issue in 2 sentences or less.

### Action Items
REPLACE THIS TEXT -If this is the beginning of the task this is most likely something to be researched and documented.

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.

### Resources/Instructions
REPLACE THIS TEXT -If there is a website which has documentation that helps with this issue provide the link(s) here.
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
---
name: Control what appears when you paste your sites link in social media sites
about: Add Open Graph Markup tags to header
title: Control what appears when you paste your sites link in social media sites
labels: enhancement, question
assignees: ''

---

### Overview
When your website is shared on slack, facebook, twitter, etc. It should automatically display with an image and title instead of just the URL.

### Action items
Identify what to put in the following fields:
og:url
g:type
og:title
og:description
og:image
og:type (optional)
og:local (option)
using the standards set forth in the instructions.

Add content to header and test with the tool provided in the instructions.

### Instructions
[A Guide to Sharing for Webmasters](https://developers.facebook.com/docs/sharing/webmasters#markup)
45 changes: 45 additions & 0 deletions .github/ISSUE_TEMPLATE/create-agenda.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
---
name: Create Agenda
about: Assign issue to all team members day after meetup in prep for next meetup
title: ''
labels: documentation, help wanted, question
assignees: ''

---

### Overview
This issue tracks the agenda for our weekly meetings

#### Issue Template
```
## [Date ] Meeting Agenda
### Prework to prep for meeting
- [ ] #
### Recurring items: Happens on the ________ meeting
- [ ] review any issues that are in the [new issue approval column]
- [ ] Accountability and Support Check.
- [ ] Review assignments for each Team member
- [ ] [Name of Person]
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label] and define how to break down further
- [ ] Review to see if there are any members to Onboard or Offboard
- [ ] #
### New Items
- [ ]
- [ ] Carry over Items to next meeting that don't get addressed
### FYIs
-
### Notes from Meeting
### Task Items
```

### Links to other agenda issues for your team
(so that you can easily post on their agendas items that come up at yours)

### Previous Meetings (link to each comment with the date)
30 changes: 30 additions & 0 deletions .github/ISSUE_TEMPLATE/create-project-card-for--project-name-.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
---
name: Create project card for [project name]
about: Gather information to add this project to HackforLA's website
title: ''
labels: documentation, good first issue, question
assignees: ''

---

### Overview
Provide collateral for the HackforLA website

### Action Items
- [ ] Gather items
- [ ] 600 x 400 image
- [ ] Alt image text
- [ ] 1500 x 700 hero image (please do not put project title on hero image)
- [ ] Alt image text
- [ ] Name of project
- [ ] A blurb about your project
- [ ] Links (github, slack channel url, Testing Site, Live Site, etc.)
- [ ] Any resources for a Getting Started link (a link to a wiki, readme(s) or both)
- [ ] What you are looking for skills wise
- [ ] Partner(s)
- [ ] Location
- [ ] Status
- [ ] Add project Card to website

### Resources/Instructions
See project cards on the hackforla.org website for examples
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
name: 'Lighthouse: Cross-origin destinations are unsafe'
about: Instructions for addressing the cross-origin linking vulnerabilities
title: 'Lighthouse Issue: Cross-origin destinations are unsafe'
labels: ''
assignees: ''

---

### Overview
Links to cross-origin destinations are unsafe both from a security and performance perspective.

### Action Item
Run [Lighthouse](https://developers.google.com/web/tools/lighthouse/) and then follow the instructions in [cross-origin destinations are unsafe]
(https://developers.google.com/web/tools/lighthouse/audits/noopener) .

## Summary of instructions
When using *target=_blank* also adding *rel="noopener"* to the tag ensures that new page runs in a separate process.
117 changes: 117 additions & 0 deletions .github/ISSUE_TEMPLATE/onboard---offboard--product.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,117 @@
---
name: 'Onboard & Offboard: Product'
about: Use this issue to create an onboarding/offboarding issue 1 time.
title: 'Onboard & Offboard: Product'
labels: ''
assignees: ''

---

### Overview
We need to have a checklist of items to do when a product manager onboard and offboards so that the process can be consistent and fast.

### Date Updated
(insert date you created this issue and keep updating the date each time the org template change are integrated)

### Action Items
- [ ] Check to see if the org template for this process has new steps in it, and if it does, update this issue and its template with content and add the last date you updated the template below
- [ ] Copy template to comment below
- [ ] Add name of person
- [ ] Check off as done

```
#### Onboard
- [ ] Slack channel membership
- [ ] [insert name of channel]
- [ ] [insert name of 2nd channel]
- [ ] Add to Google calendar invites
- [ ] [DAY - PM meeting]
- [ ] [DAY - BA meeting]
- [ ] [DAY - UX Research meeting]
- [ ] [DAY - All-team meeting]
- [ ] [DAY - Design team meeting]
- [ ] Add to team page on Wiki
- [ ] Google Drive
- [ ] Add to drive as Manager
- [ ] Roster
- [ ] Send link
- [ ] Team member adds themselves
- [ ] Check for Public and note in roster
- [ ] Check for 2FA and note in roster
- [ ] GitHub
- [ ] Add to team write team
- [ ] Change membership to maintainer
- [ ] Add to read vault
- [ ] Change membership to maintainer
- [ ] Figma
- [ ] invite
- [ ] acceptance
- [ ] 1password
- [ ] invitation
- [ ] acceptance
- [ ] add to vaults
- [ ] [REPLACE with name of primary vault]
- [ ] [REPLACE with name of secondary vault]
- [ ] Zoom vault
- [ ] Add to email address(s)
- [ ] [REPLACE with name of primary email]
- [ ] [REPLACE with name of secondary email]
- [ ] Social Media Accounts with role assignment
- [ ] Facebook
- [ ] Train how to
- [ ] login to team account
- [ ] setup chrome shortcut for adding to desktop
- [ ] use zoom spreadsheet, vault and accounts
- [ ] calendar invite
```
```
#### Offboard
- [ ] Remove from Google calendar invite
- [ ] [DAY - PM meeting]
- [ ] [DAY - BA meeting]
- [ ] [DAY - UX Research meeting]
- [ ] [DAY - All-team meeting]
- [ ] [DAY - Design team meeting]
- [ ] WIKI
- [ ] move to new place on team page
- [ ] 1password setup
- [ ] remove from team vaults
- [ ] [REPLACE with name of primary vault]
- [ ] [REPLACE with name of secondary vault]
- [ ] Zoom vault
- [ ] Google Drive
- [ ] demote to viewer
- [ ] Roster
- [ ] mark as inactive
- [ ] GitHub
- [ ] demote member to read only team and remove from write team
- [ ] Figma
- [ ] remove from team
- [ ] Help them delete the desktop shortcut to email address if they made one.
- [ ] Remove from email address(s)
- [ ] [REPLACE with name of primary email]
- [ ] [REPLACE with name of secondary email]
- [ ] Remove from Social Media Accounts with role assignment
- [ ] Facebook
```

### Resources/Instructions
- [1password.com](https://1password.com/)
- [REPLACE with Google Drive Link]
- [REPLACE with Team Roster]
- Check public and 2FA at [people page](https://github.com/orgs/hackforla/people)
- [REPLACE with GitHub Team URL]
- [base (read)]
- [write]
- [maintain]
- [triage]
- [admin]
- [other]
- WIKI team page: https://github.com/hackforla/[Replace with name of your project]/wiki/The-Team
- [Replace with name of your project Figma]
- Shortcut for adding a profile to the desktop: chrome://settings/manageProfile
- Tutorials
- [Forward emails to team members](https://github.com/hackforla/product-management/wiki/Forward-emails-to-team-members)
---
[org template](https://raw.githubusercontent.com/hackforla/.github/main/.github/ISSUE_TEMPLATE/onboard---offboard--product.md) updated 2022-02-23
[Changelog](https://github.com/hackforla/product-management/wiki/Onboard-Offboard-Changelog)
20 changes: 20 additions & 0 deletions .github/ISSUE_TEMPLATE/update-content-for-readme-file.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
name: Update Content for ReadMe file
about: Instructions for revising the README.md file inside this repository
title: ''
labels: documentation, good first issue, help wanted, question
assignees: ''

---

### Overview
We need to have a working READme file to easily on-board new team members.

### Action Items
- [ ] Add the following information as a comment to this issue:
- [ ] Identify what information needs to be collected.
- [ ] Identify who holds each piece of information.
- [ ] Collect information.

### Resources/Instructions
PUT LINK TO README.md FILE HERE
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
---
name: 'Update Project Profile: [name of project]'
about: We are making a project home page for each project and need some additional
info
title: 'Update Project Profile: [name of project]'
labels: documentation
assignees: ''

---

### Overview
Update the following fields for your project. These updated fields will then be updated to be shown on the website.

### Action Items
- [ ] Update wording of anything currently on the project card (see [hackforla.org](https://www.hackforla.org/))
- [ ] Provide information on which Tools your team is using for the project (Ex: figma, Balsamiq, photoshop, etc.) . This is different than programming languages
- [ ] Update "Looking For" Section
- [ ] Update any links that are not currently displayed on the site (do you have a demo site?)
- [ ] Hero image to be displayed on Project Home Page at 1500 x 700 px
- [ ] Any resources for a Getting Started link (either a link to a wiki or readme)

### Resources/Instructions
See the hero image on the [hackforla.org](https://www.hackforla.org/) homepage
15 changes: 15 additions & 0 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
name: ci
on:
push:
branches:
- main
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: actions/setup-python@v2
with:
python-version: 3.x
- run: pip install mkdocs-material
- run: mkdocs gh-deploy --force
Loading

0 comments on commit fc32f41

Please sign in to comment.