aziontech/bundler

feat: Create Azion/Vulcan custom 404

jotanarciso opened this issue · 1 comments

jotanarciso commented

Description:

Currently, when the Azion/Vulcan Edge function (worker) cannot find an asset and there is no handled 404 response for server-side generated (SSG) pages, a generic 404 error is displayed. To enhance the user experience and branding, we want to create a custom 404 page that aligns with the platform's design and provides relevant information to the users.

The goal of this issue is to implement a custom 404 page within the Azion/Vulcan platform. This page will be displayed when a requested asset or SSG page is not found, improving the user experience and providing a more informative and visually appealing error message.

Tasks:

  • Design and create a custom 404 page template that aligns with the platform's design guidelines.
  • Implement the necessary logic in the Azion/Vulcan Edge function to detect and display the custom 404 page when an asset or SSG page is not found.
  • Update the server-side generated (SSG) rendering to return the custom 404 page when a requested page is not found.
  • Test the custom 404 page in various scenarios to ensure its functionality and visual appeal.
  • Document the usage and configuration of the custom 404 page in the platform's documentation.
  • Perform code review and ensure the implementation meets quality standards.
  • Update the project's documentation and contribute guidelines to reflect the changes and provide information on contributing to the project.

Acceptance Criteria:

  • A custom 404 page should be designed and implemented to align with the platform's design guidelines.
  • The Azion/Vulcan Edge function should be updated to detect and display the custom 404 page when an asset or SSG page is not found.
  • Server-side generated (SSG) rendering should return the custom 404 page when a requested page is not found.
  • The custom 404 page should be tested in different scenarios to ensure its functionality and visual appeal.
  • The usage and configuration of the custom 404 page should be documented in the platform's documentation.
  • All tasks should be completed and tested.
  • The code should undergo a thorough review and adhere to the project's quality standards.