diff --git a/.github/ISSUE_TEMPLATE/add-project-logo-or-image-to-your-main-repository.md b/.github/ISSUE_TEMPLATE/add-project-logo-or-image-to-your-main-repository.md deleted file mode 100644 index b913665..0000000 --- a/.github/ISSUE_TEMPLATE/add-project-logo-or-image-to-your-main-repository.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -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) diff --git a/.github/ISSUE_TEMPLATE/blank-issue.md b/.github/ISSUE_TEMPLATE/blank-issue.md deleted file mode 100644 index 4c90699..0000000 --- a/.github/ISSUE_TEMPLATE/blank-issue.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -name: Blank Issue -about: Consistent formatting make Issues concise and easy to navigate -title: '' -labels: 'complexity: missing, feature: missing, role: missing, size: missing' -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. diff --git a/.github/ISSUE_TEMPLATE/control-what-appears-when-you-paste-your-sites-link-in-social-media-sites.md b/.github/ISSUE_TEMPLATE/control-what-appears-when-you-paste-your-sites-link-in-social-media-sites.md deleted file mode 100644 index 899c3e8..0000000 --- a/.github/ISSUE_TEMPLATE/control-what-appears-when-you-paste-your-sites-link-in-social-media-sites.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -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) diff --git a/.github/ISSUE_TEMPLATE/create-project-card-for--project-name-.md b/.github/ISSUE_TEMPLATE/create-project-card-for--project-name-.md deleted file mode 100644 index 5e9496a..0000000 --- a/.github/ISSUE_TEMPLATE/create-project-card-for--project-name-.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -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 diff --git a/.github/ISSUE_TEMPLATE/custom.md b/.github/ISSUE_TEMPLATE/custom.md deleted file mode 100644 index 48d5f81..0000000 --- a/.github/ISSUE_TEMPLATE/custom.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -name: Custom issue template -about: Describe this issue template's purpose here. -title: '' -labels: '' -assignees: '' - ---- - - diff --git a/.github/ISSUE_TEMPLATE/lighthouse--accessibility---forms.md b/.github/ISSUE_TEMPLATE/lighthouse--accessibility---forms.md deleted file mode 100644 index e43c873..0000000 --- a/.github/ISSUE_TEMPLATE/lighthouse--accessibility---forms.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -name: 'Lighthouse: Accessibility - Forms' -about: Instructions for creating or improving forms to make them accessible when visitors - use screen readers AKA Form elements must have labels -title: 'Lighthouse: Accessibility - Forms' -labels: '' -assignees: '' - ---- - -### Overview -In order for your sites form(s) to be usable by visitors using screen readers all the form elements need labels. There are specific details and exceptions, which can be found in the instructions below. - -### Action Items -*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. -*If your site does not have forms* review the instructions and design new forms using the WCAG standards. - -### Instructions -Deque University -https://dequeuniversity.com/rules/axe/3.2/label diff --git a/.github/ISSUE_TEMPLATE/lighthouse--accessibility---links.md b/.github/ISSUE_TEMPLATE/lighthouse--accessibility---links.md deleted file mode 100644 index 1769d93..0000000 --- a/.github/ISSUE_TEMPLATE/lighthouse--accessibility---links.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -name: 'Lighthouse: Accessibility - Links' -about: AKA Links must have discernible text -title: 'Lighthouse: Accessibility - Links' -labels: '' -assignees: '' - ---- - -### Overview -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. - -### Action Items -*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. -*If your site does not have links yet* review the instructions and design all new links using the WCAG standards. - -### Instructions -Deque University -https://dequeuniversity.com/rules/axe/3.2/link-name diff --git a/.github/ISSUE_TEMPLATE/lighthouse--cross-origin-destinations-are-unsafe.md b/.github/ISSUE_TEMPLATE/lighthouse--cross-origin-destinations-are-unsafe.md deleted file mode 100644 index 6417137..0000000 --- a/.github/ISSUE_TEMPLATE/lighthouse--cross-origin-destinations-are-unsafe.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -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. diff --git a/.github/ISSUE_TEMPLATE/lighthouse--how-to.md b/.github/ISSUE_TEMPLATE/lighthouse--how-to.md deleted file mode 100644 index c99a39c..0000000 --- a/.github/ISSUE_TEMPLATE/lighthouse--how-to.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -name: 'Lighthouse: How To' -about: Provides overview of how to use Lighthouse and links to additional resources -title: 'Lighthouse: How To' -labels: '' -assignees: '' - ---- - -### Overview -Lighthouse is an open-source, automated tool for improving the quality of web pages. You can run it against any web page, public or requiring authentication. It has audits for performance, accessibility, progressive web apps, and more. Hack For LA recommends that you run the tests and evaluate what changes you might want to make on your website to improve performance and accessability. - -### How To Use -Lighthouse is in the Audits panel of the Chrome DevTools. To run a report: - -1. Download Google Chrome for Desktop. -2. In Google Chrome, go to the URL you want to audit. You can audit any URL on the web. -3. Open Chrome DevTools. -4. Click the Audits tab. -5. Click Perform an audit. DevTools shows you a list of audit categories. Leave them all enabled. -6. Click Run audit. After 60 to 90 seconds, Lighthouse gives you a report on the page. - -For more information go to : -https://developers.google.com/web/tools/lighthouse/ - -### Tip -You will want to re-run lighthouse on any code changes before integrating them into your site. Sometimes the specific suggestions it makes, do not actually result in improved performance or can actually harm performance. diff --git a/.github/ISSUE_TEMPLATE/lighthouse--image-optimization.md b/.github/ISSUE_TEMPLATE/lighthouse--image-optimization.md deleted file mode 100644 index b2464e1..0000000 --- a/.github/ISSUE_TEMPLATE/lighthouse--image-optimization.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -name: 'Lighthouse: Image Optimization' -about: Instructions for optimizing images -title: 'Lighthouse: Image Optimization' -labels: '' -assignees: '' - ---- - -### Overview -When you run the lighthouse review it may suggest some specific image optimizations such as choosing another image format and making those changes may or may not improve your sites actual performance. - -### Action Items -Run lighthouse on a local version of the website and then apply suggested changes and retest locally before determining if you want to keep the changes. - -### Instructions/Resources -Google's Tools for Web Developers: [Optimize Images](https://developers.google.com/web/tools/lighthouse/audits/optimize-images) -Read [closed issue #111](https://github.com/hackforla/website/issues/111) from when HackforLA.org did our audit, to see why we decided not to do the image optimization diff --git a/.github/ISSUE_TEMPLATE/proposal-to-change-project-md-file-format.md b/.github/ISSUE_TEMPLATE/proposal-to-change-project-md-file-format.md deleted file mode 100644 index 7ca2c00..0000000 --- a/.github/ISSUE_TEMPLATE/proposal-to-change-project-md-file-format.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -name: proposal to change project.md file format -about: To propose changes to project.md file format -title: Proposal to change project.md file format [that accomplishes x] -labels: documentation, enhancement -assignees: '' - ---- - -### Overview -Describe the purpose for the proposal change - -### Action items -- [ ] Indicate current state in a yaml snipit here: - -- [ ] Indicate desired future state in a yaml snipit here: - -- [ ] Perform test - - [ ] one project.md file - - [ ] updating logic of appropriate include file - - [ ] Get signoff -- [ ] update all project.md files with new or revised fields -- [ ] Update Template project.md wiki page -- [ ] Submit pull request - indicating Issue #294 is affected (format changes log), and the text "fixes Issue #[number that you are creating now] - -### Resources -Wiki page - [Template of a project.md file](https://github.com/hackforla/website/wiki/Template-of-a-project.md-file) - -***Links to comments on other issues where this proposal originated*** -REPLACE TEXT - put links here diff --git a/.github/ISSUE_TEMPLATE/update-content-for-readme-file.md b/.github/ISSUE_TEMPLATE/update-content-for-readme-file.md deleted file mode 100644 index ec57085..0000000 --- a/.github/ISSUE_TEMPLATE/update-content-for-readme-file.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -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 diff --git a/.github/ISSUE_TEMPLATE/update-project-profile---name-of-project-.md b/.github/ISSUE_TEMPLATE/update-project-profile---name-of-project-.md deleted file mode 100644 index 3212478..0000000 --- a/.github/ISSUE_TEMPLATE/update-project-profile---name-of-project-.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -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 diff --git a/.github/ISSUE_TEMPLATE/wave-chrome-extension--accessibility-review.md b/.github/ISSUE_TEMPLATE/wave-chrome-extension--accessibility-review.md deleted file mode 100644 index 7a8184a..0000000 --- a/.github/ISSUE_TEMPLATE/wave-chrome-extension--accessibility-review.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -name: 'Wave Chrome Extension: Accessibility review' -about: Describe this issue template's purpose here. -title: 'Wave Chrome Extension: Accessibility review' -labels: '' -assignees: '' - ---- - -### Overview - -#### Action Items -1. add [WAVE chrome extension](https://chrome.google.com/webstore/detail/wave-evaluation-tool/jbbplnpkjmmeebjpijfedlgcdilocofh) -2. visit site -3. click the extension and review the red flags. -4. Run the same steps for the development site (localhost). Ensure that the chrome extension has the "Allow access to file URLs" enabled. -5. Document all suggested changes in the comments. diff --git a/.github/ISSUE_TEMPLATE/which-accessibility-testing-tool-should-you-use-.md b/.github/ISSUE_TEMPLATE/which-accessibility-testing-tool-should-you-use-.md deleted file mode 100644 index 1658c1c..0000000 --- a/.github/ISSUE_TEMPLATE/which-accessibility-testing-tool-should-you-use-.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -name: Which accessibility testing tool should you use? -about: There are a lot of tools, this issue has a list of our favorites and links - to more -title: Which accessibility testing tool should you use? -labels: '' -assignees: '' - ---- - -### Overview -There are more than 100 accessibility testing tools. Figuring out which ones to use can be a black hole. For guidance we recommend this article: [Which accessibility testing tool should you use?](https://medium.com/pulsar/which-accessibility-testing-tool-should-you-use-e5990e6ef0a) - -### Summary of Article -The author recommends using the tools in the following order fixing as you go along, since no one tool catches all the relevant issues - -[aXe](https://www.deque.com/axe/) -[SiteImprove](https://chrome.google.com/webstore/detail/siteimprove-accessibility/efcfolpjihicnikpmhnmphjhhpiclljc) -[Tenon](https://tenon.io/) -[WAVE](https://wave.webaim.org/extension/) -[Lighthouse](https://developers.google.com/web/tools/lighthouse/#devtools) - -But if you want to test your site with other tools, here is a bigger [list](https://www.w3.org/WAI/ER/tools/)