SSWConsulting / SSWConsulting/SSW.Rules

💄 404 Page - UI Improvements

Open
#2,395 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

01-small Area: Frontend YakShaver
Dominant language
TypeScript
Stars
26
Forks
17
Avg merge
14h 39m
Merged PRs (30d)
2

Description

Requested by: @Aibono1225 via YakShaver.ai 🦬
cc: @Aibono1225, @Marxoz, @PothieuG, @Freego1783, @tiagov8

Hi Team!

  🟥  Watch the video (1 min 2 sec)

  Url from screen share: https://ssw.com.au/rules/kb

Pain

The current 404 (Not Found) page in Rules V3 (TinaCMS) is visually inconsistent with the existing SWO website error page. This PBI aims to review the design with the designer and either improve the current 404 page or align it to match the standard SSW error page for a consistent user experience.

Acceptance Criteria
  1. The 404 page design is reviewed with a designer.
  2. A decision is made to either enhance the existing 404 page or align it with the SSW website error page.
  3. The implemented 404 page matches the approved design and visual standards of the SSW website.
  4. The 404 page displays correctly when navigating to a non-existent URL.
Screenshot

Screenshot
Figure: 404 page inconsistent with current site error page design

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by opening the Rules V3 page at https://ssw.com.au/rules/kb and navigating to a non-existent URL to inspect the current 404 page. Compare it with the standard SSW website error page, then confirm the preferred design with a designer; done means the implemented page matches the approved visual direction and renders correctly for missing routes.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs, typescript
Domain
design, frontend, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.