UI Pattern Library & CMS/Portal Infrastructure #155
wesleyboar
started this conversation in
Ideas
Replies: 3 comments
-
|
The whole Portal and CMS team is welcome. I am sure @jchuahtacc, @rstijerina, @jgentle, and @xandroc can offer some experienced direction. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
We could also do this in a video chat, instead. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
As of FP-1472 and FP-721 completion, the current plan is "2. Use Two Independent Solutions" that are the same desired software, but "3. Use One Independent Software" may exist using undesirable software until the former can be realized. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Question
How coupled do we want UI pattern library software to be to our Core-CMS & Core-Portal?
If discussing this requires knowing how to share components, please see Ideas to Share Components Across CMS And Portal.
Ideas
I imagine a scale of options from tightly-coupled to complete independence:
0. Use Two Independent Features
Have 2 independent low-tech manual solutions that use existing Django and React features.
1. Use One Coupled Software
Just 1 software configured for both Django and React.
2. Use Two Independent Solutions
Have 2 softwares, or 2 instances of one software, configured for Django and React respectively.
3. Use One Independent Software
Just 1 software configured for static assets, independent of Django and React.
Reference
Beta Was this translation helpful? Give feedback.
All reactions