2.5.21 Make components from admin views parts
Related to the audit.
A good first step would be to remove existing repetition in the admin codebase, by using more view helpers or a distinct Ruby solution like GitHub’s ViewComponents. If this is not enough, another solution could be to migrate the existing admin application to a Vue.js application, and reuse existing Vue.js components, thus migrating the Ruby on Rails project to an API-only mode. Finally, if all admin actions are or could be available in the Vue.js app, the admin codebase should as well be removed.
I propose to work on a mix of view helpers and reusable widget partials; I don't think we'll make a separate application for the administration. The VueJS app may be the solution too, as long as it's still integrated to this codebase (as the garden apps currently are).
If the VueJS solution is chosen some controllers will need to be implemented in the API too.
It's tagged good first issue
, depending on what you plan to do...