- Using the CLI to work with files
- Jesse Showalter
- CLI games:
- A huge cheat sheet
Collaborate to create an accessible web page.
- Practice using your computer's CLI by replicating this folder structure using only terminal commands.
- 🥚 html-css-git-exercises - Week 3
- Complete the exercises in
week-3 - Push your work regularly to GitHub
- Complete the exercises in
- 🥚 HTML-CSS-Practice-Problems
- 🐣 css-exercises
This week's project is to build your own accessible & responsive clone of the DuckDuckGo home page. We don't expect your DOM to be identical to DuckDuckGo's, but the rendered site should be visually as close as possible. Unlike the last two weeks, this project does not have a video tutorial for you to follow. You're on your own!
You are expected to submit your code from his tutorial in a new repository generated from this starter template. Your repository should be named duck-duck-clone and should be cleanly developed with one branch per step. It's up to you to write the development strategy!
This week you will also expected to have entirely correct and accessible HTML & CSS including correct Semantic HTML and ARIA. Pay special attention to points of user interaction like the search field and submit button! Your coaches will be using the validation buttons on your deployed page, FireFox's Accessibility inspector, and the accessibility audit build into Chrome Devtools to check for any mistakes. Since these tools are also available to you, you will be able find and fix any errors on your own before submission. Any validation errors left when you submit your work will land your project in "NEEDS REVISION".
Your repository must contain:
- A README describing your project in detail. Check out these articles to learn more about writing good README's: makeareadme.com, bulldogjob, meakaakka
- One well-named branch per user story. If we check out any branch, it should contain only the code necessary to make that step work. and it should work!
- A file called
development-strategy.mdin which you explain how you broke the project into user stories, describe each user story, and describe what code you wrote to implement this user story. Check out the tomato timer code-along for an example. - Include your wireframe in the
development-strategy.mdalong with a little explanation of why you made it like you did. You can either include a link if you use wireframe.cc, or upload an image if you use another tool.