Skip to content

[Feature] The file structure in the repository can be improved. #287

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

Closed
1 task done
Murdock9803 opened this issue Jun 27, 2024 · 0 comments · Fixed by #289
Closed
1 task done

[Feature] The file structure in the repository can be improved. #287

Murdock9803 opened this issue Jun 27, 2024 · 0 comments · Fixed by #289
Assignees
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work

Comments

@Murdock9803
Copy link
Member

Problem

At present, some files in the codebase are scattered and not organized properly. These are not intuitive for the first time contributors and can make them confused. Re-structuring the codebase can make it more maintainable and collaborative.

Description

For example, the style.css file lies in the docs/ directory, at the same level as some of the pages of website like all.html and submission.html. Furthermore, images and downloadable PDFs are also lying in the docs/ directory. These can be segregated from the rest of the files by placing inside an _assets folder. The html pages can also be grouped into one _pages directory.

Implementation

  • I would be interested in implementing this feature.
@Murdock9803 Murdock9803 added 🟩 priority: low Low priority and doesn't need to be rushed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🏁 status: ready for work Ready for work and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work
Projects
None yet
1 participant