Should I add the navbar on the 404 page?
I'll submit a pr with some first looks soon

@IyaadDev it would be really great if you propose some UI designs.

👍

will provide some later this week*

Quick question: [slug].page.tsx seems to cover all pages, I've tried changing the code a bit so that 404 errors are displaying the page on 404.tsx, but it doesn't seem to work... any potential solutions?

export async function getStaticPaths() {
  // Adjusted to extract 'paths' directly
  const { paths } = await getStaticMarkdownPaths('pages');

  return {
    paths,
    fallback: false, // Show 404 for unknown paths
  };
}

export async function getStaticProps(args: any) {
  // Adjusted to extract 'props' directly
  const result = await getStaticMarkdownProps(args, 'pages');

  if (
    !result ||
    !result.props ||
    !result.props.frontmatter ||
    !result.props.content
  ) {
    return {
      notFound: true, // Trigger 404 page
    };
  }

  // Return the 'props' object
  return {
    props: result.props,
  };
}

@IyaadDev this can be helpful https://nextjs.org/docs/14/pages/building-your-application/routing/custom-error

@DhairyaMajmudar what do you think of this design?

@AQIB-NAWAB Looks cool 💯

Okk nice , I will develope according to this design

I'll be away for a while, @AQIB-NAWAB looks like he's doing a good job so far 👍

Just a quick proposal for your design: perhaps change the casing on the "back home" button

In addition, installing the 404 page may mean modifying the error handling process in _error, personally, I still haven't figured out how to do it yet...

I'll be away for a while, @AQIB-NAWAB looks like he's doing a good job so far 👍

Thank you! @AQIB-NAWAB you can go ahead with your PR.

Hi, Is this issue still open for contribution? If yes, I’d love to work on it.

Yep, still open :)
Feel free to work on it!

thanks... will drop a pr soon