Skip to content

An improved 404 page design #1427

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

Merged
merged 5 commits into from
Oct 24, 2024
Merged

An improved 404 page design #1427

merged 5 commits into from
Oct 24, 2024

Conversation

samejr
Copy link
Member

@samejr samejr commented Oct 23, 2024

  • New layout for the 404 page
  • Uses the same logic as before, no major code changes other than layout
  • Includes a 3D Trigger.dev logo made in Spline

Summary by CodeRabbit

  • New Features

    • Enhanced visual presentation and functionality of the error display component.
    • Introduced animated background effects for a more engaging user experience.
  • Bug Fixes

    • Updated button text from "Home" to "Go to homepage" in the error display.
  • Refactor

    • Improved layout structure of the ErrorDisplay component, utilizing new components for better styling and interaction.

Copy link

changeset-bot bot commented Oct 23, 2024

⚠️ No Changeset found

Latest commit: 78bc86b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

coderabbitai bot commented Oct 23, 2024

Walkthrough

The changes involve modifications to the ErrorDisplay.tsx component and the route.tsx file. The ErrorDisplay component has been redesigned to enhance its visual presentation, incorporating new imports, a full-screen layout, animated elements, and updated button properties. Additionally, the button text in the RouteErrorDisplay fallback has been changed to "Go to homepage." These updates aim to create a more interactive and visually appealing error handling experience.

Changes

File Path Change Summary
apps/webapp/app/components/ErrorDisplay.tsx Updated imports, redesigned layout with full-screen dark background, added animated elements, changed button text to "Go to homepage", and modified function signatures.
apps/webapp/app/routes/_app.orgs.$organizationSlug/route.tsx Changed button title in RouteErrorDisplay from "Home" to "Go to homepage" in the error fallback.

Poem

In the web's bright glow, a change takes flight,
Errors now dance, a whimsical sight.
With buttons that guide, and backgrounds that play,
"Go to homepage," they cheer, lighting the way!
A rabbit hops by, with joy in its heart,
For every new feature is a work of art! 🐰✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (1)
apps/webapp/app/components/ErrorDisplay.tsx (1)

58-58: Clarify the purpose of the empty div

The self-closing <div> at line 58 has styling applied but contains no content. If it's intended for visual layout or effects, consider adding a comment to explain its purpose. If it's unnecessary, you might consider removing it to clean up the code.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 2d63c5d and 78bc86b.

📒 Files selected for processing (2)
  • apps/webapp/app/components/ErrorDisplay.tsx (2 hunks)
  • apps/webapp/app/routes/_app.orgs.$organizationSlug/route.tsx (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • apps/webapp/app/routes/_app.orgs.$organizationSlug/route.tsx
🧰 Additional context used
🔇 Additional comments (1)
apps/webapp/app/components/ErrorDisplay.tsx (1)

65-69: Verify the external iframe source for security and privacy concerns

Embedding an external iframe from "https://my.spline.design/..." may introduce security and privacy risks. Ensure that this external content is from a trusted source and that embedding it complies with your application's security policies.

Run the following script to identify other external iframes in the codebase, which can help assess if this practice is consistent with existing patterns:

{message && <Paragraph>{message}</Paragraph>}
<LinkButton
to={button ? button.to : "/"}
shortcut={{ modifiers: ["meta"], key: "g" }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Potential conflict with existing browser shortcut for "Command+G"

The shortcut meta+g may conflict with existing browser shortcuts (e.g., "Command+G" is commonly used for "Find Next" in browsers on macOS). Consider choosing a different key combination to avoid overriding default browser behavior.

Copy link

pkg-pr-new bot commented Oct 23, 2024

@trigger.dev/build

pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/build@1427

@trigger.dev/core

pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/core@1427

@trigger.dev/react-hooks

pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/react-hooks@1427

trigger.dev

pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev@1427

@trigger.dev/sdk

pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/sdk@1427

commit: 78bc86b

@ericallam ericallam merged commit 9bc641d into main Oct 24, 2024
9 checks passed
@ericallam ericallam deleted the better-404 branch October 24, 2024 09:37
@coderabbitai coderabbitai bot mentioned this pull request Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants