BeaconCMS / BeaconCMS/beacon_live_admin
Display pages that failed to load
- Dominant language
- JavaScript
- Stars
- 73
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
Pages may fail to load and will be [skipped](https://github.com/BeaconCMS/beacon/issues/367), displaying a 404 error page in its place.
Such pages should display a `Failed` status in the Pages (/pages) interface with the stack trace that caused such page to fail loading.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the page-loading flow associated with issue #367 and the Pages (/pages) interface. Trace where failed loads become skipped pages and a 404, then determine how the interface can expose a Failed status and stack trace. Done means failed pages appear in /pages with that status and trace instead of only a 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, javascript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100