Documentation: Frontend Building Checklist
What does this MR do?
It updates our development process documentation part and adds newly created checklists for building a big new feature.
Are there points in the code the reviewer needs to double check?
Check the Checklist
Why was this MR needed?
So our Frontend Development process gets better.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Documentation created/updated - Review
-
Has been reviewed by Frontend
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together -
Internationalization required/considered -
End-to-end tests pass ( package-and-qamanual pipeline job)
What are the relevant issue numbers?
Edited by Tim Zallmann