xz / xz/new.css
The production site is down? 404 error?
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 4.1k
- Forks
- 127
- PR merge metrics
- No merged PRs in 30d
Description
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the screenshot and the issue thread to identify which production URL returns 404, then reproduce the failure. Inspect the repository's hosting or deployment entry point and confirm the site loads successfully without the reported 404 when done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100