RFC: Website Renewal

[dashtaki]

Background: 🗒️

Given the upcoming need for additional features and the emergence of new requirements, it is advantageous to renew the application using a suitable framework or library. The task is not daunting as the codebase is not complex or extensive.

Problems: 🐞

1. Excessive boilerplate code has been utilized throughout the application.
2. Lack of modularity makes maintenance challenging.
3. Adding even a simple feature requires modifications in multiple places within the code.
4. The user interface has potential for improvement, specifically in terms of saving space.
5. Inconsistent Code Style and Structure: The absence of defined coding standards and conventions
6. The current technology stack used in the application may be outdated or lacking support
7. ...

Why Renew? Desired Outcome: 🎯

Numerous frontend frameworks and libraries are available today that can greatly enhance the efficiency of single-page applications (SPAs). Next.js and SolidJS are among the top options for moving forward. Here are some reasons supporting this choice:

1. Improve scalability and maintainability will significantly reduce the time spent on problem-solving and adding new features.
2. The simplified codebase will encourage more contributions from developers, making the project more appealing.
3. Consideration of server-side rendering (SSR) and client-side rendering (CSR) will enhance performance.
4. Utilizing a framework or library designed for SPAs will increase scalability.
5. The renewal will facilitate caching and ensure code stability for new features involving API calls.
6. It will be easier to develop a clear and test-friendly design, leveraging triggered outputs, functions, events, etc.
7. The abstraction layer of SPA frameworks hides complex internals, providing robustness.
8. By selecting a widely adopted and actively maintained framework or library we ensure the long-term viability of the application
9. ...

Next Steps: 🚢

1. Share this RFC and gather feedback.
2. Apply the proposed solution if everyone is in agreement and satisfied with the approach.

Hello @dashtaki ,
Thank you for writing this description. I am very interested in developing RTBF (Right to Be Forgotten), but currently, we do not have access to active contributors or the income required for that. If you would like to join our collaborative team, please inform me.

[dashtaki]

I'm willing to contribute without expecting any payment. Although we currently lack active contributors and financial resources, I believe that with a collaborative team effort, we can make progress. We can also share out concerns as much as we can and see if anybody interested to contribute.

Gonna ask some of my friends as well. 👍

send me your Telegram username (handle) to this email address: info [at] rtbf.ir.

[dashtaki]

Hi @amirshnll 👋
In follow-up to our last discussion, we mentioned the need for a new design to move forward.
Could you let me know if there are any updates on the design?

Additionally, Let me know if we need any assist in terms of design, then we can find someone who can help up.