{ | |
"env": { | |
"browser": true, | |
"es2021": true | |
}, | |
"parserOptions": { | |
"ecmaVersion": 2021, | |
"sourceType": "module" | |
}, | |
"plugins": ["import"], |
Slideshow Section: Introduction to Accessibility Testing Tools
Slide 1.1: Introduction to Accessibility Testing Tools
Provide an overview of the importance of accessibility testing in web development.
Explain how automated testing tools can help identify and fix accessibility issues.
Set the stage for the upcoming sections that explore different categories of accessibility testing tools.
module.exports = { | |
env: { | |
browser: true, | |
es2021: true, | |
node: true, | |
}, | |
extends: ['eslint:recommended', 'plugin:react/recommended', 'plugin:@typescript-eslint/recommended'], | |
overrides: [], | |
parser: '@typescript-eslint/parser', | |
parserOptions: { |
Simulate an Editor to Review and Make Writing Suggestions | |
PROMPT: | |
As a detail-oriented content editor, your primary role will be to review written pieces, such as blog posts, articles, marketing materials, or academic papers, and provide feedback on how to improve the content. This feedback may include in-depth suggestions for reorganizing the content, rephrasing certain sections, or adding additional information to enhance the piece. Additionally, you will be responsible for making edits and revisions to the text itself, ensuring that it is free of errors and meets high standards for quality. | |
When providing feedback, it is important to consider the intended audience and purpose of the piece. You should provide guidance on how to better achieve these goals through your recommendations for improvement. To do this effectively, you should be thoroughly familiar with best practices for writing and editing, including guidelines for style, tone, and formatting.Your ultimate goal as a content editor is to improve |
Please do the following before our lesson to save us time and you money:
- commit & push your latest code you've written to GitHub and send me the GitHub repo. Let me know if you're not sure how to do this. Here is a guide to do so
https://github.com/git-guides
-
send me all of the project/assignment details if you have a project/assignment. Including the due date.
-
send me some information about what you've been learning, or what you want to work on together.
Monday Lecture: HTML/CSS Review
Objective: At the end of this lesson, students will be able to:
- Build websites without Repl.It
- Use the VS Code Live Preview Extension
- Open Website projects in the browser with Live Preview
- Use Chrome DevTools
- Understand the Chrome Dev Tools Element Tab
The node_modules folder in a Node.js project contains a lot of files and directories that can be easily generated from the project's package.json file. Therefore, it's a good idea to exclude this folder from version control using a .gitignore file. Here are the steps to delete the node_modules folder, add it to .gitignore, commit the changes, push them to the remote repository, and then reinstall the dependencies using npm:
- Delete the node_modules folder:
rm -rf node_modules
- Create a .gitignore file in the root of your project if it doesn't exist already:
#!/bin/zsh | |
git reset | |
mkdir -p ~/code/tmp/delete-me/ | |
secondsInterval=20 | |
branchName=`date +"%Y%m%d%H%M%S%Z"` | |
commitDateTime=`date +"%Y-%m-%d %T%Z"` | |
(git ls-files --modified --others --exclude-standard | grep . > /dev/null) && git add . && git stash | |
git checkout main && git pull |