What type of PR is this? (check all applicable)

• [x] Refactor
• [x] Feature
• [x] Optimization

Description

This updates the reading list to get the tags of the articles in your reading list as opposed to filtering by the tags you follow. General consensus among the team was that we should make this change, since the current version (tags you follow) was not really intuitive.

Related Tickets & Documents

Closes https://github.com/forem/InternalProjectPlanning/issues/240

QA Instructions, Screenshots, Recordings

1. Save some articles from the home page: localhost:3000
2. Go to your reading list: localhost:3000/readinglist
3. See that the proper tags are displayed, and that there are no duplicates

Added tests?

• [x] No, and this is why: We don't test for the state of the readingList component at all, so I didn't feel the need to add one. Happy to though, if I should!

Added to documentation?

• [x] No documentation needed

[optional] What gif best describes this PR or how it makes you feel?

What type of PR is this? (check all applicable)

• [ ] Refactor
• [x] Feature
• [ ] Bug Fix
• [ ] Optimization
• [ ] Documentation Update

Description

Small adjustment.

We recently shipped this button which just said "user", but I think adding the user's name here is more human.

It's a small thing and totally cool that we shipped the first copy as something we could later improve on.

QA Instructions, Screenshots, Recordings

Please replace this line with instructions on how to test your changes, as well as any relevant images for UI changes.

Added tests?

• [x] Yes
• [ ] No, and this is why: please replace this line with details on why tests have not been included
• [ ] I need help with writing tests

Added to documentation?

• [x] Developer Docs and/or Admin Guide
• [ ] README
• [ ] No documentation needed

What type of PR is this? (check all applicable)

• [ ] Refactor
• [x] Feature
• [ ] Bug Fix
• [ ] Optimization
• [ ] Documentation Update

Description

In several cases, email address domains are a great way to restrict access to a certain Forem, whether it's a company-wide Forem, or perhaps one restricted to people with a harvard.edu email address, it's a pretty established pattern which has been requested.

In a lot of cases it can be used in conjunction with invitations to help ensure everyone that should have access to a Forem can most easily without adding extra process burden.

Related Tickets & Documents

We've talked about this but I couldn't find a ticket.

QA Instructions, Screenshots, Recordings

This PR includes the option to make public which domains are allowed. There are legit reasons for not displaying this info if it is private.

Added tests?

• [x] Yes
• [ ] No, and this is why: please replace this line with details on why tests have not been included
• [ ] I need help with writing tests

Added to documentation?

• [x] Developer Docs and/or Admin Guide
• [ ] README
• [ ] No documentation needed

I will add to the admin guide after this is merged.

[optional] Are there any post deployment tasks we need to perform?

Yes. Add to admin guide.

[optional] What gif best describes this PR or how it makes you feel?

What type of PR is this? (check all applicable)

• [x] Refactor
• [ ] Feature
• [ ] Bug Fix
• [ ] Optimization
• [ ] Documentation Update

Description

This PR introduces updated design for footer. With recently introduced dynamic links for navigation, the design we've created for footer while ago stopped making sense. We've created that footer design having in mind very specific links listed in a very specific order. With generalizing navigation in general we also have to start thinking about footer slightly different, having other Forems in mind as well - since the order of the links made sense only for DEV anyway.

On the bright side of things, I think this UI for footer is definitely much more flexible and feels more readable.

Related Tickets & Documents

• #10921

QA Instructions, Screenshots, Recordings

Added tests?

• [ ] Yes
• [x] No, not needed.
• [ ] I need help with writing tests

Added to documentation?

• [ ] Docs.forem.com
• [ ] README
• [x] No documentation needed

[optional] Are there any post deployment tasks we need to perform?

🚨🚨🚨 There's always something related with cache...

What type of PR is this? (check all applicable)

• [x] Refactor
• [ ] Feature
• [ ] Bug Fix
• [x] Optimization
• [ ] Documentation Update

Description

This PR introduces a slightly updated layout and UI for user's profile. The idea is to consolidate left and right sidebars into one basically. This is a temporary (or not?) solution until we're done with rethinking IA for entire user view.

QA Instructions, Screenshots, Recordings

Just click around.

Added tests?

• [ ] Yes
• [x] No, not yet because I'm not sure if any are needed.
• [ ] I need help with writing tests

Added to documentation?

• [ ] Docs.forem.com
• [ ] README
• [x] No documentation needed

What type of PR is this? (check all applicable)

• [x] Refactor
• [ ] Feature
• [ ] Bug Fix
• [x] Optimization
• [ ] Documentation Update

Description

This PR applies a bit of styling to our Notifications view.

It's a first take on this and there are clearly things we could improve (especially reaction buttons and icons and their states) but probably later in future.

QA Instructions, Screenshots, Recordings

If you want to populate your notifications locally, go here.

Added tests?

• [ ] yes
• [ ] no, because they aren't needed
• [ ] no, because I need help

Added to documentation?

• [ ] docs.forem.com
• [ ] readme
• [x] no documentation needed