palladius / palladius/vibecoding
404 Error for Article with External URL in data.yaml
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
The article 'Autotranslate my Hugo blog with Gemini' (publish_date: 2024-02-05) is defined in etc/data.yaml with an external url (https://ricc.rocks/...). However, the application attempts to serve this article via an internal route (/articles/2024-02-05-autotranslate-my-hugo-blog-with-gemini), resulting in a 404 error.
This indicates a mismatch between the data definition and the routing logic for articles that have external URLs. The application should either:
- Directly link to the external URL for such articles.
- Have a mechanism to fetch and display the content from the external URL internally (if desired, though direct linking is simpler).
Currently, the article is unreachable within the application's internal routing.
(Note: This issue is a re-creation of #10, using a temporary file for the body as per user instruction.)
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 article entry in etc/data.yaml for “Autotranslate my Hugo blog with Gemini” and trace the application’s article routing logic for entries with an external url. Confirm the current 404 behavior, then verify that the article is reachable through the application by following its external URL rather than an internal article route.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100