-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue: Improve File Structure for LisBook Project #10
Comments
hey @Ctoic please assign this issue to me. |
Sure will assign the issue do follow the best practises to complete the task. Happy coding :) |
hey @Ctoic is this issue still open . if yes then do assign me. |
Best of luck and do your best 👍🏼 I hope you will get your 4 pull request merge from here and complete hacktoberfest |
Hi @Ctoic, I would like to work on this issue and improve the file structure as proposed. Could you please assign it to me? Thanks! |
Make sure it works afer deployment @sAchin-680 |
Go Ahead @sAchin-680 |
Thank you for the feedback, @Ctoic ! I will ensure that all changes are thoroughly tested after deployment to verify that the project works as expected with the new file structure. I'll also double-check all file references and asset loading to avoid any issues. Please feel free to let me know if there are any additional details or requirements you'd like me to consider during this process. |
The current file structure of the LisBook project can be improved to enhance organization and ease of navigation for contributors. A well-structured project makes it easier for beginners to understand the application flow and locate files.
Proposed Changes:
Create a /src directory to contain all source files, including:
A /css folder for stylesheets.
A /js folder for JavaScript files.
An /img folder for images and icons.
The main index.html file.
Introduce an /assets directory for static assets, such as:
A /fonts folder for custom fonts.
A /media folder for additional audio files or media.
Create a /docs directory for documentation files, including:
CONTRIBUTING.md for contribution guidelines.
README.md for project overview and instructions.
LICENSE for license information.
Add a .gitignore file to exclude unnecessary files from the Git repository.
Benefits:
Improves organization and readability of the project.
Facilitates easier contributions from new developers.
Enhances the scalability of the project as it grows.
Acceptance Criteria:
Implement the proposed file structure.
Ensure all existing files are moved to their new locations without breaking functionality.
Update any file references in the code accordingly.
The text was updated successfully, but these errors were encountered: