Refactor Folder Structure and Module Naming for Improved Organization

[devcodes9]

Is your feature request related to a problem? Please describe.

The current folder structure and module naming in the Editor Hub repository are inconsistent and overly verbose. This makes navigation and maintenance of the codebase more difficult than necessary. For example, we have folders like quill-emojijs-main instead of simply emoji.

Describe the solution you'd like

Refactor the folder structure and module naming to be more concise, consistent, and intuitive. This should include:

1. Simplifying module names (e.g., emoji instead of quill-emojijs-main)
2. Organizing related modules into logical groupings
3. Ensuring consistent naming conventions across the project
4. Updating all relevant import statements and documentation

Implementation details

1. Create a new folder structure that logically groups related modules
2. Rename modules to be more concise while still being descriptive
3. Update all import statements throughout the codebase
4. Update documentation, including README files, to reflect the new structure

Proposed folder structure: (Can be changed) editor-hub/ ├── src/ │ ├── core/ │ ├── modules/ │ │ ├── emoji/ │ │ ├── mention/ │ │ ├── table/ │ │ └── ...

Example of module renaming:

• quill-emojijs-main -> emoji
• quill-mention -> mention
• quill-better-table-master -> table

Relevant code

This change will affect multiple areas of the codebase. Here's an example of how imports might change:

// Before
import Emoji from 'quill-emojijs-main';
// After
import Emoji from 'modules/emoji';

Additional context

Refactoring the folder structure and module naming will improve the overall organization of the project, making it easier for both maintainers and contributors to navigate and understand the codebase. It will also make the project more approachable for new contributors.

Possible challenges

1. Ensuring all imports are correctly updated across the entire project
2. Maintaining backwards compatibility for any external projects that may be using specific import paths
3. Updating all documentation and examples to reflect the new structure

Acceptance Criteria

• [ ] New folder structure is implemented
• [ ] All modules are renamed to be more concise and descriptive
• [ ] All import statements in the codebase are updated to reflect the new structure
• [ ] No broken imports or build errors after refactoring

[infernodragon456]

Hello, can you assign me this issue to work on?

[devdcodes9]

@infernodragon456 Assigned..Happy Coding!

[infernodragon456]

@devcodes9 should I clone the main branch or the staging branch?

[devcodes9]

@infernodragon456 you can clone it from staging

[infernodragon456]

@devcodes9 I have updated the file structure as mentioned. Here is a screenshot for reference: Please review and let me know of any changes! If this is acceptable, let me know so that I can create a PR.

[devcodes9]

@infernodragon456 Structure looks fine(other than 2 dist folders). I would request you to read the acceptance criteria, dont forget to resolve the imports and build. Also, provide a screen recording in the PR.