Feature: Redirect opensauced.pizza/username to /user/username about landing-page HOT 8 CLOSED

@bdougie Did you mean https://opensauced.pizza/username to https://insights.opensauced.pizza/user/username?

from landing-page.

Let's go with /u

from landing-page.

@bdougie Did you mean https://opensauced.pizza/username to https://insights.opensauced.pizza/user/username?

Yes. This will most likely need an edge function to quickly check if the user exist in the API.

Open to other suggestions.

from landing-page.

@bdougie Did you mean https://opensauced.pizza/username to https://insights.opensauced.pizza/user/username?

Yes. This will most likely need an edge function to quickly check if the user exist in the API.

Open to other suggestions.

@bdougie Where would the user be redirected if the user doesn't exist?

Since we are redirecting users to the insight, shouldn't the insight app handle the rest?

from landing-page.

Since we are redirecting users to the insight, shouldn't the insight app handle the rest?

Correct ideally the insights app would have a 404. Today the page displays with errored data if not found.

from landing-page.

Might be better suited for a URL shortener.

from landing-page.

@bdougie If we use the "/username" path we will be required to check our existing pages ('/blog', '/teams) and add some logic to treat these as reserved paths. And this has to be refactored every time we add a new route for pages.

But if we use "/u/username" we will not be required the checking.

Which path should we go for?

from landing-page.

@bdougie This issue has been fixed and addressed in #128

from landing-page.