JdeRobot / JdeRobot/VisualCircuit
Fix: Broken "Website" link and FontAwesome 403 error on About/Tutorial pages .
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 20
- Forks
- 34
- Avg merge
- 4h 56m
- Merged PRs (30d)
- 10
Description
Describe the bugs
While reviewing the live documentation, I identified two technical issues that affect user experience and UI consistency:
-
Broken "Follow" Link (404 Not Found): The "Website" link under the "Follow" button on the About page is configured as a relative link instead of an absolute URL. This causes a 404 error as it tries to navigate to
/about/jderobot.github.ioinstead of the actual organization homepage. -
FontAwesome Kit Error (403 Forbidden): The script at line 561 (
https://kit.fontawesome.com/4eee35f757.js) is failing to load. This prevents icons from rendering correctly across the site.
To Reproduce
- Go to the VisualCircuit About Page.
- Click the Follow button and select Website -> Observe the 404 error.
- Open DevTools (F12) and check the Console -> Observe the 403 error for the FontAwesome kit.
Screenshots
Technical Analysis
- Navigation: The link needs to be updated from
jderobot.github.iotohttps://jderobot.github.ioto prevent relative pathing. - Icons: The FontAwesome Kit ID
4eee35f757likely needs thejderobot.github.iodomain added to its whitelist, or the project should move to a standard CDN.
Suggested Solution
I am happy to submit a Pull Request to fix the relative link and update the FontAwesome implementation if directed to the preferred configuration files.
Contributor guide
No contributing guide indexed for this repository
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 with the About and Tutorial page sources and inspect the FontAwesome script around line 561. Verify the Follow > Website destination and the browser console error, then confirm the link resolves correctly and icons load without a 403 on the affected pages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100