trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
P2 Explorer ✕
LaterP0 TrustP1 FeedP10 MoneyP10 TalkP11 Files and dataP11 MoneyP12 Files and dataP12 MaintainersP13 MaintainersP13 TemplatesP14 TemplatesP3 Fork treeP4 Forge in a linkP5 Open to every agentP6 Never lostP7 SteeringP8 StoryP9 CalmP9 MultiplayerP9 Talkbugflowfull-suiteoutside
- /explore has a search box: a plain GET form on ?q= that filters ranked apps by name and description P2 Explorer
- /search and `GET /api/v1/search` find guides too, as their own group above issues and code P2 Explorer
- /explore.atom's `updated` is the newest entry's time, so a reader sees no change until there is one P2 Explorer
- /sitemap.xml also lists the guides, /templates, /security and /status, each with its last change P2 Explorer
- Asking /explore for a page past the last one goes to the last page, and the address says which page is shown P2 Explorer
- Every search door takes the same longest query, and no page echoes more of it than fits on a line P2 Explorer
- An app's explore row shows its last-ship date and fork count read from stored state, with no per-row query P2 Explorer
- Every app on /explore carries a 'make it yours' button that forks it into the visitor's forge in one POST P2 Explorer
- /api/v1/explore rows carry the numbers the page's why-line shows: forks, ships, likes and age P2 Explorer
- /explore filters to what changed in the last 7 or 30 days with two plain links kept in the URL P2 Explorer
- /explore sorts by newest or most forked with two plain links kept in the URL, the active one marked P2 Explorer
- Each row on /explore says why it sits where it does in plain numbers: forks, ships, likes and age P2 Explorer
- /explore pages its list with a plain Next and Previous link kept in the URL P2 Explorer
- /explore with filters that match nothing says so and offers the one link that clears them P2 Explorer
- /explore sorts by freshness as well as use, chosen by a plain link and kept in the URL P2 Explorer
- The explorer's filter state lives in the URL, so a filtered view can be sent and reloaded P2 Explorer
- The explorer's filters live in the address, so a filtered view can be shared and survives a reload P2 Explorer
- The explorer's filters live in the URL: a shared link reproduces the same ranked list P2 Explorer
new above
offline