feat: add landing page for catalyst

[kieckhafer]

Impact: minor
Type: feature

Issue

When a user first lands on the Operator UI, a blank screen is shown, which makes it look broken.

Solution

Add a landing page that just lets the user know where they are, and provides links to docs, and common features.

Breaking changes

None

Testing

1. Go to /operator
2. See the landing page
3. Click other links and make sure they all still work, and the the landing link doesn't override them.

[kieckhafer]

@rymorgan @cassytaylor just wanted to put something here so that there isn't a blank page when you first log into the Operator UI. I think this passes as a first draft of this, just to get it up there, but happy to discuss improvements if you think this needs to be changed before it's merged.

[kieckhafer]

@aldeed could you please take a look specifically at how the Route is added to the Switch, just want to make sure I'm doing that in a legit way: https://github.com/reactioncommerce/reaction/pull/5226/files#diff-44c61a0d4d7989c935d5505b71eff89dR130

I was initially adding it using the registerOperatorRoute function, but it was getting loaded before other routes were added to that array, therefore overriding them so every page would just show this component.

We could add it to the very end of that array, knowing our current components that are loaded, however if someone adds a new route in the future that happens to get loaded after this one, then it would cause the same problem, which is why i did it this way.

[rymorgan]

I'm good with this as a draft. I think in the near future we should leverage this page as an onboarding dashboard and possibly an alert center but let's give that some thought. Having it look not broken is a win.

[aldeed]

@kieckhafer I think if you add exact prop to the Route in the map (it's a boolean prop so just needs to be present with no value), then registering it will work. I'm guessing none of our other registered components are relying on the default partial path matching, but a quick skim should be enough to see if it broke any other routes.

https://reacttraining.com/react-router/web/api/Route/exact-bool

[kieckhafer]

@aldeed I don't think any other components are relying on the default, I took a look and didn't' see anything. Plus the blank page... so if something was relying on it, it wasn't working anyway.

Adding the exact prop works, PR updated, ready for another look.

[aldeed]

👍 Leaving for @machikoyasuda to merge if this looks good.

[machikoyasuda]

Suggested change

	See our <MuiLink href="https://docs.reactioncommerce.com/docs/dashboard">Store Operator's Guide</MuiLink> for more information.
	See our <MuiLink href="https://docs.reactioncommerce.com/docs/dashboard">Store Operator’s Guide</MuiLink> for more information.

[machikoyasuda]

@kieckhafer Looks good! I just had this tiny tiny nitpick. If you want, I can commit this and merge it.

[kieckhafer]

No worries, I updated it, thanks for catching that! Should be ready now.