mirror of
https://github.com/aljazceru/goose.git
synced 2025-12-17 06:04:23 +01:00
46 lines
2.2 KiB
YAML
46 lines
2.2 KiB
YAML
version: 1.0.0
|
||
title: "404Portfolio"
|
||
description: "Create personalized, creative 404 pages using public profile data"
|
||
|
||
instructions: |
|
||
Create an engaging 404 error page that tells a creative story using a user's recent public content from **one** of the following platforms: **GitHub**, **Dev.to**, or **Bluesky**. You do not need to use all three—just the one selected by the user.
|
||
|
||
The page should be fully built with **HTML, CSS, and JavaScript**, featuring:
|
||
|
||
* Responsive design
|
||
* Personal branding elements (e.g., name, handle, avatar)
|
||
* Narrative-driven layout that turns the error into an opportunity for discovery
|
||
|
||
Use platform-specific methods to fetch recent user content:
|
||
|
||
* For **Dev.to**, use the [public Dev.to API](https://developers.forem.com/api) to retrieve recent articles, reactions, and profile information.
|
||
* For **GitHub**, use the GitHub REST or GraphQL API to access recent repos, commits, and contributions.
|
||
* For **Bluesky**, use public feed endpoints from the AppView API (e.g., `app.bsky.feed.getAuthorFeed`) to pull posts, replies, or likes.
|
||
|
||
Incorporate the fetched data into a compelling narrative (e.g., “Looks like this page is missing, but \[username] has been busy!”), and display it using engaging visuals like cards, timelines, or media embeds.
|
||
|
||
Wrap the user’s activity into a story — for example:
|
||
|
||
“This page may be lost, but @username is building something amazing. Their latest open source journey involves a new repo that’s gaining stars fast…”
|
||
“You won’t find what you’re looking for here, but you will find @username’s hot take on async/await in their latest Dev.to post.”
|
||
|
||
The result should be a small narrative-driven microsite that dynamically celebrates the user's presence online—even when the destination is missing.
|
||
|
||
Ask the user:
|
||
|
||
1. Which platform to use: GitHub, Dev.to, or Bluesky
|
||
2. Their username on that platform
|
||
|
||
Then generate the complete code in a folder called 404-story.
|
||
|
||
|
||
activities:
|
||
- "Build error page from GitHub repos"
|
||
- "Generate error page from dev.to blog posts"
|
||
- "Create a 404 page featuring Bluesky bio"
|
||
|
||
extensions:
|
||
- type: builtin
|
||
name: developer
|
||
- type: builtin
|
||
name: computercontroller |