Skip to content
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

Components and Images folders #83

Merged

Conversation

grmbyrn
Copy link
Contributor

@grmbyrn grmbyrn commented Dec 4, 2023

Changes Made:

Moved relevant components from the routes folder to a new components folder within the lib directory for better organisation.

Created an images folder in the static directory and updated references to images in the code to use relative paths instead of hardcoding image addresses in the src.

Details:

1. Component Organization:

Before: Components were scattered across the routes folder.
After: Components are now organized in a dedicated components folder within the lib directory.

2. Image Handling:

Before: Image addresses were hardcoded in the src attribute, making it less maintainable.
After: Images are now stored in the static/images folder, and references have been updated to use relative paths, improving maintainability and allowing for easier changes.

Additional Notes

The changes aim to enhance project structure, making it more modular and maintainable.
Please review the updated code to ensure there are no regressions or issues.

… folder to static folder and replace links in image src
@josecelano
Copy link
Member

ACK ac9407e

@josecelano josecelano merged commit 28d36be into nautilus-cyberneering:main Dec 4, 2023
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants