[FEATURE] <Add customize 404-page>

[bhavyastar]

Description

• Add customize 404 page
• If by mistake the user redirects to the wrong page, then a customized webpage with a 404 status code will be shown.

Screenshots

Additional information

No response

[AvineshTripathi]

@bhavyastar can you work on homepage remaining part as suggested in the comments there and I can take this and get done today

[bhavyastar]

The PR is already done for the Homepage.

[codezuma]

@bhavyastar Is this issue closed i would like to contribute also where can i find the vector you have showed in screenshot,
for now if i choose a wrong route it redirecting to hashnode 404

[AvineshTripathi]

You can customize however that change won't be done in this repo and instead should be done on hashnode cause current 404 is nothing but 404 from hashnode

[codezuma]

@AvineshTripathi I didn't get you, what are you trying to say ?

[AvineshTripathi]

currently our 404 page is redirected to 404 page of hashnode of which source code is not there in this repo so any customizing for 404 should be done outside this repo

[codezuma]

We can change the routing

[AvineshTripathi]

There is some routing conflicts already due to which I believe had to have a similar arrangement so I dont think that is possible unless we solve that complexity

[AvineshTripathi]

@sanyamjain04 ^ can you confirm if this is correct?

[sanyamjain04]

@sanyamjain04 ^ can you confirm if this is correct?

The 404 page of kubesimplify is 404 page of blogs.kubesimplify.com, so no need to create a 404 page

[AvineshTripathi]

To customize it we should do changes in hashnode and notin this repo

[sanyamjain04]

I don't think there is an option to change the default 404 page to our custom 404 page in Hashnode.

and we already have a 404 page on kubesimplify website that appear for 1-2 seconds and then redirects to the hashnode 404 page.

[sanyamjain04]

I just confirm there is no feature available for changing the 404 page in hashnode.

[bhavyastar]

I think we need to close this issue.
CC: @AvineshTripathi