This project was on behalf of our own codebase, wanting to make it more accessible and reader friendly. The elements of this codebase have been updated to meet with global standards. ((((Provide a short description explaining the what, why, and how of your project. Use the following questions as a guide:)))
- The motivation? A semantic element clearly describes its meaning to both the browser and the developer so its win win!!
- We built this project to help with accessibility google ranking and to help with seo
- The problem that it solves is clearly just that an article should make sense on its own,
- Semantics doesnt need to be hard actually it can be fun?
What are the steps required to install your project? Provide a step-by-step description of how to get the development environment running.
Provide instructions and examples for use. Include screenshots as needed.
To add a screenshot, create an assets/images folder in your repository and upload your screenshot to it. Then, using the relative filepath, add it to your README using the following syntax:
```md
```
My cat collaborated with me on this project all across the keyboard multiple times. Thanks lilly !!
If you used any third-party assets that require attribution, list the creators with links to their primary web presence in this section.
If you followed tutorials, include links to those here as well.
The last section of a high-quality README file is the license. This lets other developers know what they can and cannot do with your project. If you need help choosing a license, refer to https://choosealicense.com/.
🏆 The previous sections are the bare minimum, and your project will ultimately determine the content of this document. You might also want to consider adding the following sections.
Badges aren't necessary, per se, but they demonstrate street cred. Badges let other developers know that you know what you're doing. Check out the badges hosted by shields.io. You may not understand what they all represent now, but you will in time.
If your project has a lot of features, list them here.
If you created an application or package and would like other developers to contribute it, you can include guidelines for how to do so. The Contributor Covenant is an industry standard, but you can always write your own if you'd prefer.
Go the extra mile and write tests for your application. Then provide examples on how to run them here.