Improve project translation listing under admin tab

[humitos]

Currently, under Admin -> Translations tab we have something like this to list "Existing translations"

I think we want to change this to feel more like the rest of the site (considering some improves that @stsewd has already done in other pages with listings --like redirects)

(I took this image from Project Import, but it's just to share the idea)

[stsewd]

We need to wait to #3572 gets approved/merged so we can reuse the css classes.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[saadmk11]

Can I Work on This Issue?

[humitos]

@saadmk11 I'd double check with @agjohnson or @ericholscher that my proposal is what we want before start working on it. I'm pinging them here looking for the 👍 of one of them.

[saadmk11]

@saadmk11 I'd double check with @agjohnson or @ericholscher that my proposal is what we want before start working on it. I'm pinging them here looking for the of one of them.

Okay Sure.

[agjohnson]

Yeah, all our admin forms should follow the new pattern. #3572 looks like a good base, I'd also look at how we implement the rest of the form for the page, as we have old forms that tried to be a list view and an edit view in a single page. The newer versions of admin pages don't do this and instead use a separate page for add/edit operations.

[saadmk11]

I saw a few admin pages use the Old Pattern (Form and List view at the same time). I would like to propose to change the Old pattern with the new one as suggested by @agjohnson.
I was able to Find these pages using the old pattern:

1. Domains
2. Maintainers
3. Redirects
4. Translations
5. Notifications

And I would also like to address the Environment Variables page should have a remove button on the list view which is used in the new pattern.
I would like to work on this if this gets accepted.
and please feel free to add any corrections to my proposal.
if I understood it incorrectly please correct me.

[agjohnson]

It would be best to split this all into digestible chunks either way, but 👍 on addressing the old pattern use in all of our forms. We are about to start a contract that will address the UX and styling on these forms, so this part is not as important as having all the correct views and form handling.

[saadmk11]

@agjohnson If I understood you correctly, you want to split the old pattern views (different views for list, create/update form) so that it matches the new pattern. Such as the subproject views in the project Admin
https://github.com/rtfd/readthedocs.org/blob/b06dedb5bf008d5d835110faa6176c24146546f1/readthedocs/projects/views/private.py#L484-L503
If I'm correct we can start working on this in small pieces (page by page) and test it.