- HTML 62.4%
- CSS 21.5%
- JavaScript 16.1%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
Arshdeep
9337866e8e
The bars were only doing a CSS :hover color swap to a native <title>
tooltip — slow to appear, unstyleable, and on its own gives no reason
for a bar to look interactive at all.
Replaced with one shared .chart-tooltip, positioned on hover/focus,
matching the site's own card styling instead of the browser default.
Every bar and line-chart point is now tabindex="0" so keyboard/touch
users get the same info via focus, not just mouse hover.
Content is more useful too, not just a repeat of the axis label:
- Wealth/hourly bars now show a percentage of the total alongside the
count ("12 people · 18% of the total · 0–100 Rokda").
- The daily line chart gets a dot on every single day, not just the
first/last/peak the labels already cover — every day's number is a
hover or a tab away now.
- Skips the peak label whenever the peak lands on the first or last
day, which would sit it directly on the date label already there.
Verified in-browser: dispatched real mouseover/mouseout/focusin events
and confirmed the tooltip shows the right content, hides on mouseout,
and computed styles (gold fill, dark card, pointer cursor) resolve
correctly in both cases.
|
||
| assets | ||
| .gitignore | ||
| commands.html | ||
| credits.html | ||
| index.html | ||
| leaderboard.html | ||
| minecraft.html | ||
| README.md | ||
| REDESIGN.md | ||
| script.js | ||
| styles.css | ||
| testers.html | ||
After Hours Docs
Live: https://afterhours.arshnah.in
Public landing page, command reference, and alpha tester checklist for After Hours, a Discord bot. Plain HTML/CSS/JS, no build step, no framework, no dependencies. Pages: index.html (landing), commands.html (full command catalog), testers.html (alpha test checklist), leaderboard.html (live top players), shared styles.css and script.js.
Live data. index.html and leaderboard.html both carry a
<meta name="jugaad-api"> tag pointing at https://jugaadapi.arshnah.in (the
bot's read-only API, behind nginx on the VPS). The command count and the
leaderboards come from there. leaderboard.html also has a Server
Activity section — a daily messages chart, a busiest-hours-UTC chart, and a
Rokda wealth distribution, all plain hand-built SVG (lineChart/barChart in
script.js, no chart library) reading /activity and /wealth. It is
progressive enhancement: the numbers in the HTML are already correct, and
a missing tag, an unreachable API, a CORS refusal or bad JSON all leave the
page exactly as served. The failure mode is "slightly stale", never "blank".
Both tags must match.
Activity data only exists from whenever guild_activity_daily started being
written (see Jugaad-Bot/lib/activity.js) — the daily chart has no history
before that and starts empty, by design, not as a bug. Wealth is a live
snapshot of every wallet, so it's accurate immediately.
Search. Cmd/Ctrl+K anywhere opens a palette that searches every command;
/ focuses whichever filter the page has. commands.html is the single source
of truth for the index — on that page it's read from the DOM, elsewhere it's
fetched and parsed, so nothing is generated or duplicated.
The real OAuth2 invite URL is live in index.html. The footer used to carry a GITHUB_REPO_PLACEHOLDER; it now links to commands.html instead, because the bot repo is private (it's cloned with a PAT — see Jugaad-Bot/DEPLOY.md) and a public visitor would just hit a 404. Swap it for a real GitHub link if the repo is ever made public. To deploy: import this repo into Vercel via the dashboard and accept the defaults — it's a static folder, so no configuration is needed.
Heads-up for future updates: commands.html and testers.html both go stale as new phases ship. They were generated against the bot's live command code, so each is split into live commands and Coming soon ones. testers.html only lists commands that were live at generation time. When a new phase lands, re-walk jugaad-bot/commands/ and re-sync both pages — move newly-shipped commands out of Coming soon in commands.html, and add them to the testers.html checklist with an action + expected result (and an edge case where one is worth testing).