You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To speed up DPUL-Collections development (see #133 for details) we will replace LUX Header and Footer components with custom Phoenix Components. From a user perspective, these components should seek to mimic the look, feel, and functionality of the LUX components, at least for this iteration.
It may be helpful to use LUX's CSS to match colors and other atomic styles using CSS-variables. See the instructions.
Due to anticipated interactivity and stateful needs, the Header component should be implemented as a Phoenix Live Component. The Footer should be fine implemented as a functional component as it will only need to compartmentalize markup.
Summary or User Story
To speed up DPUL-Collections development (see #133 for details) we will replace LUX Header and Footer components with custom Phoenix Components. From a user perspective, these components should seek to mimic the look, feel, and functionality of the LUX components, at least for this iteration.
It may be helpful to use LUX's CSS to match colors and other atomic styles using CSS-variables. See the instructions.
Due to anticipated interactivity and stateful needs, the Header component should be implemented as a Phoenix Live Component. The Footer should be fine implemented as a functional component as it will only need to compartmentalize markup.
Implementation Notes
Review the markup for the LuxLibraryHeader and LuxUniversityFooter to see how these are constructed.
Acceptance Criteria
This section can be completed by the DLS team. Some requirements to consider
including:
First step
Write a test.
The text was updated successfully, but these errors were encountered: