lirios / lirios/lirios.github.io
404 on team page
Nobody has claimed this yet.
- Dominant language
- Astro
- Stars
- 18
- Forks
- 16
- Avg merge
- 3h 6m
- Merged PRs (30d)
- 6
Description
On the initial load, the team page returns the following error (tested with Chrome and its default JS console).
GET https://liri.io/team/%7B%7B%20member.image%20%7D%7D 404 ()
%7B%7B%20member.image%20%7D%7D Failed to load resource: the server responded with a status of 404 ()
The error itself apparently relates to one deferred JS function in the generated HTML.
It doesn't break the site but it appears to slow it down ever so slightly.
PS: Any way to get the team page working in a development environment?
I'm still a Jekyll newbie and have yet to figure out what the "API" bit in team.js is referring to (and why there's a reference to port 8080 in there). However, it's the only page that doesn't appear to even load on localhost.
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 inspecting the team page's generated HTML and team.js, then reproduce the GET request for the literal {{ member.image }} path in Chrome. Check how the team page is served locally and what the API reference and port 8080 represent. Done means the page no longer requests the unresolved template path and loads without the 404 in development.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, jekyll
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100