brytebee / awesomebooks

In this project, I built a simple website that allows users to add/remove books from a library list of books. I used JavaScript objects and arrays. I also used vanilla JavaScript DOM manipulation to simulate REACT and AJAX's single-page website concept. Lastly, I used is HTML and CSS3 technologies.

AWESOME BOOKS

First JS Project: Awesome Project

In this project, I built a simple website that allows users to add/remove books from a library list of books. I used JavaScript objects and arrays. I also used vanilla JavaScript DOM manipulation to simulate REACT and AJAX's single-page website concept. Lastly, I used is HTML and CSS3 technologies.

Snapshot

This project features HTML5 semantic tags, CSS and JS-DOM.

Built With

• HTML5, CSS3 and JS-DOM

Live Demo

Live Demo Link

Prerequisites

Knowledge of HTML Semantics CSS And JS-DOM

Author

👤 Atsighi Bright

• GitHub: @brytebee
• Twitter: @brytebee
• LinkedIn: brytebee

👤 Safa Aballagh

• GitHub: @Safafa
• Twitter: @safa aballagh
• LinkedIn: Aballagh Safa

🤝 Contributing

Contributions, issues, and feature requests are welcome!

Feel free to check the issues page.

Show your support

Give a ⭐️ if you like this project!

Acknowledgments

• Hat tip to anyone whose code was used
• Inspiration

📝 License

This project is Microverse licensed.

awesomebooks's Issues

Peer-to-peer code review

Peer Code Review

Hello @brytebee, we absolutely love the work you've done here and can't wait to see what the finished product looks like.

However we have a few suggestions on how you can make your website better.
Note that these are only suggestion's.

1.

To keep your code as clean as possible we recommend putting this line of code;

AwesomeBooks/index.html

Line 18 in e74c7eb

<script src="script.js"></script>

In the head section of your website and adding defer to it, this will make it so you don't need to have all your script files at the end of the page.
e.i

<script defer src="script.js"></script>

2.

We also noticed that currently there is no live demo of your web app, we'd really love to see what it looks like without having to clone the repo as well as follow active changes without cloning every sing time;
You can read more about deploying a page using GitHub Pages here.

3.

Consider separating the artifacts in your repository based on what they are. e.i placing the js files within a js folder to keep your repository organised, the same applies for the css files.