feat: Welcome & Not Found page

[mpabarca]

Description

• Create welcome page (desktop and mobile).

• This page includes an UI layer with some "guidance/tips" on how to use the dashboard, that will depend of the status of the user. (see screenshots)
  -> If there is not project on the user dashboard
  -> If somehow the browser lose the session from the user or is still loading so it's show placeholder

• Change [[...slug]] route to [...slug] so now the path "/" is not included on that layout.

• Create folder (welcome) to locate this "/" route with an specific layout and page.

• Create a Not Found page

Motivation and Context

Now that more people (and possibly more companies) are joining, it might be a good idea to improve the UI and UX to make navigating the platform more enjoyable.

Screenshots:

Special cases

Mobile version

Not Found page

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

[simonbs]

Great job on making the Not Found and Welcome pages more engaging! The Not Found page looks perfect, but I’ve left some comments on the Welcome page for your thoughts.

My main suggestion is to reduce the amount of content on the Welcome page. Currently, there’s a lot happening, which might overwhelm users and make it harder for them to know what to focus on.

Additionally, would it make sense to convert the help text with arrows into traditional, dismissible tooltips? This way, returning users won't see content that's no longer relevant to them. We could track whether the tooltip is hidden using local storage, avoiding any need to modify the database schema.

[mpabarca]

Additionally, would it make sense to convert the help text with arrows into traditional, dismissible tooltips? This way, returning users won't see content that's no longer relevant to them. We could track whether the tooltip is hidden using local storage, avoiding any need to modify the database schema.

@simonbs I like the idea! I started implementing it, but I noticed something related to the strict mode we have in the app’s development environment. I’d like to address this "bug" before moving forward, , as it affects the correct behaviour needed to achieve this idea.

Would it be possible to leave it this way for now, and in the next PR, I can add this cool idea and hopefully solve the issue?