Add welcome mat with homepage redirects

[echappen]

Blocked by #524

Changes proposed in this pull request:

• Redirects users to /login when navigating to root / and not authenticated
• When authenticated and navigating to root, redirect users to one of their orgs: /orgs/:org_id
  • When lastViewedOrgId is set, take them to this org
  • If not, then make a CAPI request to get their first org and take them there
• Implements welcome mat design for /orgs/:org_id as specified in Create "welcome mat" for authenticated users #529
• Pulls in real blog data from https://cloud.gov/updates.xml

How to test

• add NEXT_PUBLIC_BLOG_FEED_URL=https://cloud.gov/updates.xml to .env.local
• Spin up a uaa-docker container (instructions)
• Log into the CF CLI
• Run the dev server npm run dev-cf
• Try to access / - you should be redirected to UAA login
• Use the credentials found in /uaa-docker/uaa.yml to log in
• After log in, you should be redirected to /orgs/:org_id

Related issues

Closes #529

Submitter checklist

• Added logging is not capturing sensitive data and is set to an appropriate level (DEBUG vs INFO etc)
• Updated relevant documentation (README, ADRs, explainers, diagrams)

Security considerations

Uses org id stored in cookie to make CF API requests in order to show the content on the page

[beepdotgov]

@echappen This looks so good already. Excited to see this (almost) live!

I spotted a couple things in this branch; I know it’s still a WIP, so logging them here for when/if you’re ready for them.

This is probably a setup thing on my end, but the blog area’s not loading for me:

The leading on the main card is a little tight; could we increase it a bit?

(Adding a line-height-sans-4 to that graf looked good to me, but let me know what you think.)

It looks like the org picker is overlapping the main content area:

And finally, will you be working the updated footer into this PR? (widescreen, small screen)

(If it’s out of scope for this week, that’s great — let me know, and I’ll open a separate issue for implementation!)

[echappen]

@beepdotgov Thanks for all this! Let's open up a separate issue to update the footer, as I think that will take some dedicated work and I wouldn't want that to hold up the rest.

[beepdotgov]

@echappen On it! Edit: done! #591

[beepdotgov]

Thanks so much for the tip on the blog feed config, @echappen — it looks great now.

I’d love to suggest a couple tiny tweaks, if you have a minute! Here’s the current state:

Here’s a quick in-browser edit:

Here’s the TLDR of what I changed:

1. Changed .text-light to .text-normal on the h2
2. Added a non-breaking space between “Cloud.gov” and “blog” in the h2, to prevent the orphaned word
3. Removed the top margin on the article title
4. Added line-height-sans-4 to the blog teaser

Do those seem doable to you?

(Also, it looks like the browser’s default link colors might be getting applied to links in that block; is that right? Can we apply our default blue for the dash?)

[echappen]

@beepdotgov All doable! Just pushed those updates.

[hursey013]

I'm noticing on initial login that I'm directed to a blank homepage as opposed to the login page. If I reload the page, I'm properly directed to localhost:9001/login.

[echappen]

I'm noticing on initial login that I'm directed to a blank homepage as opposed to the login page. If I reload the page, I'm properly directed to localhost:9001/login

@hursey013 I noticed that middleware wasn't triggering at all for initial page loads of the root url /. Including it in the route matchers seems to fix that. Do you know if we'd need anything more specific for the matcher?