-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: introduced not found / error layout #6247
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Ideally through a Markdown file. Realistically, it's complex (sorta) but doable For static exports, once the Website Redesign is done, is imperative that the structure and content of But that has a few caveats:
|
cc @canerakdas ☝️ my comment above has a relevant solution. |
Lighthouse Results
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Awesome work here! ✨
Description
This PR introduces not found / error layout
Screenshot
Validation
npm run serve:redesign