Feature: Redirect opensauced.pizza/username to /user/username

[bdougie]

Type of feature

🍕 Feature

Current behavior

Working on social cards and it would be nice to redirect these urls.

Suggested solution

Add a redirect in Netlify

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Contributing Docs

• I agree to follow this project's Contribution Docs

[shamimbinnur]

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

[bdougie]

@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.

[shamimbinnur]

@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?

[bdougie]

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.

[bdougie]

Might be better suited for a URL shortener.

[shamimbinnur]

@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?

[bdougie]

Let's go with /u

[shamimbinnur]

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