WIP: Rewrite frontend guide
What does this MR do?
Proposed re-structure
graph LR
A[Frontend Guide] --> B[Principles]
A --> C[Initiatives]
A --> D[Development]
A --> E[Style guides]
A --> F[Tips]
A --> G[Dependencies]
B --> B1(Discuss your architectural design before implementation)
B --> B2(Principle describing when to use Vue, jQuery and vanilla JS)
C --> C1(CSS refactor initiative)
C --> C2(Webpack code splitting initiative)
C --> C3(Use gitlab-svgs initiative)
D --> D1(Design patterns)
D --> D2(Components)
D --> D3(Accessibility)
D --> D4(Network Requests)
D --> D5(Security)
D --> D6(Performance)
D --> D7(Internationalization)
E --> E1(Vue)
E --> E2(SCSS)
G --> G1(Overview)
G --> G2(DropLab)
G --> G3(Gitlab-svgs)
http://ce-docs-fe-guide.178.62.207.141.xip.io/ce/development/fe_guide/
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
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-qa
manual pipeline job)
What are the relevant issue numbers?
Edited by Clement Ho