Skip to content

Conversation

@megh-bari
Copy link
Contributor

@megh-bari megh-bari commented Aug 17, 2025

… dreaded 404 abyss

Description

This PR implements a custom 404 (Page Not Found) page with a “Go Back To Home” button to replace the default Next.js error page. The new page provides a branded user experience that aligns with OpenCut's design system and offers clear navigation back to the main application. it help users easily return to the homepage when they hit a missing page.

Previously, users encountering non-existent routes would see a generic browser/Next.js error page. This custom implementation maintains brand consistency and provides a better user experience with helpful navigation options.


Screenshots

Laptop View

image

Mobile View

image

Type of change

  • 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)
  • This change requires a documentation update

How Has This Been Tested?

  • Manually tested that the 404 page displays correctly and the “Go Back To Home” button redirects to the homepage.
  • Responsive design: Verified layout works on mobile and desktop viewports
  • Navigation functionality: Confirmed "Go Home" button redirects to main page
  • Image loading: Tested custom 404 image loads correctly

Test Configuration:

  • Node version: v22.12.0
  • Browser: Chrome/Brave
  • Operating System: Windows

Test Steps:

  1. Run bun dev
  2. Navigate to http://localhost:3000/non-existent-page
  3. Verify custom 404 page displays with proper styling
  4. Click "Go Home" button to test navigation
  5. Test on different screen sizes for responsiveness

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have added screenshots if ui has been changed
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Additional context

This update improves user experience by guiding users from dead-end pages back to the homepage quickly.

Design Decisions:

  • Used Next.js app router convention with not-found.tsx for automatic 404 handling
  • Implemented custom image with optimal visibility
  • Leveraged existing UI components (Button, Lucide icons) for consistency
  • Followed project's Tailwind CSS patterns for styling

Files Added:

  • src/app/not-found.tsx - Custom 404 page component
  • public/images/404-custom.png - Branded 404 image asset

This contribution aligns with the project's contribution guidelines, focusing on UI/UX improvements while avoiding the preview system area scheduled for refactoring.

Summary by CodeRabbit

  • New Features
    • Introduced a dedicated 404 “Page Not Found” experience for invalid URLs.
    • Provides clear page title and description for improved SEO and sharing.
    • Full-screen, centered layout with a custom illustration and friendly guidance.
    • Prominent “Go Back to Home” button with recognizable icon for quick recovery.
    • Responsive design aligned with existing branding for a seamless look and feel.

@vercel
Copy link

vercel bot commented Aug 17, 2025

@megh-bari is attempting to deploy a commit to the OpenCut OSS Team on Vercel.

A member of the Team first needs to authorize it.

@netlify
Copy link

netlify bot commented Aug 17, 2025

👷 Deploy request for appcut pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 03f9ebe

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 17, 2025

Walkthrough

Adds a Next.js App Router NotFound page at apps/web/src/app/not-found.tsx, exporting metadata (title, description) and a default NotFound component that renders a full-screen 404 view with a custom image and a button linking to the homepage.

Changes

Cohort / File(s) Change Summary
NotFound Page
apps/web/src/app/not-found.tsx
New App Router 404 page added. Exports metadata (title, description) and default NotFound component. Uses next/image, next/link, a UI Button, and lucide-react Undo2 icon; renders centered 404 UI with 404-custom.png and a "Go Back To Home" action.

Sequence Diagram(s)

sequenceDiagram
  participant User
  participant NextAppRouter as Next.js App Router
  participant NotFound as not-found.tsx
  participant Home as "/"

  User->>NextAppRouter: Request unknown route
  NextAppRouter->>NotFound: Render NotFound page
  NotFound-->>User: Display 404 view with image and button
  User->>NotFound: Click "Go Back To Home"
  NotFound->>Home: Navigate to "/"
  Home-->>User: Render homepage
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I twitch my whiskers at a missing way,
A painted 404 where lost links stray.
With a hop and a button, homeward I glide,
Undo2 winks — the path restored with pride. 🥕

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between a9a0b83 and 03f9ebe.

📒 Files selected for processing (1)
  • apps/web/src/app/not-found.tsx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • apps/web/src/app/not-found.tsx
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Vade Review
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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

🧹 Nitpick comments (2)
apps/web/src/app/not-found.tsx (2)

6-10: metadata export is likely ignored in not-found.tsx

In Next.js App Router, metadata/generateMetadata are supported on page.tsx and layout.tsx, not not-found.tsx. This export may be a no-op and could confuse future maintainers. Consider removing it or moving the title/description logic to the nearest layout/page.

Apply:

-export const metadata = {
-  title: "404 | Page Not Found - OpenCut",
-  description:
-    "Oops! The page you’re looking for isn’t available. Head back to the homepage or continue exploring OpenCut.",
-};

If you want a 404-specific title, we can explore a layout-level title template approach or centralize metadata in app/layout.tsx.


14-16: Minor a11y/semantics polish: use

, add an H1, and fix extra whitespace

  • Prefer a semantic <main> landmark for primary content.
  • Provide a visible <h1> (“Page not found”) to set page context for screen readers.
  • Remove the double space in text-gray-600 mb-8.
-    <div className="min-h-screen flex bg-white items-center justify-center">
+    <main className="min-h-screen flex bg-white items-center justify-center" role="main">
       <div className="text-center">
         <div className="mb-4">
@@
-        <p className="text-gray-600  mb-8">
+        <h1 className="text-2xl font-semibold mb-2">Page not found</h1>
+        <p className="text-gray-600 mb-8">
           Sorry, the page you&apos;re looking for can&apos;t be found.
         </p>
@@
-    </div>
+    </main>

Also applies to: 25-27, 35-35

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 13dff38 and a9a0b83.

⛔ Files ignored due to path filters (1)
  • apps/web/public/images/404-custom.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • apps/web/src/app/not-found.tsx (1 hunks)
🧰 Additional context used
📓 Path-based instructions (5)
**/*.{jsx,tsx}

📄 CodeRabbit Inference Engine (.github/copilot-instructions.md)

**/*.{jsx,tsx}: Don't use accessKey attribute on any HTML element.
Don't set aria-hidden="true" on focusable elements.
Don't add ARIA roles, states, and properties to elements that don't support them.
Don't use distracting elements like <marquee> or <blink>.
Only use the scope prop on <th> elements.
Don't assign non-interactive ARIA roles to interactive HTML elements.
Make sure label elements have text content and are associated with an input.
Don't assign interactive ARIA roles to non-interactive HTML elements.
Don't assign tabIndex to non-interactive HTML elements.
Don't use positive integers for tabIndex property.
Don't include "image", "picture", or "photo" in img alt prop.
Don't use explicit role property that's the same as the implicit/default role.
Make static elements with click handlers use a valid role attribute.
Always include a title element for SVG elements.
Give all elements requiring alt text meaningful information for screen readers.
Make sure anchors have content that's accessible to screen readers.
Assign tabIndex to non-interactive HTML elements with aria-activedescendant.
Include all required ARIA attributes for elements with ARIA roles.
Make sure ARIA properties are valid for the element's supported roles.
Always include a type attribute for button elements.
Make elements with interactive roles and handlers focusable.
Give heading elements content that's accessible to screen readers (not hidden with aria-hidden).
Always include a lang attribute on the html element.
Always include a title attribute for iframe elements.
Accompany onClick with at least one of: onKeyUp, onKeyDown, or onKeyPress.
Accompany onMouseOver/onMouseOut with onFocus/onBlur.
Include caption tracks for audio and video elements.
Use semantic elements instead of role attributes in JSX.
Make sure all anchors are valid and navigable.
Ensure all ARIA properties (aria-*) are valid.
Use valid, non-abstract ARIA roles for elements with...

Files:

  • apps/web/src/app/not-found.tsx
**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (.github/copilot-instructions.md)

**/*.{ts,tsx}: Don't use TypeScript enums.
Don't export imported variables.
Don't add type annotations to variables, parameters, and class properties that are initialized with literal expressions.
Don't use TypeScript namespaces.
Don't use non-null assertions with the ! postfix operator.
Don't use parameter properties in class constructors.
Don't use user-defined types.
Use as const instead of literal types and type annotations.
Use either T[] or Array<T> consistently.
Initialize each enum member value explicitly.
Use export type for types.
Use import type for types.
Make sure all enum members are literal values.
Don't use TypeScript const enum.
Don't declare empty interfaces.
Don't let variables evolve into any type through reassignments.
Don't use the any type.
Don't misuse the non-null assertion operator (!) in TypeScript files.
Don't use implicit any type on variable declarations.
Don't merge interfaces and classes unsafely.
Don't use overload signatures that aren't next to each other.
Use the namespace keyword instead of the module keyword to declare TypeScript namespaces.
Don't use empty type parameters in type aliases and interfaces.
Don't use any or unknown as type constraints.
Don't use the TypeScript directive @ts-ignore.
Use consistent accessibility modifiers on class properties and methods.
Use function types instead of object types with call signatures.
Don't use void type outside of generic or return types.

**/*.{ts,tsx}: Don't use primitive type aliases or misleading types
Don't use the TypeScript directive @ts-ignore
Don't use TypeScript enums
Use either T[] or Array consistently
Don't use the any type

Files:

  • apps/web/src/app/not-found.tsx
**/*.{js,jsx,ts,tsx}

📄 CodeRabbit Inference Engine (.github/copilot-instructions.md)

**/*.{js,jsx,ts,tsx}: Don't use the return value of React.render.
Don't use consecutive spaces in regular expression literals.
Don't use the arguments object.
Don't use primitive type aliases or misleading types.
Don't use the comma operator.
Don't write functions that exceed a given Cognitive Complexity score.
Don't use unnecessary boolean casts.
Don't use unnecessary callbacks with flatMap.
Use for...of statements instead of Array.forEach.
Don't create classes that only have static members (like a static namespace).
Don't use this and super in static contexts.
Don't use unnecessary catch clauses.
Don't use unnecessary constructors.
Don't use unnecessary continue statements.
Don't export empty modules that don't change anything.
Don't use unnecessary escape sequences in regular expression literals.
Don't use unnecessary labels.
Don't use unnecessary nested block statements.
Don't rename imports, exports, and destructured assignments to the same name.
Don't use unnecessary string or template literal concatenation.
Don't use String.raw in template literals when there are no escape sequences.
Don't use useless case statements in switch statements.
Don't use ternary operators when simpler alternatives exist.
Don't use useless this aliasing.
Don't initialize variables to undefined.
Don't use the void operators (they're not familiar).
Use arrow functions instead of function expressions.
Use Date.now() to get milliseconds since the Unix Epoch.
Use .flatMap() instead of map().flat() when possible.
Use literal property access instead of computed property access.
Don't use parseInt() or Number.parseInt() when binary, octal, or hexadecimal literals work.
Use concise optional chaining instead of chained logical expressions.
Use regular expression literals instead of the RegExp constructor when possible.
Don't use number literal object member names that aren't base 10 or use underscore separators.
Remove redundant terms from logical expressions.
Use while loops instead of...

Files:

  • apps/web/src/app/not-found.tsx
**/*.{tsx,jsx}

📄 CodeRabbit Inference Engine (.cursor/rules/ultracite.mdc)

**/*.{tsx,jsx}: Always include a title element for icons unless there's text beside the icon
Always include a type attribute for button elements
Accompany onClick with at least one of: onKeyUp, onKeyDown, or onKeyPress
Accompany onMouseOver/onMouseOut with onFocus/onBlur
Don't import React itself
Don't define React components inside other components
Don't use both children and dangerouslySetInnerHTML on the same element
Don't insert comments as text nodes
Use <>...</> instead of ...

Files:

  • apps/web/src/app/not-found.tsx
**/*.{ts,tsx,js,jsx}

📄 CodeRabbit Inference Engine (.cursor/rules/ultracite.mdc)

**/*.{ts,tsx,js,jsx}: Don't use the comma operator
Use for...of statements instead of Array.forEach
Don't initialize variables to undefined
Use .flatMap() instead of map().flat() when possible
Don't assign a value to itself
Avoid unused imports and variables
Don't use await inside loops
Don't hardcode sensitive data like API keys and tokens
Don't use the delete operator
Don't use global eval()
Use String.slice() instead of String.substr() and String.substring()
Don't use else blocks when the if block breaks early
Put default function parameters and optional function parameters last
Use new when throwing an error
Use String.trimStart() and String.trimEnd() over String.trimLeft() and String.trimRight()

Files:

  • apps/web/src/app/not-found.tsx
🧠 Learnings (1)
📓 Common learnings
Learnt from: CR
PR: OpenCut-app/OpenCut#0
File: .cursor/rules/ultracite.mdc:0-0
Timestamp: 2025-08-15T00:50:09.126Z
Learning: Applies to {pages/**/**/*.{tsx,jsx},app/**/**/*.{tsx,jsx},src/pages/**/**/*.{tsx,jsx},src/app/**/**/*.{tsx,jsx}} : Don't use <img> elements in Next.js projects
Learnt from: CR
PR: OpenCut-app/OpenCut#0
File: .cursor/rules/ultracite.mdc:0-0
Timestamp: 2025-08-15T00:50:09.126Z
Learning: Applies to {pages/**/**/*.{tsx,jsx},app/**/**/*.{tsx,jsx},src/pages/**/**/*.{tsx,jsx},src/app/**/**/*.{tsx,jsx}} : Don't use <head> elements in Next.js projects
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Vade Review
🔇 Additional comments (1)
apps/web/src/app/not-found.tsx (1)

17-23: Good use of Next/Image and alt text

  • Uses next/image (aligned with our “no in Next.js” guideline).
  • Alt text is concise and meaningful.

@enkei64
Copy link
Contributor

enkei64 commented Aug 18, 2025

I'm confused about line 9 in not-found.tsx, what do you mean by "or continue exploring OpenCut"?

@megh-bari
Copy link
Contributor Author

I'm confused about line 9 in not-found.tsx, what do you mean by "or continue exploring OpenCut"?

Just add it casually, nothing else. It means both "Go to Home Page" and " Continue Explore OpenCut" take you to the homepage, where you can explore. It’s just a description for metadata bruh

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