Migrate the Hub to React and make it deployable on-premises

[lbroudoux]

As the previous attempt to update the Hub fell short (see #76), we're launching a new initiative with some new potential contributors. Following discussions during the spring, the goal is now clear: to transition the Hub to React technology. But before diving into technical details, let's remind some goals, requirements and constraints that will allow us to put some guardrails on the tasks to come:

1. The functional goal is to move the Hub UC to something friendly that can be easily customized (logo, name, colors, styles) for in-house/on-premises usage.
2. The technical goal is to migrate the existing old stack (mainly Angular 8 and Bootstrap 4) to an up-to-date React-based ecosystem,
3. As stated in the DEPENDENCY_POLICY.md file, we'd like to integrate 3rd party dependencies only when it makes sense (ie: the usage or diversity requirements are somewhat strong enough to justify pulling out a dependency). There's a strong requirement that picked dependencies must have compatible licensing terms with the CNCF policy.
4. Selected library, project structure, implementation code, and so on should be aligned with common standards and best practices within the field to make future maintenance easy and welcome many more contributions!
5. The produced Hub frontend should be easily embeddable as a web component (or a library if a web component is not possible) so that it will be seamlessly reused across other frontends like the Microcks application itself, a Microcks Backstage plugin, or any custom-made internal developer portal.

I know we have people out there ready for suggestions. Let's keep this issue opened as a global tracking point and let's deep dive into specific scoped task discussions via sub-issues.

Thanks!

[pplancq]

I've created a PR #191 with the initial documentation for the React migration process. The PR includes:

1. An analysis of the current Angular frontend.
2. A detailed migration plan to React.
3. A status report on the current state of the migration.
4. A roadmap with tasks, priorities, and timeline.

The documentation is intended to provide a clear path forward for the migration and ensure that all contributors are aligned on the goals and approach.

Please review the documentation and provide any feedback or suggestions. Let's discuss any adjustments needed to the plan and start addressing the critical issues highlighted in the status report.

[lbroudoux]

This is awesome! Thanks for contributing this documentation that will certainly help us move things forward. I'll merge this PR asap.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️