-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat: Implement page footer with USWDS components #1285
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for veda-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
renamed old footer to PageFooterLegacy
I suppose the content will be included in the new footer component
Contributes to the feature branch #1285 Hej @snmln ! Thanks for setting up the feature branch and foundations for the new footer component! I renamed the old footer to PageFooterLegacy, that way we can use the regular import path for our new footer component. Also added a .env var that allows us to switch between old and new footer implementations easily. Campground Rule[^1]: While working on the feature flag, I addressed an unrelated lint warning within the files I made changes to. [^1]: Always leave the campground cleaner than you found it.
**Related Ticket:** _{link related ticket here}_ ### Description of Changes Creating slim footer. - Establishing initial Front-end - Creating footer object model in veda.config.js - Setting up initial default.config.js - Wiring up Config data flow - Turning USWDS breakpoints on TO DO's for this PR: - Implement dynamic creation of links in footer component
@faustoperez Can you take a look at the preview view here: https://deploy-preview-1285--veda-ui.netlify.app/ We have the front-end in place and are currently working through functionality. So this should be in a good spot for a design review. |
This reverts commit d830c03.
type='button' | ||
tabIndex={0} | ||
id={item.id} | ||
onClick={show} | ||
style={{background: 'none', border: 'none', cursor: 'pointer'}} | ||
style={{ background: 'none', border: 'none', cursor: 'pointer' }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what was the reason for using inline styles?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Style problems detected over in next-veda-ui (developmentseed/next-veda-ui#26):
|
Creating initial test suite
I am adding some more fields to the secondary section in the footer section, in order to have any text content configurable: Added `division`, `version`, and `name`, repurposed `title`. I'd be curious to know how other instances might use and configure the footer, this could better inform naming decisions (e.g. `division`?).
@AliceR I have corrected the issues on the nextjs instance. Heads up on one of the bullet points:
This is an issue with the content section not respecting the |
Related Ticket: #1135
Description of Changes
TO DO:
Checkin with Fausto on progress.Notes & Questions About Changes
{Add additonal notes and outstanding questions here related to changes in this pull request}
Validation / Testing
{Update with info on what can be manually validated in the Deploy Preview link for example "Validate style updates to selection modal do NOT affect cards"}