Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[cms-v2] Master issue for coordination and checklist #1604

Closed
27 tasks
fernandoabolafio opened this issue Dec 3, 2019 · 2 comments
Closed
27 tasks

[cms-v2] Master issue for coordination and checklist #1604

fernandoabolafio opened this issue Dec 3, 2019 · 2 comments

Comments

@fernandoabolafio
Copy link
Member

CMS refactor coordination issue

This issue intends to describe the work to be done for the competition of the "CMS v2".
Different from the work done for the proposals website, the CMS won't have design specs prior to the development. Thus, it is up to the developers to follow the layout and code style employed on the proposals redesign.

Work Summary and checklist

The following is a checklist containing the work to be done for the refactoring:

  • Authentication
    • Login
    • Signup
    • Reset password
    • Resend verification email
  • Invoice
    • User List
    • Admin List
    • New
    • Edit
    • Draft
    • Detail
    • Admin actions (approve, reject, dispute)
    • Comments
  • Payouts
    • Generate payouts
    • Payouts summary
  • User/Contractor
    • Manage tab
    • Invite
    • Search
  • DCC
    • List
    • New DCC
    • Detail
    • Admin review (approve/reject)
    • Support/opose

Methodology

In order to accomplish the work described above and keep the current website working, this work will be completed in a separated branch which will be constantly synchronized with the master branch. Once this refactoring is done, there should not be any backwards compatibility with the old side. Meaning that all remaining artifacts and libraries ("snew-classic-ui" for instance) will be removed.

@fernandoabolafio
Copy link
Member Author

duplicated of #1685

@xaur
Copy link

xaur commented Feb 5, 2020

Actually #1685 is a duplicate of this since it was created later. Please don't recreate issues because it breaks existing links and makes navigation harder. e.g. #1625 still says "to accomplish what is described in #1604".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants