Refactor homepage responsibilities for a more readable and maintainable frontend.

[diostoup1522]

The issue

The repository's frontend homepage component has grown into an unreadable ~850-line tome,
most of which is not JSX but rather a lot of large React hooks
(with some scoring cognitive complexity > 21 on the SonarQube analysis)
handling a lot of unrelated responsibilities all in a single component
which can make maintaining and modifying the frontend all the more difficult.
A single homepage component shouldn't be responsible for configuring:

• Tauri integration
• File importing and exporting
• Slash commands
• AI actions
• Drag-and-drop handling
• Keyboard shortcuts and menu actions

but rather orchestrating these functionalities together.

My proposal

Refactor the homepage into separate components
and make utility functions to move away some of the logic
the component hooks are currently responsible for
so that functionality can be maintained and modified separately.

The benefits

This would make maintaining the frontend easier, more productive,
lowering overall cognitive complexity,
making the codebase more structured
and helping the editor's frontend catch up with the more popular markdown editors.

[petertzy]

Thanks for the proposal — the timing is perfect, as this is exactly one of the areas I was planning to work on next.

I agree with the overall direction. The homepage has accumulated too many responsibilities, and I think it would be beneficial to separate the logic into smaller, more focused components, hooks, and utility functions so that the code is easier to organize and maintain. Several of the areas you mentioned were also part of my original plan for improving the frontend structure.

The main concern is that #239, as currently scoped, seems quite large to tackle as a single task or contribution. I think it would be more practical to break this refactoring effort down into several smaller, well-defined sub-issues that contributors can work on independently.

Would you, or perhaps other interested contributors, be willing to help turn this issue into a set of organized and actionable sub-issues? For example, the different responsibilities identified here could be evaluated and split into separate refactoring tasks where appropriate.

I think that would make the work easier to review, reduce the risk of a large refactor, and help us move the project forward incrementally.

Thanks again for raising this issue and for the thoughtful proposal!

[diostoup1522]

Should I close this issue then or keep it open as it is gradually fixed?

[diostoup1522]

I will make the sub issues as soon as I can.

[petertzy]

Thanks! I think it would be better to keep this issue open and use it as the overall tracking issue for the refactoring effort.

Once you create the sub-issues, we can link them here and tackle them incrementally. We can close #239 once the relevant sub-issues have been completed, or once we feel the homepage refactoring has reached the intended scope.

Thank you.